New DC/DNS server - can't connect 2

[amberlynn]

I'm trying to set up a new domain controller.
I'm using MS Server 2003 R2. I've also set it up as a DNS server.
I did all this using the wizards.
Now I'm trying to join a PC (XP Pro) to the new domain, but it can't find the domain controller.
I've googled, but can only find step by step instructions to setting up the DC/DNS server - no basic troubleshooting.
There's a good chance I'm missing something very basic, as my understanding of DCs and DNS servers if VERY limited
Any suggestions would be appreciated!!
Amber

 

[normntwrk]

make sure the DC points to itself for DNS

on the PC from a command line do an ipconfig /all and see if the results match up

Norm

 

[amberlynn]

ipconfig /all from server:

host name: mack-dc-02
Primary dns suffix: mack.local
node type: unknown
IP routing enabled: no
WINS proxy enabled: no
DNS suffix search list: mack.local

Ethernet Adapater Local Area Connection:
DHCP enabled: no
IP address: 10.38.71.59
Subnet: 255.255.255.0
Default gateway:
DNS server: 10.38.71.59

The server has another NIC that I don't have plugged in to anything - not sure if this matters?

On the PC that I'm trying to connect:

The DNS settings that display in IPconfig are wrong - because I can't change them to the new domain - the old domain settings still show here.

The IP settings:
DHCP enabled: yes
Autoconfiguration enabled: yes
Autoconfiguration IP address: 169.254.83.230
Subnet mask: 255.255.0.0
Default gateway:
DNS servers: 10.38.71.59

Thanks,
Amber

 

[normntwrk]

Your server doesn't have a gateway defined, you will need one if it is to access the Internet (use your router address)

On the PC, manually set the IP settings so that it is on the same network (example use 10.68.71.60 ) and see if you can connect to your server or join the domain



Norm

 

[amberlynn]

Right now there is no internet access.
The company I work for has just been sold. In a few weeks we lose our domain connection & internet access.
I am trying to setup and new DC and make sure it is working properly before we lose our old one. I can't hook our new DC up to the internet yet (I would have to add it to our existing domain).

That worked!
I gave it an ip address of 10.38.71.196

My question is - why do I have to do this?
Will I have to give all PCs static IP addresses in the future?

Thanks!
Amber

 

[normntwrk]

I would guess that you don't have a DHCP server running on the network , sometimes people let the router do DHCP or set the DC up as a DHCP server....you only need one DHCP server and only one DHCP server


Norm

 

[amberlynn]

So when we connect a router to this new domain, it will do the DHCP routing and assign IP addresses on the fly?

Thanks so much for your help!

Amber

 

[normntwrk]

Most routers are already set up to dish out DHCP addresses but you will have to change the IP range /scope of the router or the network as most routers come set up with a 192.168.x.x scope or a 10.10.x.x scope

have fun

Norm

 

[karlisi]

If you are using router as DHCP server, be sure to specify correct DNS server address 10.38.71.59 for clients.

I prefer to use one of network servers as DHCP server, easy to manage, can specify additional parameters for clients.

===
Karlis
ECDL; MCSA