Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Cannot connect computer to domain

Hello,

We are having an issue after migration of a SBS 2003 server to Server 2008 R2.  the migration was smooth and did not require being siezed.  The old SBS server is offline.

However, when we now go to add another server and another workstation, we get the error that "An Active Directory Domain Contoller (AD DC) for the domain culd not be contacted..."

When clicking details, it shows the domain controller was successfully contacted, but states:  "However no domain controllers culd be contacted...".

All referneces to the old server were removed from DNS and from ADSI, but still no luck.  

thanks in advance for someone's help on this.
0
SRC-S1
Asked:
SRC-S1
1 Solution
 
Haresh NikumbhSr. Tech leadCommented:
If this server is having 2 nic? with different ip address?
0
 
SRC-S1Author Commented:
No single nic.  It is a virtual server, however (vmware) configured in bridge mode.  We have done the same setup in the past without issues of any kind.
0
 
Alan HardistyCo-OwnerCommented:
What are the results of running DCDIAG from a command prompt on your existing DC?

You can run:

dcdiag >c:\dcdiag.txt

To output the results to a file.

What DNS settings are you using on the existing DC?  Is it pointing to itself (not 127.0.0.1) for DNS?

What DNS settings are being given out via DHCP?

Alan
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Haresh NikumbhSr. Tech leadCommented:
run the repadmin and showreps commands to check for errors
0
 
babuseCommented:
Check the DNS Settings to be pointing to your DC.
Also when adding it to the domain, try using the fully qualified domain name in the "Domain" field.
0
 
SRC-S1Author Commented:
Pretty simple..the server that was migrated points only to its own IP address for DNS, and it only has one nic.  The DNS zone appears to be in order, and the SVR entries have been re-registered, DNS flushed and so on.

It does sound like the FSMO roles transfers, even  though read as successful and clean on the old decommissioned server and the new, hat something might have gone south.  

Appreciate your help.
0
 
SandeshdubeyCommented:
To get the clear viwe can you post the ipconfig /all details of existing DC and problematic client computer.Also run dcdiag /q and netdom query dc and post the output.

Ensure that correct dns setting is configured on DC and client as thishttp://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

See this similar topic:
http://www.techsupportforum.com/forums/f103/solved-cant-join-a-client-to-active-directory-domain-607542.html
http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/dcb6fc40-021a-4fce-b840-87034213bb6a
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now