[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Domain Login Issues

Hello,
I do IT support at a private school where we have a network of 25+ computers with the server running Windows Server Standard. We utilize a domain scenario whereby each computer uses a specific DNS server to point them to the domain. In my lab of 17 computers I had a computer that needed a new power supply the other day and I changed it out. Not sure if having the case open, etc contributed to the problem or not, but I realize it becomes part of the troubleshooting issue, so I mention it.

I run DeepFreeze on these computers, which is a program that reverts the HD back to it's original state each time it is rebooted. Because of this, it only keeps the generic domain user and mine in the user information. All others utilize the Default username to set up their desktop etc. Their username is stored on the computer until it is rebooted. All computers in the lab are Dell Vostro 200 running Windows Vista Business.

This computer that I'm having an issue with, will allow the generic and my login whereby these can access all the network resources, but if a "new" user attempts to log in, it gives the "username or password not recognized" error.

Other pertinent info:
When I look at the users in the computer/properties/adv sys settings, I see several "Unknown Accounts".
It's definitely not a user issue (i.e password, expired/locked account, etc).
It's definitely related to this system specifically (as opposed to its location)
DNS server is set correctly.

Help anyone? Thanks!
0
NCDebbi
Asked:
NCDebbi
  • 3
  • 2
  • 2
1 Solution
 
JBond2010Commented:
The way DNS should be setup is the User PCs should using the ip address of the Domain Controller that is performing DNS. This is typically configured in the DHCP Scope Options provided you are using DHCP on your Server and not your Router/Firewall.

Can you confirm how DNS is configured on your LAN and also DHCP.


Thank you,

JBond2010
0
 
Justin OwensITIL Problem ManagerCommented:
If you have verified that DNS is correctly set up (because that is integral to AD health, as JBond2010 points out) as I believe it will be, then it appears that you have lost a trust relationship between the computer and the Directory.  

1. Disjoin the computer from the domain.
2. Reboot.
3. Rejoin the domain.

This should resolve your issue.

DrUltima
0
 
Justin OwensITIL Problem ManagerCommented:
ADDENDUM:

This lost trust happens for several reasons, some of which are new hardware makes AD think it is a new computer, being offline longer than the AD tombstone, etc.  It is not ultra common, but it is also not at all uncommon.

DrUltima
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
NCDebbiAuthor Commented:
All computers in the labe are configured to have their IP addresses configured automatically and are handed out by our main switch. These are all connected in the lab via a switch and are then connected to one port on the main switch. Also, all computers are set to the IP address of the Domain Controller in the network settings in the IPV4 properties under "Use the following server DNS addresses"

All other computers in the lab are working fine and users can log on without issue.
Thanks,
Debbi
0
 
JBond2010Commented:
As DrUltima has pointed out disjoin the PC from the Domain and then restart the PC and then rejoin back to the domain and see does this help.
0
 
NCDebbiAuthor Commented:
Wow! I've had to change out two other power supplies on these lab machines and it didn't do that before, so I'm very suprised that it DID work! Disjoin, reboot, rejoin, reboot...login successful!!!

Thanks to both of you for your quick responses and to you, DrUltima for the fix :)
0
 
Justin OwensITIL Problem ManagerCommented:
Glad that worked for you.  Honestly, the power supply issue was most likely an extenuating circumstance rather than causal in this case.  Thank you for accepting my Answer.  Remember, if you ever need similar assistance, you can "Ask a Related Question" from this Question in order to alert the Experts who participated in this one as well as the Experts who monitor your new Question's assigned Zones.

DrUltima
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
Tackle projects and never again get stuck behind a technical roadblock.
Join Now