SMS w/ W2K SP2 login issue

[plindqui]

Have an issue with a few W2K computers where it seems the combination of SMS and Service Pack 2 causes the login process to become so slow that it does not log in a user to the workstation.

Computers are W2K with service pack 2
SMS is service pack 3

If W2K SP2 is removed, PC works ok
If SMS client is removed, PC works ok

Symptoms are the PC boots, but is extremely slow in bringing up the login GUI. Once the login comes up and the user enters in their ID and password, the PC never reboots. This happens with any user. It does not happen if the network cable is pulled (This is how I got on the PC to remove SP2 or SMS client).

By examining the security log, I discovered that if I replace the msv1_0.dll with the W2K SP1 version, the PC works ok. Was hoping someone might have an idea as to what is happening as this does not happen to every PC. Any help is much appreciated.

Possible other clues: I am currently having an issue where I am unable to remotely access the Computer Management on another W2K machine unless I use the IP address instead of the workstation name. Was told this is a WINS issue.

Also am having an issue where I was receiving an out of memory error when trying to add a domain user to a local group from a local PC. Solution from MS was to add SP2 for W2K and that is where the SMS issue first came into play.

 

[jasonbauer]

plindqui;

I am having the exact same problem, and was curious to know if you had found anything.

We have recently purchased a slew of new IBM workstations that require SP2. Once the SMS client is installed, the user is unable to startup the computer. They will see the message: "Preparing Network Connections" for a good 1-2 minutes, and then "Applying computer settings" at which point the computer is hung. If we bring the computer up without the network cable in, all is well.

I originaly thought it was a W2K DNS issue, but have narrowed it down to the combination of SMS2 sp3 and W2K sp2.

Let me know if have any ideas, as I am stuck.

Thanks in advance.
Jason

 

[plindqui]

Thanks for posting to my problem. The only thing we've been able to figure out so far is that if I replace the msv1_0.dll with the version from W2K SP1, everything works again. From what we've been able to tell, something is going on with the way the machine is authenticating users to the network. When the machine is stalled out, it appears to be trying to login the SMS accounts.

What is very interesting to me is that we also run IBM machines. However, the problem is sporadic and not necessarily related to one model. We've got a couple Netvista A40's, a thinkpad A21M, and some PL300's with the problem. We were also thinking that this might be related to W2K DNS and would be interested to know how you eliminated this as a possible culprit.

We were contemplating calling Microsoft with this one, but since the problem is sporadic, we were told they wouldn't be much help.

Do you have any other helpful info?

Thanks
Pat