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: Jlittle78 on 2 Mar 2010 08:14 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: Danny Sanders on 2 Mar 2010 09:30 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: Santhosh Sivarajan on 2 Mar 2010 10:05 It seems like a name resolution issue. Make sure your XP clients have proper DNS and WINS configuration. Also, make sure to check your DC configuration. -- Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights. "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 10:23 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: Danny Sanders on 2 Mar 2010 11:36
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! >> >> >> . >> |