Problem solved.
The Voyager 2100 has 2 MTU settings both on the LAN and WAN side.
By default its set to 1400.. and even changing it in line to those set on your PC and performing the max packet size check
C:\Documents and Settings\kitz>ping -f -l 1402 www.kitz.uk.com
Pinging www.kitz.uk.com [213.171.219.239] with 1402 bytes of data:
Reply from 213.171.219.239: bytes=1402 time=60ms TTL=247
Reply from 213.171.219.239: bytes=1402 time=49ms TTL=247
Reply from 213.171.219.239: bytes=1402 time=47ms TTL=247
Reply from 213.171.219.239: bytes=1402 time=47ms TTL=247
Ping statistics for 213.171.219.239:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 60ms, Average = 50ms
If the remote server is mis-configured then for some reason the Voyager doesnt appear to pass the headers on the the LAN side correctly.
This only dawned after using ethereal to capture packets to see exactly what was going on.
217.146.105.5 -> 192.168.7.2 -> TCP -> http > 1110 []Seq=`769441889 Ack=1 Win-20498 bogus TCP header length (0, must be at least 20).
Ive no idea why the MTU setting of 1430 was getting broken.. but changing it to 1500 on the LAN side solved this problem.
This is a long-standing issue with the Voyager 2100 that even had Voyager stumped way back in Feb 2006.Thanks to
MickKi, a customer on the PN portal forums, for suggesting I try capturing the data packets to see if I could see where things were going wrong and for his input on there.
