Windows 2000

[shannonlapekas]

I have a Windows 2000 server at a remote location. It is connected to this facility by a T1 line. It can see the servers located at the other facility but I can not map drives to the other servers on the network. On the main server I am not seeing this server listed in the available computers. I can see the remote server from the main server though when I ping that servers ip address.

Does anyone have any thoughts as to why I can not map to the drives on this server?

 

[ReddLefty]

If you have routers (which I'm pretty sure you do) between both, you can have multiple issues of why you cannot map a network drive.

Let's presume that both your routers do not act or have any firewall capabilites, which means all IP traffic flows to and fro.

You need a WINS server at each end to see the names of the other computers. Otherwise, you will only be able to see machines with their IPs.

or

You need to add all the addresses in the DNS at both ends once more (if your not using a DHCP).

WINS is usually the easiest solution... less maintenance.

 

[shannonlapekas]

I have 4 other machines over there that do have their drives mapped to the network without any problems. I have WINS set up at both ends. The 4 other machines are running XP Pro. I don't think that it could be a router configuration problem since the other machines are visible to the network.

 

[ReddLefty]

Ok, then many factors may still be at play, but I need to make sure I understand your network fully.

Let's put some names on the situation.

SITE A: Has a W2K server with WINS, DNS and clients
SITE B: Has a W2K server with WINS, DNS and 4 XP clients.


Site B clients map drives to Site A Server
Site A clients can't map drives to Site B server.

is this correct?

 

[shannonlapekas]

That is all correct except that the Site A clients can map to the Site B server. The new Site B server that was installed today can not map to the Site A server. The remaining Site B computers (client XP machines) can map to the Site A server.

 

[ReddLefty]

So only the servers can't map to each other?

If so, it sounds like DNS trouble.

- You may want to check both DNS to make sure the right IP's are listed

- Make sure your WINS hosts the right DOMAIN names in it's database with the right server

Maybe a quick fix is to add the servers to the LMHOSTS file.

C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS (edit or create)
add the line:
SERVER1 10.0.0.1 #PRE #DOM:<domain name>

then open a DOS box and type NBTSTAT -R <-(capital R)

Do the same for the other server but with the name and IP address of SERVER2.

 

[shannonlapekas]

How do I add the line to the lmhosts file? It looks like to me when you open it in notepad it is only examples of what it could look like.

 

[Jpoandl]

I agree there is most likely something misconfigured on the new Windows 2000 server.

Check you IP settings. WINS can be left out of the picture in a pure Windows 2K/XP environment. I would consentrate more on the DNS side of things.

If your still having trouble, exlpain you domain environment.

Also, check the event viewer of the problematic Windows 2000 server. I bet there is a warning or error that will lead to the resolution to this problem.

_Hope this helps..

Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[ReddLefty]

Don't use the LMHOSTS.SAM (sample). Create a new one called LMHOSTS (no extention). Carefull when you use notepad cause it adds a .TXT extention to it. You must rename it afterwards.

Take this line and paste it into the LMHOSTS file:

SERVER1 10.0.0.1 #PRE #DOM:<domain name>

In SITE A server, place SITE B's server name, IP and domain in the LMHOSTS file.

Do the same on SITE B but using SITE A server information.

Then run NBTSTAT -R <-Capital R on both servers in a dos windows.

Then try to ping SERVERA and PING SERVERB.

 

[shannonlapekas]

I am getting the following two errors in the event viewer:

Event 10035 This host can not be ACS since the Active Directory has not been properly configured via the QoS ACS management console. Please configure the subnets via the QoS ACS mangement console.

Even 10047 QoS RSVP has failed to find any interfaces with traffic control enabled. Install QoS traffic control services via Network connection

 

[ReddLefty]

If you do not need the Quality of Service management, you can remove it. It's in your network services... but if you can ping your servers, it's odd that this would have anything to do with it, but I don't know QoS well enough to say for sure.