new forest domain setup not allowing domain logins
in [Windows Servers]
|
Prev: Any disk utilities to correct overly long file names/folder paths?
Next: Add permissions for local workstation client
From: James McIllece [MS] on 2 Mar 2010 16:02 =?Utf-8?B?SmxpdHRsZTc4?= <Jlittle78(a)discussions.microsoft.com> wrote in news:6D43D9F4-85AE-4FC5-8CDF-1B5F02B1CA6C(a)microsoft.com: > Ah, that might be it, the server DNS does point to 127.0.0.1 > I will try that, however i am wondering about the clients. They are > all setup to get all settings via DHCP from my router.....would i > still need to manaully setup the DNS on the clients to point to the > server > If your router allows you to configure DHCP options, configure the DNS server option with the IP address of your DNS server. When clients obtain their IP addresses, they also receive any DHCP options that you configure on the DHCP server. Depending on the router you're using and your network setup, you might want to consider installing DHCP on the WS03 machine. If you do so, you can configure DHCP options for clients on the DHCP server. HTH -- -- James McIllece, Microsoft Please do not send email directly to this alias. This is my online account name for newsgroup participation only. This posting is provided "AS IS" with no warranties, and confers no rights.
From: Jlittle78 on 2 Mar 2010 21:42 hmm. i changed DNS server in the TCPIP properties from 127.0.0.1 to 192.168.1.100 (this is the static IP of the server) i left the alternate DNS blank. On the XP client i gave it a static IP and only added the static IP of the DNS server but i am still not able to login to this domain. I am still able to browse the web on the XP client with the DNS as my server rather than my ISPs DNS so i am pretty sure DNS is working properly at this point. Now i am clueless why i wouldn't be able to login to the domain. Any other thoughts? Why would i be able to have the XP client join the domain from within windows, then after the necessary reboot not be able to login to that same domain? just doesn't make sense. I'd prefer not to have this domain controller run DHCP as there is another segment of the network that i want nothing to do with the domain or server. any other thoughts would be appreciated. thx "Danny Sanders" wrote: > Ah, that might be it, the server DNS does point to 127.0.0.1 > > I will try that, however i am wondering about the clients. They are all > > setup to get all settings via DHCP from my router.....would i still need > > to > > manaully setup the DNS on the clients to point to the server > > > Your AD clients must point to the DNS server for your AD domain in order to > "find" the domain. If you are using DHCP, change it there. If you are not > using DHCP then change them manually. > > I would suggest using Windows DHCP. > > hth > DDS > > > "Jlittle78" <Jlittle78(a)discussions.microsoft.com> wrote in message > news:6D43D9F4-85AE-4FC5-8CDF-1B5F02B1CA6C(a)microsoft.com... > > Ah, that might be it, the server DNS does point to 127.0.0.1 > > I will try that, however i am wondering about the clients. They are all > > setup to get all settings via DHCP from my router.....would i still need > > to > > manaully setup the DNS on the clients to point to the server > > > > "Danny Sanders" wrote: > > > >> Verify that the DNS server is pointed to itself in the properties of > >> TCP/IP > >> for DNS. Make sure it is using the actual IP address of the server not > >> 127.0.0.1. Make sure the clients are pointed to the DNS server for the > >> domain only. > >> See: > >> How To Install and Configure DNS Server in Windows Server 2003 > >> http://support.microsoft.com/kb/814591 > >> > >> Best practices for DNS client settings in Windows 2000 Server and in > >> Windows > >> Server 2003 > >> http://support.microsoft.com/kb/825036 > >> > >> How to configure DNS for Internet access in Windows Server 2003 > >> http://support.microsoft.com/kb/323380 > >> > >> hth > >> DDS > >> > >> > >> "Jlittle78" <Jlittle78(a)discussions.microsoft.com> wrote in message > >> news:F977979C-43BF-46D0-9C6F-E5F4E8BFBFFD(a)microsoft.com... > >> >I just setup a new 2003 server and ran the setup wizard to setup AD for > >> >a > >> >new > >> > domain. The wizard ran fine and installed DNS ok (it appears), my XP > >> > clients > >> > are allowed to join the domain, but upon reboot they are not able to > >> > login > >> > to > >> > the domain. At the login screen when i click the drop down to change > >> > the > >> > login to the new domain i get a message saying "building domain list" > >> > and > >> > then select the new domain, but when i enter the proper login info i > >> > get > >> > another message saying "the system can not login becuase the domain is > >> > unavailable". I have no idea where to look next, but i suspect there is > >> > something wrong in the DNS setup perhaps? I would think the initial > >> > AD/DNS > >> > setup wizard would install what i need for a very basic single domain? > >> > Any > >> > insight would be great! > >> > >> > >> . > >> > > > . >
From: Jlittle78 on 2 Mar 2010 21:50 My router does not offer that flexability for changing DNS server on the LAN side. it only allows me to set the DHCP IP range and WINS server. I changed my XP client to a static IP and entered in the IP address of the DNS server on the client but it still gives me the error message that the domain is not available when trying to login to it. I am able to browse the web no problem so i believe DNS is working correctly on the server. even without logging into the domain, i can login to the local system and browse the network neighborhood and see the domain....when i double click it i am asked for a login name and password which i enter and can then browse the domain....there must be something simple i am missing preventing me from logging into the domain at startup. any other thoughts? Thanks "James McIllece [MS]" wrote: > =?Utf-8?B?SmxpdHRsZTc4?= <Jlittle78(a)discussions.microsoft.com> wrote in > news:6D43D9F4-85AE-4FC5-8CDF-1B5F02B1CA6C(a)microsoft.com: > > > Ah, that might be it, the server DNS does point to 127.0.0.1 > > I will try that, however i am wondering about the clients. They are > > all setup to get all settings via DHCP from my router.....would i > > still need to manaully setup the DNS on the clients to point to the > > server > > > > If your router allows you to configure DHCP options, configure the DNS > server option with the IP address of your DNS server. When clients obtain > their IP addresses, they also receive any DHCP options that you configure > on the DHCP server. > > Depending on the router you're using and your network setup, you might want > to consider installing DHCP on the WS03 machine. If you do so, you can > configure DHCP options for clients on the DHCP server. > > HTH -- > > -- > James McIllece, Microsoft > > Please do not send email directly to this alias. This is my online account > name for newsgroup participation only. > > This posting is provided "AS IS" with no warranties, and confers no rights. > . >
From: Danny Sanders on 3 Mar 2010 09:34
The DNS server needs to register it's SRV records in it's DNS zone. The clients look for the SRV records in the DNS zone. The netlogon service does this. See: How to verify that SRV DNS records have been created for a domain controller http://support.microsoft.com/kb/816587 How To Reregister SRV records of a Domain Controller In DNS Zone http://support.microsoft.com/kb/556002 hth DDS "Jlittle78" <Jlittle78(a)discussions.microsoft.com> wrote in message news:09A491F5-F2AE-45BF-BE8A-F684C82464EF(a)microsoft.com... > hmm. i changed DNS server in the TCPIP properties from 127.0.0.1 to > 192.168.1.100 (this is the static IP of the server) i left the alternate > DNS > blank. > On the XP client i gave it a static IP and only added the static IP of the > DNS server but i am still not able to login to this domain. I am still > able > to browse the web on the XP client with the DNS as my server rather than > my > ISPs DNS so i am pretty sure DNS is working properly at this point. > Now i am clueless why i wouldn't be able to login to the domain. Any other > thoughts? > Why would i be able to have the XP client join the domain from within > windows, then after the necessary reboot not be able to login to that same > domain? just doesn't make sense. > I'd prefer not to have this domain controller run DHCP as there is another > segment of the network that i want nothing to do with the domain or > server. > > any other thoughts would be appreciated. > thx > > > "Danny Sanders" wrote: > >> Ah, that might be it, the server DNS does point to 127.0.0.1 >> > I will try that, however i am wondering about the clients. They are all >> > setup to get all settings via DHCP from my router.....would i still >> > need >> > to >> > manaully setup the DNS on the clients to point to the server >> >> >> Your AD clients must point to the DNS server for your AD domain in order >> to >> "find" the domain. If you are using DHCP, change it there. If you are not >> using DHCP then change them manually. >> >> I would suggest using Windows DHCP. >> >> hth >> DDS >> >> >> "Jlittle78" <Jlittle78(a)discussions.microsoft.com> wrote in message >> news:6D43D9F4-85AE-4FC5-8CDF-1B5F02B1CA6C(a)microsoft.com... >> > Ah, that might be it, the server DNS does point to 127.0.0.1 >> > I will try that, however i am wondering about the clients. They are all >> > setup to get all settings via DHCP from my router.....would i still >> > need >> > to >> > manaully setup the DNS on the clients to point to the server >> > >> > "Danny Sanders" wrote: >> > >> >> Verify that the DNS server is pointed to itself in the properties of >> >> TCP/IP >> >> for DNS. Make sure it is using the actual IP address of the server not >> >> 127.0.0.1. Make sure the clients are pointed to the DNS server for the >> >> domain only. >> >> See: >> >> How To Install and Configure DNS Server in Windows Server 2003 >> >> http://support.microsoft.com/kb/814591 >> >> >> >> Best practices for DNS client settings in Windows 2000 Server and in >> >> Windows >> >> Server 2003 >> >> http://support.microsoft.com/kb/825036 >> >> >> >> How to configure DNS for Internet access in Windows Server 2003 >> >> http://support.microsoft.com/kb/323380 >> >> >> >> hth >> >> DDS >> >> >> >> >> >> "Jlittle78" <Jlittle78(a)discussions.microsoft.com> wrote in message >> >> news:F977979C-43BF-46D0-9C6F-E5F4E8BFBFFD(a)microsoft.com... >> >> >I just setup a new 2003 server and ran the setup wizard to setup AD >> >> >for >> >> >a >> >> >new >> >> > domain. The wizard ran fine and installed DNS ok (it appears), my XP >> >> > clients >> >> > are allowed to join the domain, but upon reboot they are not able to >> >> > login >> >> > to >> >> > the domain. At the login screen when i click the drop down to change >> >> > the >> >> > login to the new domain i get a message saying "building domain >> >> > list" >> >> > and >> >> > then select the new domain, but when i enter the proper login info i >> >> > get >> >> > another message saying "the system can not login becuase the domain >> >> > is >> >> > unavailable". I have no idea where to look next, but i suspect there >> >> > is >> >> > something wrong in the DNS setup perhaps? I would think the initial >> >> > AD/DNS >> >> > setup wizard would install what i need for a very basic single >> >> > domain? >> >> > Any >> >> > insight would be great! >> >> >> >> >> >> . >> >> >> >> >> . >> |