New to Windows server 2003

[freak180]

Ijust found a server at my school, (working there) and I finally got it all booted up. I installed some roles and etc. However. In the computer lab I'm at I can seem to add the domain to one of the client computers. I get an error message such as "An Active Directory Domain (AD DC) for the domaim "mastbaum" could not be contacted" Is there something else I'm supposed to do?

[ToneKnee]

I'm pretty sure that if you want to add a client to the Domain Controller then the client computer needs to be pointed at a DNS server which is apart of that domain. So if you've set up a DNS server with the Domain controller when you were adding roles, then you should point the clients DNS settings to that DNS servers IP address and try again.

[freak180]

What I'm having problems is adding that client to that domain. I keep getting an error in the process.

[c.grz]

DNS is most likely the culprit.

[ToneKnee]

  On 03/11/2011 at 16:14, freak180 said:

What I'm having problems is adding that client to that domain. I keep getting an error in the process.

As I said, it's probably the DNS on the client side not pointing to the Domain controller or the Domain forest which the Domain Controller is apart of.

[freak180]

Then how do I fix this issue? I'm fairly new to this.. sorry :|

[Brandon H Supervisor]

  On 03/11/2011 at 16:21, freak180 said:

Then how do I fix this issue? I'm fairly new to this.. sorry :|

you need to point the client computer towards the domain controllers DNS, you do this by manually inserting the domain controller's IP as the DNS for the client computer

[ToneKnee]

Depending on what version of Windows your clients are running. You pretty much need to go into the Network Connections area, right click on the network adapter, go to propertises, and under TCPIP IPv4 properties, enter in the IP address of the domain controller. You'll have 2 boxes, a primary and a secondary, I'm going to assume you've only setup one DNS server and have only one IP address to the domain controller, so just leave the second box blank. When done, click okay, and okay again and try adding the client computer again.

[majortom1981]

Go to the network cards ipv4 tcp ip settings and point the dns settings to the domain controller. Make sure the domain controller also has dns role installed and configured.

[freak180]

SOrry if this is stupid to ask, how do i find out the IP address of the domain controller?

cmd ipconfig? or is it something different?

[c.grz]

You should of set a static IP on the server when you originally set it up.

[freak180]

Well I have 2 area connections. 2 Ethernet cables plugged in. And the clients are windows xp machines

[Brandon H Supervisor]

  On 03/11/2011 at 16:56, freak180 said:

Well I have 2 area connections. 2 Ethernet cables plugged in. And the clients are windows xp machines

that has nothing to do with what TheReason was saying

have you set up a static IP on the domain controller or did you install the the DHCP role?

[c.grz]

[freak180]

From what I remember it assign one to me automatically

when i hit the command ipconfig /all for area connection 2 its 10.40.47.208

[c.grz]

Servers should always have a static IP address; especially if it's a domain controller, dns or dhcp server.

[freak180]

Yeah its set as static mate and not dhcp. While I was setting it up the first time it said during the wizard that it would assign me an ip address

[c.grz]

If you didn't assign it then it ISN'T static.

[+BudMan MVC]

"it would assign me an ip address"

Dude you were given a picture/video of what a static setting would like and how to set one. It assigning you one would NOT be static.

Why do you have 2 network interfaces? If 1 on public network and other private?

The output of ipconfig /all will show you if static or the dhcp server you got it from.

Post the output of ipconfig /all and we can tell if you static or not. From your statements I find it almost impossible that your on a static IP.