7 replies
by mckaytech
Hmmm... not much information to go on but usually the best place to start is by testing network connectivity and you can test that by trying to ping, first by IP address and then by name from BDC to PDC and PDC to BDC. Also, you might try pinging from a workstation to the PDC and from that same workstation to a BDC and see what happens.
If that works okay, then try to map a share from one to the other. If that also works, then something very, very strange is going on.
One other piece ofinformation that would be useful is to know whether these servers are all on the same subnet or whether there are WAN links involved.
regards!
paul
by jhall
by lewey04
Well not much information to go on but sounds like it might be a name resolution problem. I would check to see if you can ping the PDC by address from the BDC's. If you can ping by address then you know it is a name resolution problem and you can troubleshoot DNS and/or WINS.
Good luck and send more detail if you still can't figure out the problem.
by jhall
by ronnonf
The following is assuming that your PDC has an ip address hard coded (not as DHCP client)
The following steps should be done on the BDC. Create/edit the LMHOSTS file. This can be found in \\System32\Drivers\Etc. The file needs to be calledLMHOSTS not LMHOSTS.sam or LMHOSTS.txt.
Add the following line:
#PRE #DOM:
Save the file. Open a cmd window and execute the following command "nbtstat -R"
Try it (ping by name, net view, start \\
by jhall
by jhall
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending