Login not always working (Server 2003)

One of our clients on a Windows 2003 server network, they are running Win 7 Pro on the workstation. All users login via a login script whcih maps a shared server area to the "S" drive and displays a Welcome dialogue.

For a while one of the users has experienced an intermittent problem that the mapping doesn't work and she does not see the welcome dialogue. This would imply the login script isn't working. She has to re-start her PC a few times before it maps properly.

It is only one user out of 15 on the network which experiences this. Earlier this year we completely re-installed her PC (for other instability reasons too), but this problem still occasionally persists. Yesterday despite re-starting a few times, drive S wouldn't map.

However, when I Remote Desktopped in it logged in first time, showed welcome dialogue and mapped the "S" drive. Why would Remote Dekstop work, but not, apparently when she logs in normally?

Any ideas?
LVL 1
gerlisAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,

Purely guessing here but i get the feeling it has something to do with the memberships to security groups this user has.

You could try to mirror it to the account you were using when RDP into this machine (assuming you didnt use a overweighted domain admin account) and try again. If succesfull you can bring the memberships back one by one and see where the conflict starts.
0
SommerblinkCommented:
I know that you said that the computer was wiped and you indicated that it is a "PC", but a couple questions to firm things up.

Are the DNS settings correct for the network card in this user's PC. (No non-AD DNS configured). This being incorrectly configured could manifest as an intermittent problem.

If these have been tried / do not apply, how about the physical network cable connection? Have you tried connecting the computer to another network jack, both at the desk and at the switch?

I would be interested in seeing if there are any NETLOGON 5719 errors in the System log indicating that there were no logon servers present to service the logon request. This may as well indicate that there was an early networking problem which prevented the computer from accessing the network location where the script is located at (among other things).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gerlisAuthor Commented:
Thanks, Chaps, we'll look into these.

But to let you know, I set up a manual mapping yesterday but this morning when the user logged on even that didn't work. She called me and I took her through re-stablishing the manual mapping and it worked,. So seems that at the point of start-up/logging on. the problem occurs whcih my well imply a hardware problem withe nic in the PC, or wall socket. Next week we will connect her PC to another nearby socket.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

gerlisAuthor Commented:
I plan today to swap her network cable into another, nearby, socket. We'll see if her computer behaves when logging on and/or the other computer that is swapped also exhibits the mapping problem on logon.

We'll probably leave it for a few days to see how it goes.
0
Patrick BogersDatacenter platform engineer LindowsCommented:
I cannot see why this would help since you log on everytime correctly over RDP.
IMHO it could be some form of security or authentication/profile error.

Did you try to remove this workstation from the domain and have it rejoin it?
0
gerlisAuthor Commented:
Good point, but let's see if moving the cables makes a difference. We'll leave it for a few days

Else we'll take it off the domain and put it back on, as you suggest.
0
SommerblinkCommented:
Because being ABLE to RDP to the local computer PROVES that the network is working.

But login scripts which are located on a network share are necessarily unavailable if the network is not working, even though the user will still login using cached credentials. (Given default behavior.)

Also, you did not report back if you saw any of those NETLOGON errors in the event viewer. This would indicate a cached logon.
0
gerlisAuthor Commented:
Since swapping cables a week ago, the user has not reported any mapping problems at logon.
0
gerlisAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for gerlis's comment #a39475907

for the following reason:

Discovered the solutin ourselves. We suspect a dodgy network socket
0
SommerblinkCommented:
I object.

My comments 39449273, 39464148 and 39464148 precisely predicted this as a possible source of the problem.
0
gerlisAuthor Commented:
Your comment in 39449273 did mention this, sorry I missed it when reviewing the question.

I will therefore award you the points.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.