Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WAN not showing in Network Neighborhood

Status
Not open for further replies.

RDSKC

Technical User
Jun 3, 2002
28
US
We have three remote offices, set up identically, a server (NT4 wks, svc pk6, dual NICs, one for LAN, one for WAN) each LAN has about 12 - 15 workstations with local access only, the WAN is routed to our main office(PRIME)NT4 svr. the server at site 1 shows only the LAN in Network Neighborhood, sites 2, 3, and the main office (PRIME) show their respective LANs and the servers for the other sites except site 1! However, we can ping, site 1, site 1 can ping everybody else, and we can even map to shared resources across the WAN, at this point the only problem appears to be the WAN just not visible in NN at site 1! We are logging in to the WAN at site 1, because we have have Norton Corporate antivirus that loads/updates only with successful logon, and if we turn off the router at site 1, we get the "no Domain Controller..." message. any ideas will be appreciated!
 
If I followed correctly, site1 is not visible to anyone execpt those residing at site1. Sounds like a WINS replication issue (assuming you are using WINS).

I wasn't entirely clear if the server at site1 was the server that was multi-homed or not, but you might check the routing table there as well.

I have had problems with NT4 routing on a multi-homed machine before. When a packet arrived on an interface, it wasn't always going out on the same interface it arrived on. There seemed to be no reason for this. Ultimately I had to add static routes to correct the issue until I was able to remove the second NIC entirely (which of course completely resolved the issue).
 
thank you! it turned out to be WINS issue! it seems that at site1, they have a second box with 2 nics, and WINS was not set up on the WAN NIC. Evidently, if one PC doesn't have WINS set up, then it doesn't work on the other PC either.

Thank you for your reply!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top