One Vista PC can ping the other, but not back

[Wessel Troost]

Two Vista PC's are connected in a network. The first PC has 2 network
interfaces, one of which is connected to the internet. The internet
connection is shared with a second PC, connected via a crossover
ethernet cable.

Internet ---> PC1 --> crossover cable --> PC2

The 2nd PC can browse the internet, it can ping the first PC
(192.168.0.1) and it can access shares on the first PC.

But the 1st PC can't ping the second PC! It can't access shares on
that PC either, and when I tracert to the 2nd PC, it shows "tracing
route to PC2.mshome.net". Note the weird mshome.net postfix. Both
PC's are in a workgroup which is not called mshome.net.

Anyone has a clue why the 2nd PC can ping the 1st PC, but not the
other way round?

 

[Chuck [MVP]]

Two Vista PC's are connected in a network. The first PC has 2 network
interfaces, one of which is connected to the internet. The internet
connection is shared with a second PC, connected via a crossover
ethernet cable.

Internet ---> PC1 --> crossover cable --> PC2

The 2nd PC can browse the internet, it can ping the first PC
(192.168.0.1) and it can access shares on the first PC.

But the 1st PC can't ping the second PC! It can't access shares on
that PC either, and when I tracert to the 2nd PC, it shows "tracing
route to PC2.mshome.net". Note the weird mshome.net postfix. Both
PC's are in a workgroup which is not called mshome.net.

Anyone has a clue why the 2nd PC can ping the 1st PC, but not the
other way round?

Wessel,

Asymmetrical access, or pinging, is generally a personal firewall problem. What
personal firewall does each use?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
<http://nitecruzr.blogspot.com/2006/12/windows-xp-and-vista-on-lan-together.html#Security>
http://nitecruzr.blogspot.com/2006/12/windows-xp-and-vista-on-lan-together.html#Security

When you say "can't ping", what exact error message are you getting, or problem
are you seeing?
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html

You could look at logs from "browstat status" and "ipconfig /all", from each
computer, and diagnose the problem. Read this article, and linked articles, and
follow instructions precisely (download browstat!) (note use of the command
window in Vista):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

--
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.

 

[Wessel Troost]

Asymmetrical access, or pinging, is generally a personal firewall problem. What

personal firewall does each use?

Both PC's use Windows Firewall only, with NOD32 as the virus scanner.
Disabling either Windows Firewall or NOD32 virus scanner does not make
a difference.

When you say "can't ping", what exact error message are you getting, or problem
are you seeing?

It gives a timeout. A traceroute gives a timeout too (* * *).

You could look at logs from "browstat status" and "ipconfig /all", from each
computer, and diagnose the problem. Read this article, and linked articles, and
follow instructions precisely (download browstat!) (note use of the command
window in Vista):

Ping is still a network layer below the SMB protocol, so I assume if
you can't ping, then checking the browser is a step too far.

Ipconfig shows what you'd expect it to: 192.168.0.1 for the LAN
interface, and a private IP handed out by the DHCP server in the DSL
modem for the internet connection.

As an additional problem Vista kept doing discovery on the network
interface connected to the internet, even though I disabled all
protocols except IP4 on that adapter. The network neighbourhood would
display the ADSL modem but not the other PC. (I've checked the cables
by disconnecting them, and the adapter I think is Internet becomes
disabled when I unplug the internet cable.) The ADSL modem got
confused by the Vista discovery, resolving DNS queries to the wrong
address. A reboot of the ADSL modem would restore Internet
connectivity.

Removing Internet connectivity altogether does not allow PC1 to ping
PC2.
After each reboot, PC1 insists that the twisted ethernet cable
connection is a "public network", even tho I change it to private
every time.

Reverting PC1 to Windows XP resolves the problem. Windows XP can ping
PC2, it can access shares on PC2, and it does not confuse the ADSL
modem.

Is it worth trying to get Vista to work, or is not capable to perform
the router job XP did with the lovely "Share Internet Conenction"
switch?

 

[Chuck [MVP]]

Both PC's use Windows Firewall only, with NOD32 as the virus scanner.
Disabling either Windows Firewall or NOD32 virus scanner does not make
a difference.

It gives a timeout. A traceroute gives a timeout too (* * *).


Ping is still a network layer below the SMB protocol, so I assume if
you can't ping, then checking the browser is a step too far.

Ipconfig shows what you'd expect it to: 192.168.0.1 for the LAN
interface, and a private IP handed out by the DHCP server in the DSL
modem for the internet connection.

