Is there a reason to upgrade from Windows Server Update Services (WSUS) 2.0 to 3.0?
I have a Windows 2003 Small Business Server currently running WSUS 2.0 serving 7 Windows XP client machines.
Is it worth it to upgrade? What are the benefits? Does it require re-configuring all the client machines?
Or should I just "leave well enough alone?"
I've got a situation where a client computer (Windows Vista) doesn't seem to be sending the right password to a server (Windows Server 2003).
The event log records the logon failure, but as far as I can tell the client has the right password - so I'd really like to know what is actually being sent back & forth between the two computers as they try to negotiate the logon.
Is there any way to monitor/trace/examine a Windows logon session? (I assume a plain packet capture wouldn't work, since the passwords aren't sent in plain text - at least I hope not!)
MORE INFO: The server is the only server on the network. The computers are all on the same subnet, 192.168.1.xxx. The client computer is not a member of the domain. The server computer is the DNS server - and the client computer can correctly resolve the server's address without any problems.
The following events are logged in the event log:
MICROSOFT_AUTHENTICATION_PACKAGE_V1_0, which fails with code 0xC0000234All the client computer is trying to do is connect to a network share (mapping a network drive, actually).
I have a Windows Vista (Ultimate) machine which connects to a Windows Server 2003 machine for just one thing: a mapped network drive.
There is a user account on the Server machine which exactly matches the user name & password on the Vista machine.
The problem is... when I try to connect (map) the network drive, a message comes up saying the user name or password was incorrect! Since it then gives you the opportunity to re-enter the user name and password, I re-enter the password (exactly the same, again) and it works and the drive gets mapped.
BUT... the plot thickens! After a reboot (or, I suppose, a log-off and log-on), the network drive doesn't work anymore - double clicking it gives a short delay, and then a message saying the drive can't be reconnected because the account has been locked out. Sure enough, checking on the server shows the account locked out. A glance at the event log shows repeated "invalid password" events before the account is eventually locked out.
The specific events that are recorded are:
MICROSOFT_AUTHENTICATION_PACKAGE_V1_0, which fails with code 0xC0000234Both machines are using the same LAN manager authentication method (specifically, "Send LM & NTLM, use NTLMv2 session security if negotiated") - set via security policy.
The Vista machine is not part of the domain, but the user name and password match.
The Vista machine used to work just fine, back when it was an XP machine. But then, it got upgraded to Vista (not a clean re-install, an actual upgrade) and this is what happens now.
For the life of me, I cannot figure out why it seems to be sending the wrong password, when I have checked & double-checked to make sure the password is exactly the same. I've googled & googled and found nothing useful. I'm stumped!
Does anyone have any ideas as to what might be happening here - or ideas for further troubleshooting steps I can take?
UPDATE: I've tried mapping the drive via the command line and the NET USE command - but it throws up its hands as well, with a "system error 86" which says "the specified network password is not correct." Your guess is as good as mine as to what's really going on here. I wish I could sniff the actual traffic going back & forth between the computers and see what password (if any!!) is being sent...