I also posted this prob in the 2k networking newgroup as i
am not sure weather is IE6 prob or network prob.
Thanks,
Cypher
.
I am having a similar problem. If you find an answer in
a different newsgroup, please post here also or email me.
Thanks,
Dwaine
>..
>
>
>.
>
Thanks for any input or help.
Kevin
"Dwaine" <dpr...@teknowinc.com> wrote in message news:<0a7e01c3a283$a0ed5630$a301...@phx.gbl>...
Testing to determine MTU Value
From the command prompt (a DOS window) on the system directly
connected to the Internet, type one of the following commands to find
the Internet Gateway.
For Windows 98 and Me: WINIPCFG
For Windows 2000 or XP: IPCONFIG
Next, from a command prompt on a client computer, the following
command will be used, with several different values for packet size,
to determine the largest MTU size that works:
PING -f -l nnnn xxx.xxx.xxx.xxx
-f tells the command not to fragment the packet.
-l nnnn sets the size of packet, where nnnn corresponds to the value
for MTU being tested.
xxx.xxx.xxx.xxx is the Gateway IP address
I would suggest running the above command, with the following sequence
of packet size values:
1500 -- Which should result in either an error message about needing
to fragment the packet, or 100% packet loss.
If this first PING command does not fail, then either an MTU mis-match
is not the problem, or the IP address is not located at the other end
of the connection.
1420 -- Which hopefully is low enough that the command will succeed
with 0% packet loss.
Increase the packet size by steps of 10, until the error message or
100% packet loss again occurs.
Decrease the packet size by steps of 2, until the command again
succeeds with 0% packet loss. This resulting value is the correct MTU
for the client systems.
Setting the MTU on Client Systems
Once the MTU value to use has been established, then on every client
system, the Ethernet adapter connected to the network must have the
MTU set to that value.
You can either change the registry or use the Dr TCP tool
http://www.dslreports.com/front/drtcp.html.
If you are using widows XP, SP1 fixes this apparently.
<anon...@discussions.microsoft.com> wrote in message news:<05db01c3a274$366dd6e0$a601...@phx.gbl>...