Diagnosing connection issue

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

Tom Metro wrote:
> edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org wrote:
>> What remains a mystery...I could not call up the modem
>> and router status screens in the browsers using their IP addresses
>> (no DNS used), yet both of them sent back immediate ping responses...
> While unlikely, especially with two appliances involved, it is possible
> that the web interface on them references public URLs, say for images,
> that are then being blocked by DNS or general WAN connectivity issues.
>
> You can inspect the returned HTML on those devices to see if that is the
> case.
>
> There are other possibilities, like proxy settings, or browser plugins
> that might "phone home" to a public site on each connection request. But
> with multiple browsers and OSs, this is even more unlikely.
>
> Web access filtering built-in to a router, if it depends on a public
> site to look up information about a URL, might also explain it. But
> didn't you say you had this problem both before and after switching 
> routers?
>
> It may be time to break out a packet sniffer and see what's really 
> going on.
>
>   -Tom

Yes, before and after changing routers, as well as the on-board LAN in 
the computer as well as a new NIC (PCI) that I installed last night.  I 
did not enable blocking in the old router (Linksys) and blocking (both 
sites and services) is disabled by default in the Netgear.  I also 
looked in the Netgear's log for this week (going back to last Sunday) 
and nothing indicates a problem.


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