Problems connecting fresh Windows 7 installation to existing domain

Toggle sidebar Toggle sidebar
C

crschil

Honorable
May 5, 2013
13
0
10,520
I have a very basic home network, with a server running MS Server 2012 Essentials.

One of the clients, a Wi-Fi connected laptop, recently had a hard drive replacement and reinstallation of the OS. However, since then, I am having trouble authenticating the user accounts when connecting through the laptop.

I have successfully run Server 2012 Connector on the laptop and the laptop does join the domain, but when I try to log in, the account seems to authenticate properly, but I am only able to get a temporary profile on the laptop. I am a relative novice with the Server versions of Windows, but I am relatively well versed with the consumer grade versions of Windows.

I have examined the logs on the Windows 7 machine and every time I try to log in, I get and NETLOGON error with an event id of 5917. The exact text of the error message is:

This computer was not able to set up a secure session with a domain controller in domain XYZ due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
Click to expand...

The take away from this message is the laptop does not seem to be able to reach the server to login, however, none of the other clients share this problem. Likewise, before the hard drive upgrade, this exact laptop was able to login successfully with almost the same Software and Hardware configuration (except for the hard drive). The original hard drive was the original Toshbia 250GB HDD.

Laptop Specs:


  • ■ Model: Dell Latitude E6510
    ■ CPU: i5 M520
    ■ RAM: 4GB
    ■ OS: Windows 7 Professional
    ■ SSD: Crucial m500 240 GB
    ■ WLAN: Dell DW1501 Wireless Card

I've also tried connecting via LAN with no change in behavior.

Given the issue seems localized to this laptop after the OS reinstall, it would appear to me to be something locally on the laptop, but I haven't a clue where to start. Can anyone offer any suggestions?

 
Solution
C
I managed to solve this myself with some repetitive troubleshooting.

iknowhowtofixit was on the right track, but it wasn't the Computer Name, but some combination of the specific computer and the specific user.

Here's what I isolated it to:

  • ■ My account was able to log into any other machine in the domain without any problem and a local profile was created.
    ■ Another user account that had not previously been associated with my laptop was able login and have a profile created
    ■ If I removed the laptop from the domain, the users I used to test the previous bullet would get a temp profile upon logging in.
    ■ If I changed the name of the computer, the problem persisted
    ■ If I removed or reset the machine in the domain (via the Server's...
Sort by date Sort by votes
C

crschil

Honorable
May 5, 2013
13
0
10,520


I appreciate the link, but the problem is not with any local account, but relative to the logging into a domain profile. I am successfully able to log into the main with any profile on the local machine.
 
Upvote 0 Downvote
C

crschil

Honorable
May 5, 2013
13
0
10,520


The Server 2012 Connector software is supposed to deal with this issue (or so the message tells me). However, I did try to change the computer name to something different and ended up with the same problem. I am able to login but I end up with a temporary profile on the client machine.
 
Upvote 0 Downvote
D

danny2000

Splendid
Sep 14, 2010
2,523
0
21,460


According to your wording, you're logging into the laptop and the user's profile is a temp profile, but yes, we know that are successfully logged into the domain

This will sometimes happen if that user account is using a roaming profile on the domain. Is a roaming profile account?


 
Upvote 0 Downvote
C

crschil

Honorable
May 5, 2013
13
0
10,520
I managed to solve this myself with some repetitive troubleshooting.

iknowhowtofixit was on the right track, but it wasn't the Computer Name, but some combination of the specific computer and the specific user.

Here's what I isolated it to:

  • ■ My account was able to log into any other machine in the domain without any problem and a local profile was created.
    ■ Another user account that had not previously been associated with my laptop was able login and have a profile created
    ■ If I removed the laptop from the domain, the users I used to test the previous bullet would get a temp profile upon logging in.
    ■ If I changed the name of the computer, the problem persisted
    ■ If I removed or reset the machine in the domain (via the Server's Administration Tools), the problem persisted

I'm left with the conclusion that there must have been some association between the user account and the specific laptop hardware that was not easily found.

So to fix, I just deleted the user account from the Server and recreated it. Once that was done, I was able to login and get a profile created.
 
Upvote 0 Downvote
Solution
D

danny2000

Splendid
Sep 14, 2010
2,523
0
21,460
If you remove the entry from the domain, you should also remove the computer from the domain, at the computer itself. Reboot, and then try to rejoin the domain on the computer.

The original SID for that computer/laptop was erased (from the computer/laptop itself) when Windows was re-installed.

Usually, when you remove the computer from the domain (on the computer iteself), and reboot, and then go into the user accounts applet in Control Panel, you will then see the user accounts displayed with only SIDs. If the computer, was removed on the server itself, you'll usually see the correct usernames displayed in Control Panel.

The basic problem was that the computer itself, was not allowed to be a part of the domain, because the SID had been wiped out on the computer.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom