Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 574
  • Last Modified:

Cannot connect to domain server

I have set up a Windows Server 2008 R2 Foundation server and added Active Directory Domain Services role. I have tried joining the domain from a Windows 7 PC but get an error message. The domain name is fulwell.local. If I try joining this domain I get a "cannot find domain" message. If I try "fulwell" I get a log in prompt but then, after logging on I get the error in the attached file.
Does anyone know how to fix this?
Server-domain-error.JPG
0
grapey100
Asked:
grapey100
  • 3
  • 2
  • 2
  • +2
2 Solutions
 
lpelkieCommented:
The workstation has to be using the same DNS server as the domain controller.  When you set up AD, it created a lot of service addresses.  If your workstation doesnt use the correct DNS server, you will not be able to join the domain
0
 
Anthony1982Commented:
Check the ipconfig /all of the windows 7 pc. Does it have a the proper DNS server name? Is the Windows Server 2008 R2 Foundation server you DNS server?
0
 
grapey100Author Commented:
My DNS Server is my router which is 192.168.1.254 and both the server and the laptop have this as the DNS. However, when I installed AD it did want me to install a DNS server. The DNS Server on the server has an error message (event ID 4015) and perhaps this is relevant?
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
lpelkieCommented:
That is what your issue is, the DNS server on the router is not able to handle the record types that AD requires.  You need to have the server run dns and have the workstations refer to it for lookups.  You can also then configure the DNS on the server to use the routers DNS as a rollup address
0
 
civicryanCommented:
You have to configure IP address on your server right now point to iself and try to add DNS role again ( or assign 127.0.0.1 on Prefered DNS.)
Check this event ID infohttp://technet.microsoft.com/en-us/library/cc735674(WS.10).aspx
0
 
grapey100Author Commented:
lpelkie: can you explain how I do this please? Thanks
0
 
Anthony1982Commented:
So I am assuming that your router is also handing out DHCP? Well I would first turn the router's DHCP/DNS off. Much simpler than trying to configure a rollup address. Then add/readd the roles of DHCP/DNS to the server and make sure to choose the option of using itself as the DNS server.
0
 
Darius GhassemCommented:
Do not use 127.0.0.1 you need to use.

Go into your TCP\IP settings you should have a static IP address. Your preferred DNS server should point to the server's IP address.

Once you have done this got to command prompt run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix.

On your router you need to change the DHCP server settings to make sure to you have it leasing IP address with the Primary DNS server pointing to the DC IP address. I would recommend setting up DHCP on your Windows server though.

Once you have done the above you will be able to add your workstations to  your domain.

0
 
Darius GhassemCommented:
Do not need to readd your DNS service this has already been setup during the dcpromo process you just need to change your TCP\IP settings on your network card.
0
 
lpelkieCommented:
Sorry for the delayed respose:

to configure rollup address:

go into dns manager
right click on the dns server and goto properties
goto the forwarders tab
click edit, and add the IP of your router (or whatever device is currently handing out your DNS)
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now