Fujitsu Lifebook P727 laptop review
I have recently purchased a Vodafone USB 3G modem to access the Internet from my ASUS laptop, and it's been horribly flaky. It disconnects for no obvious reason - even though the Voda control panel thinks it is still connected - on a regular basis and my MS VPN which has been rock solid over many private and public networks drops out equally regularly even when the link is actually up.
Voda's help desk suggested that I reduce the MTU on the link to "1300 or even 1100" so I edited the registry and set a new DWORD as MTU=1300 (it's the last setting in the following Registry dump of the registry settings for the Voda interface and is 1300 in Hex):
This has made a difference, but when I the tested the MTU size using an unfragemented ping such as:
ping 22.214.171.124 -l 1350 -f
I worked out that the MTU size is actually set to 1471 (or perhaps it's still 1500 if I add the TCP/IP overhead in).
So for some reason my MTU registry edit has not worked...or perhaps worked differently to what I was expecting??
Obviously, any thoughts would be appreciated because at the moment I my very expensive 3G modem is in danger of going in the bin.
SG TCP/IP Analyser gives the MTU as 1420 (full results are below) which suggests my ping test did not work well at all. Interestingly, MTU Discovery in enabled, so Voda should not have a problem with MTU size if they configure their end properly, but I guess they are only a communications company :-)
TCP options string: 0204056401010402
TCP Window: 16560 (multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 16560
Reccomended RWINs: 63480, 126960, 253920, 507840
BDP limit (200ms): 662kbps (83KBytes/s)
BDP limit (500ms): 265kbps (33KBytes/s)
MTU Discovery: ON
IP ToS: 00000000 (0)
DrTCP does the Registry tweaks for you and can be run from a Desktop icon as and when required.
BTW the ping test you mentioned earlier is how to work out your optimum MTU not how to find out what it's already set at click here
From what you say it does appear that your optimum is 1500.
So much for Voda's help desk...the MTU on this problem was a furphy. It's actually the inactivity timer that is causing the problems. I edited the Vodafone INF and changed InactivityScale (as per a Microsoft MSDN article) so it has a longer timeout and the problem is solved.
This thread is now locked and can not be replied to.