cannot connect to domain controller

May 11, 2009 at 05:19:06
Specs: Windows Vista

I need some help in connecting with my server 2003 domain controller. this is something I have never done and have no experience with it. when I go to computer properties and click on computer name and try to put my computer into that domain it says that that domain can not be contacted. What must I do on the server end? what must I do on my unconnected computer. firewall settings? remote access? where and how must I enter my un connected computer's name in active directory? I am absolutely cluless and would much appreciate a step by step guide.

See More: cannot connect to domain controller

Report •


#1
May 11, 2009 at 05:56:18
Did you setup a domain.local in Active Directory on the server? If you did, you should see it when you browse for the name.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
May 11, 2009 at 08:29:18
I did set up a domain on the server and i called it 'contoso.com'. does it have to have .local at the end. I can't even ping the 2 computers.

Report •

#3
May 11, 2009 at 08:34:05
i want to join the domain with my pc, but i am missing something somewhere.

Report •

Related Solutions

#4
May 11, 2009 at 11:18:01
If you can't ping the Domain Controller from the workstation, then you need to figure out why. You won't be able to join the Domain if the client can't access the DC.

EEOC


Report •

#5
May 11, 2009 at 12:57:22
I kinda realized that. I really don't know how to figure out why it isn't working. I don't know what to check or try, I have no clue what steps to take to get this problem sorted out. Is there something I have to do on my DC, or does the problem lie with my PC that I want to connect?

Report •

#6
May 11, 2009 at 15:27:04
Domain name: CONTOSO.COM
Administrative Contact:
Administrator, Domain domains@microsoft.com
One Microsoft Way
Redmond, WA 98052
US
+1.4258828080

contoso.com already exists & you don't own it. That's why MS recommeds .local addresses for non registered domain names.

As far as your ping problem goes, run ipconfig /all on both machines & post the output.

How do you know when a politician is lying? His mouth is moving.


Report •

#7
May 12, 2009 at 00:10:44
= }

Report •

#8
May 12, 2009 at 02:50:27
i now renamed my server djdevlam.local
is that better, or does it need a .com in there 2?

Report •

#9
May 12, 2009 at 05:59:17
I see the problem. It's in the DC configuration. You have some strange external address for the wired NIC (5.219.214.164) & a DHCP wireless address.

Disable the wireless NIC on the DC & give the wired NIC a static IP address, something like 192.168.0.100 & static DNS entries. Use your ISPs DNS.

Both machines should be connected to the router.
Modem > router > All machines.

You don't need any .com.

How do you know when a politician is lying? His mouth is moving.


Report •

#10
May 12, 2009 at 06:15:25
This address 5.219.214.164 is from a program I installed that alows u 2 create networks for any computers that are online. It is called Hamachi. I do not use this connection to go on to the internet. It is not a wired network, It works through my wireless connection. I only have wireless, this is my only connection...5.219.214.164 is from Hamachi which is a VPN service... If I do give the Hamachi a static IP address and my router's IP for DNS, then it does not work anymore...

Report •

#11
May 12, 2009 at 08:58:24
It is pretty normal when following a microsoft training manual to use CONTOSO.COM. I have seen them use this since NT4 training.

http://en.wikipedia.org/wiki/Contoso

If this is for learning and not for internet then I am sure guapo will have a different perspective/advice concering configuration.

Server and workstation do need to be in the same subnet to communicate.


Report •

#12
May 12, 2009 at 09:23:28
they are on the same subnet.....


Report •

#13
May 12, 2009 at 13:52:53
Your workstation is pointing to the router 192.168.0.1 for dns

I do not see a dns entry for the server which should be pointing to itself at 192.168.0.11

To reach Active Directory you need to use MS DNS since the internet does not know who your server is. Point the workstation dns entry to x.x.x.11, assuming it is the AD and DNS server and you should be fine.


Report •

#14
May 13, 2009 at 00:25:23
= }

Report •

#15
May 13, 2009 at 05:46:07
I only use static IPs on small networks. I also use the static DNSs of the ISP.

How do you know when a politician is lying? His mouth is moving.


Report •

#16
May 13, 2009 at 07:41:34
is the static DNS of the ISP my wireless router's IP? If not, where do I find it?

Report •

#17
May 13, 2009 at 08:56:43
To connect a workstation to a Active Directory DC you need to have the workstation point to the AD DNS server.

You do not use the ISP dns entries on the workstation in an AD environment.

You configure dns's forwarders tab to have the isp's dns servers. But there isn't even a connect to the server yet so dealing with forwarding or isp dns is very premature.

Static ip has NEVER been and NEVER will be a requirement on any lan nor does it address ANY issue except if you don't want to have a dhcp server. DHCP is just fine

dewald it does not appear you are following a MS training manual any more. The training would not direct you to use your router for dhcp. It would direct you to use the server for dhcp and disable the routers dhcp server.

you also should disable all other network interfaces, including hamachi except the wireless on both which is what you appear to be using until you have connected to the server.

Next step in troubleshooting would be to do a nslookup server01 from the workstation and post the results. This is a test to see if the workstation can talk to the servers dns and that the server dns will return the proper information.


Report •

#18
May 13, 2009 at 10:03:36
= ]

Report •

#19
May 13, 2009 at 11:05:30
For some reason your workstation is not seeing 192.168.0.11 as your dns server. It thinks 192.168.0.100 is your dns server which is why it can't find it.

When learning you need a clean environment. You have too many config issues/hamachi/router for dhcp that can confuse where and what to troubleshoot.

Go to the book store/or order online and purchase one of the MS server training courses. They will walk you through step by step.

Try craigslist for a used course material


Report •

#20
May 13, 2009 at 11:55:18
I changed my server name to 192.168.0.100.....

anyway, I am studying MCSE. they talk about stuff and then tell me to do things and they just presume that my 2 different computer's are on the same domain. no where do they give me step by step instructions on what exactly to do to get on the domain.

anyway, thanx for taking the trouble and time to try and help me.


Report •

#21
May 14, 2009 at 14:53:22
You need the mcse course material that contains labs. Those are what walk you thru the exercises.

Report •

#22
May 18, 2009 at 07:35:10
i recently configured a new server 2003 as a domain controller and also as a dns. I managed to connect my xp pc, my server 2003 pc which is a member server, and my vista pc. they are all on the domain and can connect to the internet, all but my vista pc. can some1 please tell me what settings I have to change so my vista pc can have access to the internet through my DC?


Report •


Ask Question