Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

trouble joining a laptop to a domain


  • Please log in to reply
1 reply to this topic

#1 cygnusonline

cygnusonline

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:39 PM

Posted 13 May 2015 - 02:50 PM

Hi I have been looking after a small office environment which consists of Server with server 2008 R2 and about a dozen pcs/laptops all running Windows 7 Pro and connected using a LAN (they dont have wifi). They just invested in half a dozen new laptops for a new project. I am in the process of adding them to the domain, the first four went without a hitch, however the last two had problems. The process i followed was to set up the laptops, install all the software and updates they needed then joined the domain. On the last two I first noticed that after I did the initial Windows setup the network connection icon in the bottom right had an exclamation mark, when I open network settings it says unidentified network and no internet access. If I try to join the domain I get a 'can't connect to domain controller' message. This didn't happen with the first 4 and has never happened before
 
Has anyone seen this before? Is the server on its way out?
Thanks guys
Kevin


BC AdBot (Login to Remove)

 


#2 JohnnyJammer

JohnnyJammer

  • Members
  • 1,117 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:QLD Australia
  • Local time:04:39 AM

Posted 13 May 2015 - 07:02 PM

So it sounds like you have a loop back IP 169.*.*.*, i would make sure the DHCP server has enough IP address's left.

Next make sure to set the dns and gateway manually when joining them to the domain so you dont get issues.

If that fails and you have an IP and can ping the server, try this command

net use \\servernamehere\ipc$

make sure yiou can atleast connect to the servers IPC.

 

See how that goes, if that dont work then using the command sysdm.cpl and going to NetworkID instead of change and see if you can join in that way.


Edited by JohnnyJammer, 13 May 2015 - 07:02 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users