Discussion Locked

Logging in in Windows NT - problem

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Two computers, both Windows NT machines. Computer 1 running service pack 5, computer 2 with SP6. If computer 2 is on and someone is logged in, then when you try to log in on computer 1, (as a different user entirely, mind you), computer 1 will getas far as accepting name and password, and will show the wallpaper for the user, but will just sit there then, no icons or start button. Mouse moves ok. It will sit there until you log out of computer 2, whereupon computer 1 will then show icons and start menus and all that. These two machines are not sitting next to each other, although they are on the same network and same switch. They use different IP's, have different names in network properties, different product ID numbers. To make this a little more aggrivating, if you log on to computer 1 first THEN log on to computer 2 secondly, they both work fine. Any ideas? This is pretty weird to me.

15 replies

by cdwangs

Just thought I'd add this: There are other Windows NT machines on the network, but these two computers I am talking about seem oblivious to them. The only computer that seems to have any problems at all is computer 1, and then only with computer 2. Computer 2 works great always, regardless of how computer 1 is acting.

by mckaytech

My initial reaction is "Hey, this sounds like a profile problem - probably a corrupted roaming profile." But then I'm not so sure, but here are some ideas for things to check:
1. Does this only happen with certain user accounts or with any account(or a newly created test account)? Do you have roaming profiles or local only?
2. Was this machine built from a Ghost image and the security ID not fixed?
3. Is there a WINS problem? Look at the WINS database for conflicting records.
4. Is there anything in the Event logs to suggest the problem? If you implement detailed logging of security events, then do you get any messages in the Event log?

But when all is said and done, I'd still bet on a profile problem but I'd bet small.

paul

by cdwangs

1.) Happens with any user account, including newly created test accounts. Exception: the administrator account. I tried adding admin right to the exisiting accounts with no effect. Local profiles only.

2.) Not built from image.

3.) There doesn't appear to be a WINS account. This isn't a server, so there is no winsadmn.exe to run to check.

4.) Nothing in the event logs appears to have anything to do with this. Normal messages only.

by lbischofs

Did you by chance happen to use the same IP address for these machines? Or more specifically does machine 1 have an address already in use by another machine?

by cdwangs

IP addressing for these systems is handled by DHCP, and are unique on the system.

by libran_76

check for the cable attaching to the network for that particular machine and also try to remove the network card drivers and reinstall them ifu can get one try changing it coz i think this is the problem of the nic
try it out maybe it will help

by cdwangs

A few more things of Interest:

1st system will always allow the administrator account to log in, regardless of the status of the 2nd system.

1st system accounts granted administrator rights still can't log in when second system on.

Newly created test accounts on 1st system have the same problem as existing accounts.

The 2nd system doesn't actually have to be logged in for these symptoms to occur. If the "Begin Login" window is up (press control-alt-del to login), that's enough to make the first system accounts not be able to log in.

by stuff

Not much, but a suggestion.

I agree with pmwright, it does sound like a profile. As this occurs with all users first thing that comes to my mind is that maybe one or more of the files in all users profile are shared, or that one of the dats is shared.

Second thing is MAC addresses, you rejected the guy that suggested swapping NIC, have you actually tried this.

I have not seen either of the above, so I don't know what error messages these would raise.

Have a nice day.

Chris

by james_randy

Since that question is so old, and you rejected all those answers, why don't you just close your question?

This discussion is closed to new replies.