2003 Server UNC Problem

[haid]

Hey all,
I've got a small network with a 2000 domain controller and a 2003 domain controller. Clients on the LAN can connect to the 2000 server using UNC, but when they try to connect to the 2003 server, they get a weird authentication error. When I VPN into the network, I can connect to both using UNC. Both servers are replicating fine, and all the DNS seems to be in tact.

Any ideas?
Thanks

[rammy]

Is the 2003 server behind a different firewall and do have PKI authority setup? If so you might be able to VPN in cause you have a certificate authority to do so through that firewall. Just a shot in the dark, it sounds like DNS maybe too.

[haid]

Hmm...not really sure what PKI authority is. The servers are behind the same firewall, however. How could PKI authority affect clients' abilities to connect to the server?

[rammy]

What is the error they are getting, exactly and did you just add the 2003 server to the network and when you say replication you are talking active directory?

[haid]

It says that "<Server name> is inaccessible. The target account name entered is incorrect." Something along those lines. The 2003 server has been on the network for a while. I'm pretty sure adprep was run on the 2000 server. If it wasn't, I'd probably be having some more severe issues, no?

[rammy]

For sure, I take it the 2003 server is not a member server and has been promoted and it belongs to the same domain. have you tried creating a dummy account on the 2003 server and tried logging in from one of the computers on the network?

[haid]

Yes, and it appears almost instantly on the 2000 server.

[rammy]

Make sure the server names are different, it sounds like DNS though too. Was the name space setup differently when the 2003 was promoted?

[haid]

The servers definitely have different names...not so sure about the name space though. What do you mean?

[mike brabet]

It maybe that dns is resolving netbios to the same i.p or vicea versa. Not 100% just a quick-e in passing.

Good luck