Recently we replaced a BDC on the network with a new HP Server. When we installed it into the domain we used the same name as the old server. (we did remove and recreate the computer account as should be done) Since we did this we have been experiencing a crazy problem. TCP/IP communication between the PDC and this BDC function properly, both can ping one another normally. However, when we attempt to access the BDC from the PDC's server manager console it says the network name cannot be found. Viewing and accessing the PDC from the BDC's server manager consoles works fine however. If we do "net use" or "net view" (using the new BDC's name) from the PDC it once again states that the network name cannot be found. From the BDC "net use" and "net view" work properly when specifying the PDC's name. All other BDC's are accessible from the PDC's server manager except for the one. All BDC's and the PDC are accessible from the new BDC's server manager. At first we thought this was a secure channel issue, but after resetting the secure channel ala NETMON we still have the same problem. To this point we have tested name resolution between the BDC and PDC and they are both able to resolve one another's IP address from the computer name so WINS seems to be functioning properly. We have also tried replacing the LMHOSTS files on both servers to no avail. In short we are STUMPED! ((BTW: THis is a mixed Novell/NT network with a single Domain, 1 PDC (in Georgia), and 7 BDC's (the problem BDC is in NC) connected via a Frame Relay connection with a Cisco 1600 router at each site)) Anyone with any ideas?

wow copious notes, thanks. well there's a new nic in the picture so that means a new mac address. I'm concerned that the lmhosts files are in the way so why don't you add an extension to the file ie .old and purge the cache with NBTSTAT -R , then try some pinging by ip and name. Also, did you build the BDC with this name or did you build it with another name and then change it?

Interesting case, I hope you write back with the final resolve.

Also use the ARP -a command to confirm that it's the correct mac address (after you ping)

Ned,
Thanks for the excellent advice. You will never beleive what the problem was: Turns out it was a corrupted TCP\IP stack on the BDC. (Who would have thunk it?) I discovered this after we spent 10 hours on the phone with Microsoft support. (a waste of $249) The support rep kept swearing it was a router port issue. (where he came up with that, I have no idea) Thanks for the help though. Just goes to show, sometimes it pays to just start from scratch. It was purely dumb luck that caused me to remove and replace TCP\IP, especially since pinging, net use, and net view was working fine. (at least from the BDC, actually pinging and name resolution was working both ways) Guess a little humble pie was just the dessert I was looking for!

Ataboy Todd!!!
Thanks for writing back.
IP stacks are the most difficult to diagnose. Perhaps when this new server was built there was no nic or MS Loopback Adapter installed during a reboot and that hurt the stack; just venturing a guess.

Now that more folks are pursuing the CCNA path, we are going to be suspecting router configs, a little knowledge is dangerous (LOL). I as well was suspecting an ACL on an outgoing port but good troubleshooting, when nothing's been done to the router, stays well away from that. The IP department at Microsoft has been weak for about a year now, very disappointing group. The entire NT group will be getting weaker as time goes on. They want us to just upgrade to 2000. All the guys that really knew NT no longer pick up the phone.

Well your BDC upgrade sure turned into an adventure, thanks again for writing back.

Regards, Ned