As an additional problem Vista kept doing discovery on the network
interface connected to the internet, even though I disabled all
protocols except IP4 on that adapter. The network neighbourhood would
display the ADSL modem but not the other PC. (I've checked the cables
by disconnecting them, and the adapter I think is Internet becomes
disabled when I unplug the internet cable.) The ADSL modem got
confused by the Vista discovery, resolving DNS queries to the wrong
address. A reboot of the ADSL modem would restore Internet
connectivity.

Removing Internet connectivity altogether does not allow PC1 to ping
PC2.
After each reboot, PC1 insists that the twisted ethernet cable
connection is a "public network", even tho I change it to private
every time.

Reverting PC1 to Windows XP resolves the problem. Windows XP can ping
PC2, it can access shares on PC2, and it does not confuse the ADSL
modem.

Is it worth trying to get Vista to work, or is not capable to perform
the router job XP did with the lovely "Share Internet Conenction"
switch?

Here are the known causes of "cannot ping" (dropped packets, not name resolution
problem):
1) Hardware - defective cabling, router, network card.
2) IP setting - wrong subnet or IP address.
3) Firewall - misconfigured or overlooked firewall can block ping packets.
4) LSP / Winsock - corrupt LSP / Winsock stack can misdirect ping packets.

#1 is always a possibility - either cabling, network card, or router can cause
asymmetrical traffic.

#2 should be symmetrical, so that's out.

#3 is generally a problem with pings at the network level. Windows Firewall
should be disablable, with no penalty. NOD32 possibly contains an antiworm
component that will block SMBs (browser etc), but shouldn't have any effect on
pings.

#4 is a possibility under Vista. LSP / Winsock is still part of the network
stack.
<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

Now, your symptom of "PC1 insists that the twisted ethernet cable connection is
a "public network"" could possibly be a known problem, and could cause confusion
in Windows Firewall. Which "twisted Ethernet cable" are we discussing here?
<http://nitecruzr.blogspot.com/2007/09/changes-in-internet-explorer-security.html>
http://nitecruzr.blogspot.com/2007/09/changes-in-internet-explorer-security.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.

 

[Mick Murphy]

http://www.lytebyte.com/2007/02/21/...connection-with-another-computer-using-vista/

The above should set you on the right path!

 

[Wessel Troost]

First of all thanks for your answer. I was kinda upset about not being
able to get a simple network right and your list of causes gives me
something to work on.

#1 is always a possibility - either cabling, network card, or router can cause
asymmetrical traffic.

I'll swap the NIC when I'm back.

#4 is a possibility under Vista. LSP / Winsock is still part of the network
stack.

What would fix this? A reinstall of Vista?

Now, your symptom of "PC1 insists that the twisted ethernet cable connection is
a "public network"" could possibly be a known problem, and could cause confusion
in Windows Firewall. Which "twisted Ethernet cable" are we discussing here?

It's the kind of twisted wire that connects two ethernet cards without
a hub or router in between. Are there known issues with tiwsted
ethernet cables?

 

[Chuck [MVP]]

First of all thanks for your answer. I was kinda upset about not being
able to get a simple network right and your list of causes gives me
something to work on.

I'll swap the NIC when I'm back.

What would fix this? A reinstall of Vista?

It's the kind of twisted wire that connects two ethernet cards without
a hub or router in between. Are there known issues with tiwsted
ethernet cables?

There were a number of tools to repair LSP / Winsock, under Windows XP and
previous.
<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

Having read that article, I believe that only Steps 7b, and 9 - 11, will be
applicable. It's possible that the "netsh" command in Windows Vista, will be
more effective than it was in Windows XP. I'm researching LSP / Winsock under
Windows Vista this week.

In terms of the Ethernet cable, you're mentioning a CROSS-OVER cable. If you
have connectivity from one computer to another, simply not both ways, your
cross-over cable is probably working fine. Here's my instruction for using a
cross-over cable.
<http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html>
http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html

And don't be upset with yourself for being upset. Networking isn't simple -
even 2 computers offer numerous opportunities for making mistakes. If you want
to get a feel for how complex it can be, read my tutorial.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.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.

 

[Wessel Troost]

The problem has been resolved now-- I'll post the solution in case
anyone encounters a similiar problem.

The solution was to uninstall the NOD32 virus scanner. After that,
everything worked fine.

 

[Chuck [MVP]]

The problem has been resolved now-- I'll post the solution in case
anyone encounters a similiar problem.

The solution was to uninstall the NOD32 virus scanner. After that,
everything worked fine.

If you read the networking forums, you'll find that the single most common cause
of the problems is problems with personal firewalls or virus protection. Good
job. Thanks for letting us know.

--
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.