Diagnosing connection issue

[edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org (edwardp)]

edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org wrote:
> Bill Bogstad wrote:
>    
>> On Tue, Feb 15, 2011 at 6:22 AM,<edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org>   wrote:
>>
>>      
>>> I have not as yet tried a traceroute when this occurs, but will do so the next time.   I have not experienced this same issue on my laptop using a wireless connection.
>>>
>>> But even when this occurs, /if/ the problem is further downstream, past the cable modem, at least the modem and router status pages should have no trouble coming into the browsers and they are not even doing that when this problem occurs, yet they ping fine during all this.
>>>
>>>        
>> You didn't say that before.  So if you ping the modem and router they
>> are "fine"; but accessing their web pages fails?  Try doing a simple
>> "telnet ipofdevice 80" to bypass DNS or web browser issues and see if
>> you can get a connection to the devices web pages.   You can even try
>> sending HTTP commands to the device via telnet and see if you get
>> results.   If this works, but your web browser can't connect to the
>> devices web pages then it is beginning to sound like it is a problem
>> with
>> your local system software.
>>
>> Bill Bogstad
>>
>> P.S. What do  you mean by fine for ping by the way?   Try a ping flood
>> "ping -f" as well.  Also you might try getting Matt's traceroute
>> (mtr).  It's a screen based version
>> of traceroute can be very nice for diagnosing network connectivity
>> issues (which it might not be in this case).
>>
>>      
>
> Ping fine = goes through without any packet loss, immediate response.
>
> Traceroute also went through during an "outage".
>
> Did not try telnet, but I have now disabled IPv6 on the Linux (via
> sysctl.conf) side to see if that makes any difference.
>    

The problem just occurred again, on the Windows side, telnet is not 
included with Vista, but ftp was.  ftp'ing to both the router and modem 
while this occurred resulted in "connection refused" from both, yet when 
I launched mail/news in SeaMonkey, the IMAP connection to the mail 
server went through fine, so I could send this message.  In the middle 
of typing this message though, the web browser woke up again.  So if FTP 
indicated "connection refused" and IMAP worked, then the connection was 
still working, but it was the web browser itself that froze and this is 
with IPv6 also disabled under Windows.

So the question remains unanswered:  If it /is/ the software, why with 
two totally different operating systems?



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 110216-1, 02/16/2011
Tested on: 2/16/2011 7:25:27 PM
avast! - copyright (c) 1988-2011 AVAST Software.
http://www.avast.com