Unable to see other computers on my network

  • Thread starter Thread starter Guest
  • Start date Start date
Chuck said:
Dear Chuck

Here is the other half - it wouldn't let me send it all in one go:

OK, Jim,

Now the fun starts.

Both JimTCU and Sue can ping JimsLaptop, but JimsLaptop can't ping itself.

"JIMTCU ping JimsLaptop"

Pinging JimsLaptop [192.168.1.5] with 32 bytes of data:Reply from
192.168.1.5: bytes=32 time<1ms TTL=128Reply from 192.168.1.5: bytes=32
time<1ms TTL=128Reply from 192.168.1.5: bytes=32 time<1ms TTL=128Reply from
192.168.1.5: bytes=32 time<1ms TTL=128

"SUE ping JimsLaptop"

Pinging JimsLaptop [192.168.1.5] with 32 bytes of data:Reply from 192.168.1.5:
bytes=32 time=1ms TTL=128Reply from 192.168.1.5: bytes=32 time=1ms TTL=128Reply
from 192.168.1.5: bytes=32 time=1ms TTL=128Reply from 192.168.1.5: bytes=32
time=1ms TTL=128

"JIMSLAPTOP ping JimsLaptop"

Pinging JimsLaptop [192.168.1.5] with 32 bytes of data:Request timed out.Request
timed out.Request timed out.Request timed out.

So JimsLaptop has a personal firewall or LSP / Winsock problem.
<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/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

But wait - there's more

JimTCU can't see the other 2 computers, in ad-hoc view. Nor can they see it.

Adhoc Browser View

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\JIMSLAPTOP My Dell Laptop

\\SUE Sue's laptop

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\JIMSLAPTOP My Dell Laptop

\\SUE Sue's laptop

And JimTCU can't ping itself, though the others can.

"JIMTCU ping JimTCU"

Pinging JimTCU [192.168.1.3] with 32 bytes of data:Request timed out.Request
timed out.Request timed out.Request timed out.Ping statistics for
192.168.1.3: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
"JIMTCU net view JimTCU"

"JIMSLAPTOP ping JimTCU"

Pinging JimTCU [192.168.1.3] with 32 bytes of data:Reply from 192.168.1.3:
bytes=32 time<1ms TTL=64Reply from 192.168.1.3: bytes=32 time<1ms TTL=64Reply
from 192.168.1.3: bytes=32 time<1ms TTL=64Reply from 192.168.1.3: bytes=32
time<1ms TTL=64

"SUE ping JimTCU"

Pinging JimTCU [192.168.1.3] with 32 bytes of data:Reply from 192.168.1.3:
bytes=32 time=1ms TTL=64Reply from 192.168.1.3: bytes=32 time=1ms TTL=64Reply
from 192.168.1.3: bytes=32 time=1ms TTL=64Reply from 192.168.1.3: bytes=32
time=1ms TTL=64

Which again is either a personal firewall or LSP / Winsock problem, on
JimTCU.And still more.

Sue can't ping itself, though the others can.

"JIMTCU ping Sue"

Pinging Sue [192.168.1.4] with 32 bytes of data:Reply from 192.168.1.4:
bytes=32 time=88ms TTL=128Reply from 192.168.1.4: bytes=32 time=1ms
TTL=128Reply from 192.168.1.4: bytes=32 time=1ms TTL=128Reply from
192.168.1.4: bytes=32 time=1ms TTL=128

"JIMSLAPTOP ping Sue"

Pinging Sue [192.168.1.4] with 32 bytes of data:Reply from 192.168.1.4: bytes=32
time=1ms TTL=128Reply from 192.168.1.4: bytes=32 time=1ms TTL=128Request timed
out.Reply from 192.168.1.4: bytes=32 time=1ms TTL=128

You have 3 computers that can't ping themselves. What do these 3 computers have
in common, besides geographical location?
Dear Chuck

Sorry to be a few days -work and family and things! I have looked at your
references and changed a few settings in Norton, but with intermittent
success. The 3 computers have in common Norton Internet Security, which, I
guess, is the reason they cannot all see each other. What do you think?

Regards, Jim

This sounds like an NIS related problem. Either find the setting(s) that are
lacking, or un install it completely, using all tools provided by Symantec (and
always re boot after). My preference would be the former (we need to learn how
to make it work properly), but my confidence is in the latter.
<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

My guess would be NIS anti worm protection. or maybe it's a Symantec caused LSP
/ Winsock corruption. We have no definitive diagnostic here - but since the
problem is with ping (aka ICMP Echo), it's a layer 3 or 4 problem, ie pretty low
level.
<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

--
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.
 
