"A" & "B" can't see each other, all others fine?

  • Thread starter Thread starter Kenneth
  • Start date Start date
K

Kenneth

Howdy,

We have a 5 node peer to peer all Win 2000 Pro net with a
switch.

Two of the systems cannot see each other, but all the other
systems can see, and browse these two "problem" systems.

The two systems having troubles are called "Assist" and
"Server".

If I am on "Server" and attempt to browse to "Assist" I get
the error:

\\Assist is not accessible. The network path was not found.

If I am on "Assist" and attempt to browse to "Server" I get
the error:

\\Server is not accessible. The network path was not found.

If I attempt to ping Assist from Server by name, it displays
the correct IP address, but then times out.

If I attempt to ping Assist from Server by IP address, it
times out.

If I attempt to ping Server from Assist by name or by IP it
responds.

The User & Passwords lists on both systems look fine.

I have moved cables around, and have re-booted both systems
several times.

What should be my next steps...?

Very sincere thanks,
 
Howdy,

We have a 5 node peer to peer all Win 2000 Pro net with a
switch.

Two of the systems cannot see each other, but all the other
systems can see, and browse these two "problem" systems.

The two systems having troubles are called "Assist" and
"Server".

If I am on "Server" and attempt to browse to "Assist" I get
the error:

\\Assist is not accessible. The network path was not found.

If I am on "Assist" and attempt to browse to "Server" I get
the error:

\\Server is not accessible. The network path was not found.

If I attempt to ping Assist from Server by name, it displays
the correct IP address, but then times out.

If I attempt to ping Assist from Server by IP address, it
times out.

If I attempt to ping Server from Assist by name or by IP it
responds.

The User & Passwords lists on both systems look fine.

I have moved cables around, and have re-booted both systems
several times.

What should be my next steps...?

Very sincere thanks,
Click to expand...

Hello again,

It turned out to be a #$%^&* copy of ZoneAlarm that was
running on Assist...

Thanks,
 
Back
Top