Sounds like an MTU (Max Transfer Unit) problem. DSL lines require you to use a lower MTU than 1500 (which is standard for ethernet,) since there is some overhead when you encapsulate the ethernet packages to go through the DSL modem.
It is best to have the MTU set as large as possible, otherwise you get fragmentation of packages, effectively making the line appear slower.
With most DSL lines, you should probably use MTU=1452, but to get an accurate value, issue the command
"ping -f -l 1452 <some-internet-ip>"
If it complains about fragmented packages, lower the number, if not, make it bigger. When you reach the maximum possible, subtract 28 (I think it was), and the result should be the correct MTU value.
How to set this value for the network depends on the hardware/operating system.
Main Topics
Browse All Topics





by: Chris-DentPosted on 2009-10-23 at 06:06:05ID: 25643943
Yes DNS first...
nslookup bankofengland.co.uk
If you get an IP back there, test it on the client with:
ping bankofengland.co.uk
If both of those give you IP addresses, check the browser to see if it's using a Proxy, if it does, troubleshooting needs to happen there. That's the end of DNS's involvement though, it would be time to check network connectivity (telnet bankofengland.co.uk 80), if it fails to connect, see if it's being blocked by your infrastructure.
Chris