Directory service unavailiable, new hardware same settings

Question

I'm working on a project with 2 sites connected by a VPN. Site 1 has the main server and there is a secondary server at site 2 which I am trying to replace. The current setup works perfectly however I can't for the life of me get the replacement server at site 2 up and running. I'm trying to replace like for like just upgraded hardware.

I have installed the OS (all Server 2003 Standard SP2) and used exactly the same settings as the old server. I have setup Active Directory, DNS Server, DHCP Server and WINS Server configured. I have used all the same settings as the old server (except IP address and name). I can access the active directory but I can't do anything; add, edit, delete all returns "the directory service is unavaliable". No-one can login on any of the computers on site 2 and the internet is down. Plugging the old server back in and connecting it to the network rectifies the issue (so both new and old are connected at site 2), everyone can login and the internet is back (curious since the modem connects direct to the switch, and even with the new server online I can connect to the router via IP but not the net).

I really don't have much experience but I've been roped into doing this because my company is too cheap to hire a real network admin. Any suggestions of where I can start to troubleshoot this, its driving me crazy and I only have a day before all the users are back on site.

Answer 1

When you say you have installed the OS, and used the same settings as the old server, does this mean that you have joined the server to existing domain at Site 1? When you say you can access Active Directory can you see all of the users and computers you would expect?

My thought so far is:
the reason your users cannot login when the new server is connected is that it is not a Global Catalog server, and as a result wont authenticate users. Please see the Microsoft KB article I have linked below: http://support.microsoft.com/kb/313994

You will need to check your DHCP settings, you are looking for the DNS servers and default gateway, the DNS server IP should point to your server and your default gateway to your sites router.
Once you have confirmed that DHCP is pointing your client PC's at your server for DNS you need to ensure that you have your DNS forwarders setup correctly. I tend to use googles public DNS servers for forwarding 8.8.8.8 and 8.8.4.4

If you need me to expand on the DHCP or DNS settings or where to find them let me know and I will update this answer.

I think this is enough to go on with at the moment.