Article View: comp.dcom.modems.cable
Article #444Re: BIZARRE tcp/ip problem ATTN: Navas/Swit
From: Lawrence Baldwin
Date: Tue, 06 Feb 2001 03:41
Date: Tue, 06 Feb 2001 03:41
132 lines
5473 bytes
5473 bytes
John/Randy, anyone else, I tackled this one. Bottom-line he could only load pages that were a few hundred bytes in size...or he could load pages from certain (e.g. Microsoft sites). Problem was he was negoitiating TCP MSS=1460, but in reality his link could only pass 512 byte packets reliably. Once I saw that in the trace, I did some size ranging pings on him: This pretty much sums it up: Let's test that theory with some pings where we vary the size: C:\users\default>ping -l 512 24.219.14.14 -t Pinging 24.219.14.14 with 512 bytes of data: Reply from 24.219.14.14: bytes=512 time=125ms TTL=114 Reply from 24.219.14.14: bytes=512 time=125ms TTL=114 Reply from 24.219.14.14: bytes=512 time=125ms TTL=114 Reply from 24.219.14.14: bytes=512 time=125ms TTL=114 Reply from 24.219.14.14: bytes=512 time=109ms TTL=114 Reply from 24.219.14.14: bytes=512 time=125ms TTL=114 ^C C:\users\default>^C 512 byte pings seem fine. Let's try 513 bytes: C:\users\default>^Cping -l 513 24.219.14.14 -t Pinging 24.219.14.14 with 513 bytes of data: Reply from 24.219.14.14: bytes=513 time=187ms TTL=114 Reply from 24.219.14.14: bytes=513 time=187ms TTL=114 Request timed out. Reply from 24.219.14.14: bytes=513 time=219ms TTL=114 Reply from 24.219.14.14: bytes=513 time=172ms TTL=114 Reply from 24.219.14.14: bytes=513 time=219ms TTL=114 Reply from 24.219.14.14: bytes=513 time=157ms TTL=114 Request timed out. Reply from 24.219.14.14: bytes=513 time=172ms TTL=114 ^C Ahhhh! Drops start happening. Now let's go up to 1400 bytes (what you end up needing to surf): C:\users\default>^Cping -l 1400 24.219.14.14 -t Pinging 24.219.14.14 with 1400 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. ^C C:\users\default> bamo: 100% packet loss. Conclusion: We've got a packet size problem...not sure if it's the network or your PC yet. Forced his MTU down to 512 bytes and he's surfing fine now. This obviously isn't a solution, so my next question is what the heck is going on here. At first it sounded a lot like the known ICS issue where it introduces it's own 576 byte MTU...but he says he doesn't have that installed. Oh yeah, and David didn't make it very easy on me, guy has cable modem, but no phone...man! lb. (PacketBoy) David Ciesnik wrote: > > Hello, > > I am almost at wits end with my cable modem connection! Tech support is > throwing their hands up in the air and I have never seen a problem like > this either, so I'm not sure how to proceed. > > I'm running win98. I have three things under network preferences.. > "Network for MS clients", Network adapter, and TCP/ip. Everything is > setup correctly. My network configuration is setup automatically from the > DHCP server. So my computer is assigned all of the proper values. I have > an IP address. I am able to telnet out. I can even ping my computer from > an outside network. > > But it appears that outside servers (webservers, mailservers) can't see or > read my IP address, EXCEPT for microsoft owned servers. Is this some > conspiracy from Redmond???? I launch my web browser, and I can only get > to msn.com, microsoft.com, hotmail.com.. but nothing else. The sites that > do load, load slowly, but they at least load. For any other sites, like > yahoo.com, it says "site found" and the loading status bar grows, but > eventually it just times out. > > Also, when I try to check mail.. either from MS outlook express or > netscape mail, I get the status "getting message 1 of 10", so it KNOWS how > many messages are on the server, but it can't retrieve them. > > My connection worked fine with win95. This problem started when I > "upgraded" to win98 on Friday. > > Anybody have any idea what's going on?? Why do MS sites load? I > reinstalled win98 twice already. I uninstalled and reinstalled my tcp/ip > stack several times. Anybody else experience anything like this?? > Solutions? By the way, Optel is my cable modem provider. > > THANKS, > -Dave -- ------------------------- Lawrence Baldwin Protocol Scientist 678-624-0924 http://www.mynetwatchman.com/about.htm - I'm under attack, now what?
Technical Details
Message-ID:
<3A7F7266.B06A04CC@mynetwatchman.com>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-04!supernews.com!xfer13.netnews.com!netnews.com!cpk-news-hub1.bbnplanet.com!news.gtei.net!newsfeed.atl!news3.atl.POSTED!not-for-mailReferences:
<94Bf6.1733$5s2.61515@wormhole.dimensional.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 113850,eb550c41b41f5182 X-Google-Attributes: gid113850,public X-Google-Thread: 1122a6,20d8aef3c030d409,start X-Google-Attributes: gid1122a6,public X-Google-ArrivalTime: 2001-02-05 19:41:37 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-04!supernews.com!xfer13.netnews.com!netnews.com!cpk-news-hub1.bbnplanet.com!news.gtei.net!newsfeed.atl!news3.atl.POSTED!not-for-mail Message-ID: <3A7F7266.B06A04CC@mynetwatchman.com> From: Lawrence Baldwin <baldwinlSPAMMENOT@mynetwatchman.com> X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.dcom.modems.cable,bellsouth.net.support.adsl Subject: Re: BIZARRE tcp/ip problem ATTN: Navas/Swit References: <94Bf6.1733$5s2.61515@wormhole.dimensional.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 132 Date: Mon, 05 Feb 2001 22:41:26 -0500 NNTP-Posting-Host: 208.61.191.103 X-Trace: news3.atl 981430887 208.61.191.103 (Mon, 05 Feb 2001 22:41:27 EST) NNTP-Posting-Date: Mon, 05 Feb 2001 22:41:27 EST