WORKGROUP - Cannot See all computers on some machines

[Mark Welsko]

I Have a workgroup network running at home with four computers on it.
(2) XP Pro
(1) XP Home
and (1) Unix based Snap Server

Recently on one of the XP pro computers all workgroup computers dropped off
window for view workgroup computers. I can still ping all other computers
on the network.

From other XP Pro machine I can See all network computers including the XP
Pro that lost connectivity. If I try to access the first XP Pro machine I
get an error back :

"\\Computer1 not Accessible. You might not have permisssions to use this
network resource. Contact Net admin . . The network path was not found"

I have TCP/IP installed and configured DHCP on all machines and network
connections connected through LAN side of Symantec Firewall Hardware - all
on same network and subnet
Microsoft Client and file share installed
All machines configured Netbios over TCP/IP

Tried adding NetBEUI protocol - did not work
Tried adding NWLink Netbios and it worked for awhile now doesn't seem to
work.

No DNS, WINS, or Nameserver
Workgroup name is identical on all machines.

I have a shortcut on my desktop by IP address to XP(2) from XP(1) that works
fine.

Why can't windows see the other computers? Does anyone have any ideas that
may help?

 

[Haus]

Hello
By installing the NWLink IPX/SPX you should be able to hit all puters with
or without the firewalls on.
Along with Client For MS Network, File and Print Sharing, Internet Protocol
TCP/IP

http://www.practicallynetworked.com/sharing/xp/addxp.htm

 

[Mark Welsko]

Thanks Haus, I agree but it is not working and is driving me nuts.

Here's some additional info:

If I open a remote desktop connection from the XP(1) machine (problem
machine) to the XP(2) machine it is accepted, I close the connection and for
a few minutes I can then access the XP(1) machine from the XP(2) machine .
After a few minutes of idle time the connection is lost and I get the same
error as before again.

I am not running any software firewalls only a hardware firewall with NAT at
my Internet connection point.

 

[Ron Lowe]

Thanks Haus, I agree but it is not working and is driving me nuts.

Here's some additional info:

If I open a remote desktop connection from the XP(1) machine (problem
machine) to the XP(2) machine it is accepted, I close the connection and for
a few minutes I can then access the XP(1) machine from the XP(2) machine .
After a few minutes of idle time the connection is lost and I get the same
error as before again.

I am not running any software firewalls only a hardware firewall with NAT at
my Internet connection point.

Hmm, I suspect a netbios name resolution problem.
(NetBIOS broadcast it the only name resolution method you are using.)

0 ) Remove all the spurious protocols you installed.
They just complicate the issue.
Leave only TCP/IP on all machines.

1) On each machine, attempt to ping the other by both IP address and name.
eg:

ping 192.168.0.1
ping otherpc

Report back what works and what doesn't.

If ping-by-IP-address works, but pinging the name fails,

2) report the exact error message.

3) Re-check NetBIOS-over-TCP/IP is enabled on all machines.

4) Ensure the XP firewall is disabled on the LAN connection on all machines.

5) Go to a command prompt and do an 'ipconfig /all' on each machine,
and report the 'Node Type' on each machine.

 

[Mark Welsko]

Ron,

Thanks, prior to your mail I disabled all protocols except TCP/IP (Except my
VPN Service- see below) based on info from link in Haus's reply. I verified
NETBIOS over TCP/IP on all machines and still had problems. I could Ping by
IP (never tried by name) it worked.

I just tried ping by IP again and name both worked 100%. The only
difference on the machines was a "Symantec VPN Client" service installed on
the machine withthe problem. I disabled it and it looks like everything is
now working.

The problem surfaced the other day when I patched the machine to XP-SP1. It
looks like there may be some incompaatability between the SP and Symantec?

Both machines reported Node type as hybrid. The machine having problems
listed IP routing as YES, The machine that was not having problems reported
IP routing as NO

Thanks for the help!


EDITED SEE THREAD ABOVE

 

[Ron Lowe]

Ron,

Thanks, prior to your mail I disabled all protocols except TCP/IP (Except my
VPN Service- see below) based on info from link in Haus's reply. I verified
NETBIOS over TCP/IP on all machines and still had problems. I could Ping by
IP (never tried by name) it worked.

I just tried ping by IP again and name both worked 100%. The only
difference on the machines was a "Symantec VPN Client" service installed on
the machine withthe problem. I disabled it and it looks like everything is
now working.

The problem surfaced the other day when I patched the machine to XP-SP1. It
looks like there may be some incompaatability between the SP and Symantec?

Both machines reported Node type as hybrid. The machine having problems
listed IP routing as YES, The machine that was not having problems reported
IP routing as NO

Thanks for the help!

There's certainly an incompatability between me and Symantec.

But how applying SP1 would affect the VPN client, I don't know.
I suppose it's possible that changing the ground under it's feet has broken
it.
You could try un-installing then re-installing the VPN software.

But since disabling it fixes the problem, then you probably need to
see if Symantec support has any suggestions.

The node type is OK.