I may have the same problem, no fix or solution yet. The computer connects
either via wireless or wired to a network, and DHCP, DNS, and at least ICMP
protocols seem to be working. I can ping hosts by name, and have tried
successfully with packet sizes up to 10000 bytes. I enabled Windows network
"discovery", and the network browser shows lots of printers and computers in
the "neigborhood", so netbios or netbuei (wheatever it is) seems to work
fine. I'm guessing UDP is working by TCP not, but not sure of that.
On the wired connection I can run tcpdump on the gateway router/computer,
and see lots of ordinary-looking DNS, bootp, and other queries going out, but
I don't think I'm seeing any TCP packets leaving the VIsta box, either when I
try to web-browse using IE or FIrefox (installed using a USB key). Also have
tried ftp and telnet, both to remote
hosts and hosts running on my local network, and see no outgoing connections.
I've tried to look around and poke at stuff using netsh; in particular I've
tried disabling Windows Scaling using:
netsh interface tcp set global autotuninglevel=disable
but this seems to have no effect. I've tried disabling the firewall and
virus checker, also with no effect. The virus checker was updated as
recently as a week ago (via TCP/IP)
and I ran a full scan with no hits. I've tried disabling/enabling the net
connections, and
anything else I've been able to think of. No joy.
In short, this is not a wireless networking issue, nothing to do with DHCP,
DNS, or other aspects of the basic network functionality, but maybe some
snafu in the tcp stack? Just guessing. I may go looking for a Windows
version of Netcat, since that couldbe used to test connectons using either
udp or tcp.
No idea what changed or might have caused this issue.
Ken, grasping at straws
gt8672 said:
Thanks Chuck - i did the winsock reset to no avail; i can ping major sites
(google cnn etc) and my nslookups work on these sites as well; i am
definitely stumped
Chuck said:
Recently, i have experienced an issue, with no obvious triggering event,
where neither IE or Firefox browsers can connect to the internet. My IM
client works fine.
I am running on a wireless network, but no changes have been made to the FW
or other settings. I have done all of the resolver cache, winsock resets, etc
that I have seen. I can ping other computers on the network and my WAN IP.
nslookups on well know resolve.
Ideas on troubleshooting - how on FW welcome.
Some IM clients don't use DNS, so start with a DNS check.
<
http://nitecruzr.blogspot.com/2006/05/identifying-dns-problem-in-your.html>
http://nitecruzr.blogspot.com/2006/05/identifying-dns-problem-in-your.html
Then go after LSP / Winsock corruption, in detail.
<
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
And look at your MTU setting, targeting any server that you can't connect to
through the browser.
<
http://nitecruzr.blogspot.com/2007/06/determining-mtu-to-single-server.html>
http://nitecruzr.blogspot.com/2007/06/determining-mtu-to-single-server.html
--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.