Joing Domain
in [Windows Servers]
|
Prev: Double mail sent
Next: Security Log Event Forwarding
From: JoeM on 29 Apr 2010 15:57 Just wanted to give some more info I found, and will attempt to look at now. If I setup the server to assign IP address connected to a switch I have no problem, but connected to a linksys router which was assigning IP addresses failed. Will see what can be done on the Router now. Thanks all for the info "Meinolf Weber [MVP-DS]" wrote: > Hello JoeM, > > Sounds like basic DNS configuration, please post an unedited ipconfig all > from the new DC/DNS server and a client you try to join. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > > > > I am testing Windows Server 2008R2 (evaluation copy) to see how well > > it will work in our current system. We currently have a 2003 Server > > that someone else setup, this server is going to be removed, and the > > network is being setup from scratch. > > > > I have created a Domain(if anyone has steps for this just so I can > > check my work, this would be appropriated). When I go to either the > > XP machine or Windows 7 machine, and have it join the domain I get the > > error "An Active Directory Domain Controller (AD DC) for the domain > > "corp.joe.com could not be contacted" Ensure that the domain name is > > typed correctly". I can log into the server if I use > > ""\\computername"" Any ideas, steps to try, etc would be > > appriciated. > > > > > . >
From: Bill Grant on 29 Apr 2010 20:44 That is correct. DHCP on the router will not give the clients the correct DNS setting. It will give them its own IP address for DNS. This is incompatible with AD. "JoeM" <JoeM(a)discussions.microsoft.com> wrote in message news:F7D8046C-57A1-40F0-A53F-EEBF104BF1D8(a)microsoft.com... > Just wanted to give some more info I found, and will attempt to look at > now. > If I setup the server to assign IP address connected to a switch I have no > problem, but connected to a linksys router which was assigning IP > addresses > failed. Will see what can be done on the Router now. > Thanks all for the info > > "Meinolf Weber [MVP-DS]" wrote: > >> Hello JoeM, >> >> Sounds like basic DNS configuration, please post an unedited ipconfig all >> from the new DC/DNS server and a client you try to join. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >> ** Please do NOT email, only reply to Newsgroups >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >> >> >> > I am testing Windows Server 2008R2 (evaluation copy) to see how well >> > it will work in our current system. We currently have a 2003 Server >> > that someone else setup, this server is going to be removed, and the >> > network is being setup from scratch. >> > >> > I have created a Domain(if anyone has steps for this just so I can >> > check my work, this would be appropriated). When I go to either the >> > XP machine or Windows 7 machine, and have it join the domain I get the >> > error "An Active Directory Domain Controller (AD DC) for the domain >> > "corp.joe.com could not be contacted" Ensure that the domain name is >> > typed correctly". I can log into the server if I use >> > ""\\computername"" Any ideas, steps to try, etc would be >> > appriciated. >> > >> >> >> . >>
From: DaveMills on 30 Apr 2010 02:12
On Fri, 30 Apr 2010 10:44:38 +1000, "Bill Grant" <not.available(a)online> wrote: > That is correct. DHCP on the router will not give the clients the correct >DNS setting. It will give them its own IP address for DNS. This is >incompatible with AD. It does not matter if the DHCP server is on the Lynksys router or on Windows. It does matter that the DHCP server is correctly configured to give out the right settings. The defaults for most DHCP servers are useless for Windows. > > >"JoeM" <JoeM(a)discussions.microsoft.com> wrote in message >news:F7D8046C-57A1-40F0-A53F-EEBF104BF1D8(a)microsoft.com... >> Just wanted to give some more info I found, and will attempt to look at >> now. >> If I setup the server to assign IP address connected to a switch I have no >> problem, but connected to a linksys router which was assigning IP >> addresses >> failed. Will see what can be done on the Router now. >> Thanks all for the info >> >> "Meinolf Weber [MVP-DS]" wrote: >> >>> Hello JoeM, >>> >>> Sounds like basic DNS configuration, please post an unedited ipconfig all >>> from the new DC/DNS server and a client you try to join. >>> >>> Best regards >>> >>> Meinolf Weber >>> Disclaimer: This posting is provided "AS IS" with no warranties, and >>> confers >>> no rights. >>> ** Please do NOT email, only reply to Newsgroups >>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>> >>> >>> > I am testing Windows Server 2008R2 (evaluation copy) to see how well >>> > it will work in our current system. We currently have a 2003 Server >>> > that someone else setup, this server is going to be removed, and the >>> > network is being setup from scratch. >>> > >>> > I have created a Domain(if anyone has steps for this just so I can >>> > check my work, this would be appropriated). When I go to either the >>> > XP machine or Windows 7 machine, and have it join the domain I get the >>> > error "An Active Directory Domain Controller (AD DC) for the domain >>> > "corp.joe.com could not be contacted" Ensure that the domain name is >>> > typed correctly". I can log into the server if I use >>> > ""\\computername"" Any ideas, steps to try, etc would be >>> > appriciated. >>> > >>> >>> >>> . >>> -- Dave Mills There are 10 types of people, those that understand binary and those that don't. |