Error Msg: "<WORKGROUP> is not accessible. The network path was not found."

[Rediranch]

Anyone come across this error message?

Two WIN2K Pro PC's, both have shares setup, running over a
DLINK router.

the problem PC - named Aproblem.
the PC with no problem - PC B.

Both Aproblem and PC B can ping each other, themselves
(127.0.0.1), and the router.

Both have Internet access, through the router.

Both have shares setup.

Both have the same user account that I'm logging in with.
Also changed the admin login passwords to be the same.

I verified that both have the same Workgroup.

Aproblem PC can't even see itself in "My Network Places",
I get the error message above (see subject). PC B CAN see
both PC's in "My Network Places", and also look at the
shares that are on each machine.


What I've tried:

I have disconnected them from the router, and hooked them
into a passive hub, with no change.

I've booted both into Safe Mode with Networking (to check
for software interferring), with no change.

Thought it might be an MS Patch causing problem, so I
reinstalled Win2K Pro on Aproblem PC, with no change.

I've swapped out the network card in Aproblem PC, with no
change.

I was able to use the network in order to create a Ghost
image of AProblem PC, across to PC B, so the hardware
seems fine.


Thanks

 

[Michael Johnston [MSFT]]

Make sure you disable any firewall software on the machine. Make sure you enable netbios over TCP/IP on both machines.
Make sure the subnet masks match and the machines are logically on the same subnet. Hard code the network speed and
duplex settings on the NICs in both machines.

Can you connect to PCb from the problem machine by going through Start>Run \\machinename\sharename or \\ip\\share\?

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Anthony Perona]

How are you resolving NetBIOS names on Aproblem? This is done by broadcast
first, then the LMHOSTS file. Try adding PC B's IP address to the LMHOSTS
file and make sure that you have NetBIOS over TCP/IP enabled on Aproblem.

 

[Treebeard]

Anyone come across this error message?

Two WIN2K Pro PC's, both have shares setup, running over a
DLINK router.

the problem PC - named Aproblem.
the PC with no problem - PC B.

Both Aproblem and PC B can ping each other, themselves
(127.0.0.1), and the router.

Both have Internet access, through the router.

Both have shares setup.

Both have the same user account that I'm logging in with.
Also changed the admin login passwords to be the same.

I verified that both have the same Workgroup.

Aproblem PC can't even see itself in "My Network Places",
I get the error message above (see subject). PC B CAN see
both PC's in "My Network Places", and also look at the
shares that are on each machine.


What I've tried:

I have disconnected them from the router, and hooked them
into a passive hub, with no change.

I've booted both into Safe Mode with Networking (to check
for software interferring), with no change.

Thought it might be an MS Patch causing problem, so I
reinstalled Win2K Pro on Aproblem PC, with no change.

I've swapped out the network card in Aproblem PC, with no
change.

I was able to use the network in order to create a Ghost
image of AProblem PC, across to PC B, so the hardware
seems fine.


Thanks

Do you see anything strange in:
Control Panel/Administrative Tools/Local Security Policy/Local Policies/User
Rights Assignments/Access This Computer From The Network ?