1) Click Start, Run and enter GPEDIT.MSC
2) Go to Computer Configuration, Administrative Templates, System.
3) Locate the entry for Turn autoplay off and modify it as you desire.
Sunday, September 28, 2008
Wednesday, September 17, 2008
Aztech DSL605EW setting
I used MTU = 1302 for my modem
Finding the largest MTU, by EXPERIMENT
If your MTU is too low already, (maybe 576), the following method will not be able to detect whether you can switch to an optimal size..... So first follow "CHANGING MTU for PPPoE" to reset MTU to 1500, reboot, then come back to this!
The best value for MTU is that value just before your packets get fragmented. How do you find out that? by using ping! Open an MSDOS command prompt, and just use ping -l 1472 -f www.dslreports.com, (that is a dash-letter-l-for-lambda not a dash-number-one). Reduce 1472 by 10 until you no longer get the "packet needs to be fragmented" error message, then increase by 1 until you find the max command line number for ping.
Add 28 more to this (since you specified ping packet data size, not including a packet header of 28 bytes) AND THIS IS YOUR MaxMTU.
The MaxMTU you get using this method might very well be 1500, in which case, everything is pretty boring, and your MaxMTU must already be set ok, otherwise you could not get ping working up to 1472.
For PPPoE, your MaxMTU should be no more than 1492, to allow space for the 8 byte PPPoE "wrapper", but again, experiment to find the optimal value.. For PPPoE, the stakes are high: if you get MTU wrong, you may not just be sub-optimal, things like UPLOADING, or web pages, may stall, or not work at all!
(TCP, IP, MTU and MSS magic numbers)1500 The biggest sized IP packet that can normally traverse the internet without getting fragmented. Typical MTU for non PPPoE, non VPN connections.
1492 The maximum MTU recommended for internet PPPoE implementations
1472 The maximum ping data payload before fragmentation errors are received on non-PPPoE non VPN connections
1460 TCP Data size (MSS) when MTU is 1500 and not using PPPoE
1464 The maximum ping data payload before fragmentation errors are received when using a PPPoE connected machine
1452 TCP Data size (MSS) when MTU is 1492 and using PPPoE
576 Typically recommended as the MTU for dialup type applications .. leaving 536 bytes of TCP data.
48 The sum of IP, TCP, and PPPoE headers
40 The sum of IP, and TCP headers
28 The sum of IP, ICMP headers
Finding the largest MTU, by EXPERIMENT
If your MTU is too low already, (maybe 576), the following method will not be able to detect whether you can switch to an optimal size..... So first follow "CHANGING MTU for PPPoE" to reset MTU to 1500, reboot, then come back to this!
The best value for MTU is that value just before your packets get fragmented. How do you find out that? by using ping! Open an MSDOS command prompt, and just use ping -l 1472 -f www.dslreports.com, (that is a dash-letter-l-for-lambda not a dash-number-one). Reduce 1472 by 10 until you no longer get the "packet needs to be fragmented" error message, then increase by 1 until you find the max command line number for ping.
Add 28 more to this (since you specified ping packet data size, not including a packet header of 28 bytes) AND THIS IS YOUR MaxMTU.
The MaxMTU you get using this method might very well be 1500, in which case, everything is pretty boring, and your MaxMTU must already be set ok, otherwise you could not get ping working up to 1472.
For PPPoE, your MaxMTU should be no more than 1492, to allow space for the 8 byte PPPoE "wrapper", but again, experiment to find the optimal value.. For PPPoE, the stakes are high: if you get MTU wrong, you may not just be sub-optimal, things like UPLOADING, or web pages, may stall, or not work at all!
(TCP, IP, MTU and MSS magic numbers)1500 The biggest sized IP packet that can normally traverse the internet without getting fragmented. Typical MTU for non PPPoE, non VPN connections.
1492 The maximum MTU recommended for internet PPPoE implementations
1472 The maximum ping data payload before fragmentation errors are received on non-PPPoE non VPN connections
1460 TCP Data size (MSS) when MTU is 1500 and not using PPPoE
1464 The maximum ping data payload before fragmentation errors are received when using a PPPoE connected machine
1452 TCP Data size (MSS) when MTU is 1492 and using PPPoE
576 Typically recommended as the MTU for dialup type applications .. leaving 536 bytes of TCP data.
48 The sum of IP, TCP, and PPPoE headers
40 The sum of IP, and TCP headers
28 The sum of IP, ICMP headers
Saturday, September 13, 2008
reset winsock LSP
CAUSE
There are known spyware programs that install layered service providers (LSPs) on client computers to gather user data. When Windows AntiSpyware (Beta) removes spyware programs, it also removes the spyware-based LSPs. However, Windows AntiSpyware (Beta) does not restore any LSPs after it removes the spyware.
Back to the top
RESOLUTION
Windows XP SP2
To resolve this problem if you are running Microsoft Windows XP Service Pack 2 (SP2), follow these steps:1. Rebuild the Winsock LSP chain. To do this, follow these steps:a. Log on to the Microsoft Windows XP workstation as an administrator.
b. Click Start, click Run, type cmd, and then click OK.
c. At the command prompt, type the following, and then press ENTER:
netsh Winsock reset
When the program is finished, you will receive the following message:
Successfully reset the Winsock Catalog. You must restart the machine in order to complete the reset.
If you receive this message, go to step 1d.
If you are not logged in as an administrator, you will receive the following error message:
Unable to reset the Winsock Catalog. Access is denied.
If you receive this message, log off the computer, and then log back on by using an account with Administrator access. Typically, the first user account that was created has Administrator access. Then, repeat steps 1b and 1c.
d. Restart your computer.
2. Test each of your third-party programs that are known to use LSPs.
3. Reinstall any malfunctioning third-party programs that are known to use LSPs.
There are known spyware programs that install layered service providers (LSPs) on client computers to gather user data. When Windows AntiSpyware (Beta) removes spyware programs, it also removes the spyware-based LSPs. However, Windows AntiSpyware (Beta) does not restore any LSPs after it removes the spyware.
Back to the top
RESOLUTION
Windows XP SP2
To resolve this problem if you are running Microsoft Windows XP Service Pack 2 (SP2), follow these steps:1. Rebuild the Winsock LSP chain. To do this, follow these steps:a. Log on to the Microsoft Windows XP workstation as an administrator.
b. Click Start, click Run, type cmd, and then click OK.
c. At the command prompt, type the following, and then press ENTER:
netsh Winsock reset
When the program is finished, you will receive the following message:
Successfully reset the Winsock Catalog. You must restart the machine in order to complete the reset.
If you receive this message, go to step 1d.
If you are not logged in as an administrator, you will receive the following error message:
Unable to reset the Winsock Catalog. Access is denied.
If you receive this message, log off the computer, and then log back on by using an account with Administrator access. Typically, the first user account that was created has Administrator access. Then, repeat steps 1b and 1c.
d. Restart your computer.
2. Test each of your third-party programs that are known to use LSPs.
3. Reinstall any malfunctioning third-party programs that are known to use LSPs.
Thursday, September 11, 2008
Subscribe to:
Posts (Atom)