Network Neighborhood - WAN connections can not connect to Remote

[tekieVB]

I have a customer running NW5.1 SP5 with about 20 servers and one directory tree. Here is a problem I think with the (Cisco) router config at two remote locations. I am not able to get onsite to help the customer, and I am having to rely on what they are telling me.
They can browse NN seeing all servers and volumes. However, if they try to open one of the volumes thru NN it fails stating the volume has been moved/not available. They can logon to the local servers but not remote servers, they have no DNS setup so I am sure they are seeing the objects in NN via (IPX) and NDS replication on the local servers. The servers themselves are not showing any problems according to the customer.
Is this making sense to anyone? I am not sure if my explanation is clear enough.

Any ideas or help would be appreciated.

Thanks,
JB

 

[terry712]

do they have slp set up

 

[tekieVB]

I am not really sure - it does not affect other remote wan connections, just the latest two that they have brought online.

 

[terry712]

i dont put a lot of faith in NN

is there a server at each of these remote sites or only clients

if there are servers - do the servers see each other
do they see each other over ip
type display slp services - do they see the servers

test ipx
display servers - so they see each other

at server if they do display slpda
does it find it

at client
slpinfo /all
is it finding it

 

[tekieVB]

I just wanted to update this with what the problem actually was.

The customer had recently had another company come in and change the network configurations at all of their remote routers so that they did not bridge but actually routed.

The customer had not changed the IPX network numbers at two of the remote sites and they both matched with the HQ IPX network number.

Of course they left that information out. But problem resolved and everything now works.

 

[terry712]

kinda big omission on their part

good to see all is well