Problems seeing machines over WAN Link - Error 53

[3n1]

I am having trouble seeing machines over a WAN Link. I am trying to install two new servers in a Windows 2003 network. I didn't setup this network, and this is the first time I've worked on it. It is located in two different cities connected by a T1 WAN Link. I have setup a new server as a Domain Controller and I have also setup the server as their primary DNS for their network. This machine is also the DHCP server for the local network in what we'll call “City A” (137.10.0.0). Everything works fine locally, and people are resolving names, attaching to shares and peacefully processing. However, the remote network(137.101.0.0) in “City B”, across the WAN link cannot see the new server. The new server's name is DC1-2k3, and the other two servers on that network are named 00SERVER and APPLICATIONS. When I physically go to the remote network(137.101.0.0) in city B, I can ping and resolve the name of any of the servers in City A. DC1-2k3, APPLICATIONS, and 00SERVER all respond to a ping of either their name or IP address. However, if I try and attach to a share on the new server, DC1-2K3, I am told that I cannot see the server. I can attach fine to shares on either of the other servers in City A from City B. If I do:

net view \\DC1-2K3

I get an error 53. When I do a “net view” of any of the older City A machines from the City B network I also have trouble. It is just the two older servers in City A that I can see. I checked for HOSTS files one the machines, and there were none. I noticed that the DHCP server in City B (137.101.0.0 network) was handing out a WINS server address, which corresponds to the 00SERVER in City A. I thought this was my problem, so I setup my new server (DC1-2K3 137.100.10.6) with the WINS information and rebooted. I then had entries in my WINS database that reflected that there was a machine at 137.100.10.6 that was named DC1-2K3. Unfortunately, I still can't see any resources on the new server in City A, from City B. I am completely unfamiliar with WINS servers, so i thought this was my problem, but then I did this net view

net view 137.100.10.6

and I still got an error 53. I cannot map to the new server or “net view” it via it's IP address OR it's name. The guy told me that “they had a real hard time” getting the two networks to see each other. The guy wants me to clean up his network and fix any problems that I find, and I am wondering what this problem could be. It is clearly not just name resolution, as my DNS is working fine and I can ping any machine by it's name. If I configure a machine in City B without a WINS server, it can't resolve any local names on the City A network, even though it resolves Internet names correctly. I am asking for any help anybody can give. I am at a loss.

This is the layout of the network.

City A -137.10.0.0 class B
with three servers DC1-2k3(windows 2003 R2 server) @ 137.100.10.6, 00SERVER(windows 200 Server) @ 137.100.10.5 and APPLICATIONS(windows 203 Server) @ 137.100.10.185

City B - 137.101.0.0 class B with one server 01SERVER(Windows 2000 Server) @ 137.101.10.5

 

[3n1]

I failed to note that the T1 wan link is connected by a Lucent Superpipe 155 on each end.

 

[3n1]

btt?

 

[kmcferrin]

I am unfamiliar with the Lucent device in question, but I'd be looking at 2 or 3 things here.

1. Is there a firewall somewhere in between that is blocking traffic?

2. I'm assuming that your domain controller is running DNS for your environment. Is there a DNS server at each site? If not, are the systems at both sites at least configured to use the same DNS server? Also, make sure that each DNS server has root hints installed so that it can query Internet DNS servers. AD depends on DNS, and if DNS is down or misconfigured then AD won't work correctly. Which means authentication won't work directly. Which makes mapping drives difficult.

3. I just looked up the Lucent Superpipe, and it looks like it's basically a router. I didn't see anything that indicated firewall functionality, so the next question is about the T1. Is it a direct point to point connection, frame relay, or do you have a T1 Internet connection at each site? Are the routers configured to block any traffic?

 

[3n1]

Thanks for the response.

No firewall between the point to point T1 connections nor the servers & workstations at either site. The only firewall on the network is at City A between the Internet & the switch.

There is not a DNS server at both sites, only in City A. all the workstations at City B are configured to use the DNS server at City A & all resolve internet names correctly. The DNS server also happens to be the server that we are trying to map to. Name resolution appears to be working correctly. We have no problem mapping to shares or browsing the network from within the same site, only across the T1.

I'm not familiar with the Superpipe either but looking through the configuration I can't see anything that indicates any traffic being blocked. Then again I don't see anything that proves otherwise.