Domain Login

[caseye]

I am trying to configure another server on my network to be used as a development server for the companies web page. I have the server loaded with only IIS and SQL server using windows 2000 It is connected to the network and on the same subnet it is even getting the DHCP Information From the exsisting server also I can ping the exsisting server and from that server I can ping the server I am trying to connect However I cannot log into the domain it says that the domain can not be contacted. Any Ideas

 

[CaffieneNnicotine]

God this sounds like a DNS issue. Do you have other Win2k machines on your domain? If so are they giving any errors? What happened when you joined the machine to the domain? Any errors or did everything go smoothly? In DHCP is your server dishing out the IP of your Win2k DNS server FIRST? I have MUCH less issues if I have my win2k box running DNS and Active Directory listed as the primary DNS for all my workstations. Post bcak if you need more help. All Complaints Will Be Routed To /dev/null

 

[tom11011]

Assuming the server has joined the domain, when you login, there are 3 options.

username
password
domain

for domain, make sure the domain name is selected and not the machine name.

 

[caseye]

My DHCP Server is The same as my DNS and the IP Address Is is statically assigned outside of the DHCP Range. All of the network Is windows 2000, I am pretty sure it is a DNS problem and more of a configuration problem. I am not sure If I have the DNS set4 up right when I first set it up all the computers joined without any problems however they are not listed in the DNS so I know that it is not configured right but I have had no problems with this until now I am trying to Join another server to the Domain I can Join Work stations w/2000 pro all day long any Ideas.

 

[Eddiefdz]

Why dont you assign a static ip to the Server instead of using DHCP. Also make sure that you add the DNS server's ip address. If that doesnt work, you may even try to create an LMHOSTS and HOSTS file and point it to the domain controller.

 

[CaffieneNnicotine]

Go into your dhcp config. Right click on your server name and select proerties. Click on DNS tab and check:
Automatically Update DHCP client information in DNS
Always Update DNS
Enable DNS Updates For Clients That do not support dynamic updates.

After you do that from a command line type:
ipconfig /release
ipconfig /renew

Then try pinging the FQDN of your DC by typing:
ping domaincontrollername.domain.com (or whatever your domain name is). If it wont resolve then check your SOA and A records in your DNS forward lookup zone.

Makwe sure you have an account created for the server you are trying to add to the domain in AD users and computers. You will create the account in the Computers OU. If your DNS server is your DC also, make sure your SOA records point to your DC's FQDN.

Make sure that Remote Procedure Call and Remote Procedure Call Locator services are running on the DC and the server in question.

The next part is a little fuzzy: Go into Active directory sites and services. Expand the SITES folder, then keep going until you get to you DC's name. The highlight NTDS settings. Right click on automaticcaly generated vaule and select properties. In there somewhere should be a drop down arrow that will allow you to select different transport protocols. Select IP from the list and OK your way out everything. Give this a shot.

All Complaints Will Be Routed To /dev/null