Chuck said:
On Sat, 22 Sep 2007 20:46:00 -0700, Jim Cranfield

Dear Chuck

Here is the other half - it wouldn't let me send it all in one go:

OK, Jim,

Now the fun starts.

Both JimTCU and Sue can ping JimsLaptop, but JimsLaptop can't ping itself.

"JIMTCU ping JimsLaptop"

Pinging JimsLaptop [192.168.1.5] with 32 bytes of data:Reply from
192.168.1.5: bytes=32 time<1ms TTL=128Reply from 192.168.1.5: bytes=32
time<1ms TTL=128Reply from 192.168.1.5: bytes=32 time<1ms TTL=128Reply from
192.168.1.5: bytes=32 time<1ms TTL=128

"SUE ping JimsLaptop"

Pinging JimsLaptop [192.168.1.5] with 32 bytes of data:Reply from 192.168.1.5:
bytes=32 time=1ms TTL=128Reply from 192.168.1.5: bytes=32 time=1ms TTL=128Reply
from 192.168.1.5: bytes=32 time=1ms TTL=128Reply from 192.168.1.5: bytes=32
time=1ms TTL=128

"JIMSLAPTOP ping JimsLaptop"

Pinging JimsLaptop [192.168.1.5] with 32 bytes of data:Request timed out.Request
timed out.Request timed out.Request timed out.

So JimsLaptop has a personal firewall or LSP / Winsock problem.
<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/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

But wait - there's more

JimTCU can't see the other 2 computers, in ad-hoc view. Nor can they see it.

Adhoc Browser View

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\JIMSLAPTOP My Dell Laptop

\\SUE Sue's laptop

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\JIMSLAPTOP My Dell Laptop

\\SUE Sue's laptop

And JimTCU can't ping itself, though the others can.

"JIMTCU ping JimTCU"

Pinging JimTCU [192.168.1.3] with 32 bytes of data:Request timed out.Request
timed out.Request timed out.Request timed out.Ping statistics for
192.168.1.3: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
"JIMTCU net view JimTCU"

"JIMSLAPTOP ping JimTCU"

Pinging JimTCU [192.168.1.3] with 32 bytes of data:Reply from 192.168.1.3:
bytes=32 time<1ms TTL=64Reply from 192.168.1.3: bytes=32 time<1ms TTL=64Reply
from 192.168.1.3: bytes=32 time<1ms TTL=64Reply from 192.168.1.3: bytes=32
time<1ms TTL=64

"SUE ping JimTCU"

Pinging JimTCU [192.168.1.3] with 32 bytes of data:Reply from 192.168.1.3:
bytes=32 time=1ms TTL=64Reply from 192.168.1.3: bytes=32 time=1ms TTL=64Reply
from 192.168.1.3: bytes=32 time=1ms TTL=64Reply from 192.168.1.3: bytes=32
time=1ms TTL=64

Which again is either a personal firewall or LSP / Winsock problem, on
JimTCU.And still more.

Sue can't ping itself, though the others can.

"JIMTCU ping Sue"

Pinging Sue [192.168.1.4] with 32 bytes of data:Reply from 192.168.1.4:
bytes=32 time=88ms TTL=128Reply from 192.168.1.4: bytes=32 time=1ms
TTL=128Reply from 192.168.1.4: bytes=32 time=1ms TTL=128Reply from
192.168.1.4: bytes=32 time=1ms TTL=128

"JIMSLAPTOP ping Sue"

Pinging Sue [192.168.1.4] with 32 bytes of data:Reply from 192.168.1.4: bytes=32
time=1ms TTL=128Reply from 192.168.1.4: bytes=32 time=1ms TTL=128Request timed
out.Reply from 192.168.1.4: bytes=32 time=1ms TTL=128

You have 3 computers that can't ping themselves. What do these 3 computers have
in common, besides geographical location?
Dear Chuck

Sorry to be a few days -work and family and things! I have looked at your
references and changed a few settings in Norton, but with intermittent
success. The 3 computers have in common Norton Internet Security, which, I
guess, is the reason they cannot all see each other. What do you think?

Regards, Jim

This sounds like an NIS related problem. Either find the setting(s) that are
lacking, or un install it completely, using all tools provided by Symantec (and
always re boot after). My preference would be the former (we need to learn how
to make it work properly), but my confidence is in the latter.
<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

My guess would be NIS anti worm protection. or maybe it's a Symantec caused LSP
/ Winsock corruption. We have no definitive diagnostic here - but since the
problem is with ping (aka ICMP Echo), it's a layer 3 or 4 problem, ie pretty low
level.
<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

Jim,

Besides the above issues, consider this symptom of which we're just starting to
explore the details.
<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.
 
Back
Top