How does one setup a Windows 2003 Enterprise Server on one machine with 2 nics?

70 pts.
Domain Name System
Dynamic Host Configuration Protocol
Microsoft Windows Server 2003
Microsoft Windows XP
Windows Server 2003 configuration
I have read a book (O'Reily) on setting up windows server 2003 and at my current job I am fortunate enough to be able to work/play with their servers which are also windows 2003. In this, I have a bit of experience, however I ran into a few problems when trying to setup my own personal network at home. Equipment 1 - Server (AMD Athalon XP 2800+; 1GB RAM; 80GB HDD) 2 - NICs 1 - 8-port workgroup switch (linksys EZXS88W) 1 - 4-port wireless G broadband router (linksys WRT54GS) 1 - Motorola Surfboard Modem (broadband from ISP) Equipment Setup The server's two NICs are setup as follows: NIC (Router) IP: (static) MASK: GATEWAY: DNS: NIC (Internet) IP: (dynamic) MASK: GATEWAY: DNS: I have one computer (client - windows XP Pro) connected to the 8-port switch. The uplink port on the switch is connected to the Router NIC. The Internet NIC is connected to a port on the router ( - DHCP is on) and the router is connected (via uplink port) to the modem. On the server, I installed DNS for (my computers name is myhost) so there are records in there for and These include NS, A and SOA records all out of the box and unmodified from the wizards implementation of them. I have my forward lookup zone set for and a reverse lookup zone set for (i believe that was the syntax). On the server I have also installed active directory (immediately after DNS was installed and the internet connection was tested and worked). I used DCPROMO to get active directory up and running and it passed it's diagnostic test with flying colors. I then proceeded to setup one new account named 'adam' and added him to the administrators group. I then installed DHCP on the server (associating it with - Router NIC) and authorized it for so it is now running. My goal I am developing a paperless management system (software) for a small business. I need to be able to test connectivity to the SQL database located on the server from inside the private network and from outside the network (via the internet). My plan is to get this network up and running so my 1 client computer can connect to the server (and see the internet). Also, I need to be able to access this server from outside the intranet (but that is a different post I'm sure). My dilemma As it stands right now, when I go to my client computer and try to connect to (via mycomputer->properties->computer name->change...) I am prompted with an error, saying the DNS server cannot be found (this error returns almost immediately). Directly before I installed DHCP I tried to connect to the exact same way and after the timeout period had expired I was prompted with the error, saying the DNS record could not be found for However, this record exists on my server... Finally So then, I ask you all this, what am I missing? Is this a common problem, because I am having trouble finding solutions when digging through forum posts. All I want to do is connect to my server from my client and still have internet access. (It should be noted that the router needs to stay where it is in the connection chain and must stay as a DHCP server). Thanks to all for any assitance you can provide!

Answer Wiki

Thanks. We'll let you know when a new response is added.

The problem is the computer cannot resolve the server by DNS. You should set the DNS manually when you are trying to add the computer to the domain.

In your DHCP server settings, make sure you add the Scope Option 006 for DNS server. Add the server IP to the DNS servers list. You should also be careful of multiple DHCP servers. Preferably you should use the server as the DHCP server instead of the router. Set a static IP for the server and turn off DHCP on the router.

Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • carlosdl
    Hello Pr09. What is the reason why the router must stay as a DHCP server ?
    77,180 pointsBadges:
  • Denny Cherry
    You also need to disable DHCP on the router. You currently have two DHCP servers on the network. The router is one, and the server is the other. You probably don't have the DHCP server on the router setup to point users to the correct server for DNS, and you typically do not want two DHCP servers on the same network.
    67,485 pointsBadges:
  • Pr09
    Thanks all for the replies, but the reason the router must stay on is this: I have a roommate who has nothing to do with my test server and we have a residential account with our ISP. My roommate has his computer, a Wii and an XBox. If I were to set his computer/gaming consoles up behind my server as the DHCP and the server went down when I was not there, he would essentially be locked out of his own online-connection. So currently he uses 2 of the router ports and thusly needs DHCP at that level. Now the thing that confuses me the most is the fact that , lets say I didn't have the router and I connected directy to the modem from my server (and turned DHCP on at the server level). Essentially I am connecting through my ISP assigned IP, which, since it is dynamic, I am guessing, is being served to me via their DHCP. So if there is one layer of DHCP I am behind from the get-go, then why can there not be another layer (the router) before my server? It seems there should be a way to set that up...
    70 pointsBadges:
  • mshen
    Set your client computer IP address to a static IP address. That will eliminate the DHCP issues. If the client computer is connected directly to the router, that is where it is getting the DHCP address from, and most likely that is why you can't resolve the domain name.
    27,385 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: