MTU Test
Problem:
How to check optimal WAN MTU settings.
Solution:
The primary reason is that in most if not all cases if you send packets at 1500 they will need to be fragmented resulting in degradation of performance. I would not reccomend changing the MTU settings without first checking the optimal settings for your environment, do not just take the word of your ISP, they are making a generalized statement that covers the masses, it is not a total optomization.
Checking is easy to do. First make sure that your MTU setting is in fact 1500 or the test is compromised and will result in a number that is too low.
The command is to see the largest packet is “ping -f -l XXXX www.XXX.com” -f -l forces the ping packet size to be what you specify, any size to lage returns a reply that the packet needed to be fragmented.
-l is a lowwercase L
XXXX is mtu speeds start at 1500 and decrease in multiples of 10 (1500, 1490, 1480 etc…) until you get a ping result, then increase in multiples of 1 until you again get the reply that the packets needed to be fragmented. The highest numbet that did not have to be fragmented is your highest optimal number. I would actually suggest decreasing it by 2. So if 1464 is the highest you could send without fragmentation set the MTU to 1462.
and XXX is a website of your choosing.
Grime Fighter keeps windows from booting
Problem:
Power on windows, but Avast Grime fighter immediately loads and cause a black scren – never moves farther than that. To make matters worse, there is no entry in the BIOS for this boot option.
Solution:
If your system runs Windows 8 or 8.1, please try this:
Boot to a Windows CD. You may have to disable Secure boot or mess wit UEFI settings in the bios to do this. As lon as the CD is the first boot device, it should allow you to bypass Grimefighter.
Select “Advanced options” -> “Troubleshoot” -> “Advanced Options” -> “Command Prompt”
Login to your Windows account if it prompts you
In the command prompt type (without the quotes) “bootrec /fixboot” and hit ENTER
Then type “exit” and hit ENTER
Select “Turn off your PC”
Power on the PC with the power button
If the above “bootrec /fixboot” command doesn’t work for you, you can remove the Grimefighter boot entry manually by booting back to the command prompt and doing this:
run “bcdedit /enum firmware”
Scroll up and look for the Windows Boot Manager entry with a description of Avast! Grimefighter
There will be an identifier number for this entry, it will be a random string of numbers like {233a9f91-efd8-4771-a9c7-5f4ecc823458}
Hightlight the identifier, including the curly braces, this will copy the identifier, so you can paste it into the next command, to paste after highlighting, you hit the right mouse key
Scroll back down so you can run another command
To delete the Grimefighter entry run “bcdedit /delete {233a9f91-efd8-4771-a9c7-5f4ecc823458}” using the identifier you have copied for your Grimefighter entry instead of my example one, be very careful here and make sure the identifier you delete is the one for Grimefighter, double check it before hitting ENTER
Laserjet p4015 constantly ramps up but dosen’t print
Problem:
When a print job is sent to the printer, the printer will display processing job on the control panel, and will continually ramp up and down attempting to print the job. After several minutes the printer will return to ready without posting any error messages. Occasionally, after several minutes the print job will print
Solution:
This usually isn’t a roller problem as the printer WILL pick up the paper, it just takes a few minuets, but it never hurts to check. Next check the firmware. If it’s older than 04.060.7, then it is causing a fault in the fuser. This is a documented problem and the fuser needs to be replaced. In addition, the firmware needs to be upgraded to version 04.060.7 or higher to prevent this error from recurring. You can download an executable firmware upgrade utility from :
Don’t forget to update the firmware to the latest version, if you haven’t already done it, to prevent the new fuser failing with the same fault.
