Windows 7 / Windows 8 casual users can't connect to Win 2000 SBS shares

First, I know that many responses will say Windows 2000 SBS is obsolete and unsupported. I know this. We maintain this server for access to a legacy application that will not run on newer hardware/software.

Most of our users are authenticated by logging in to the domain. These users have no trouble accessing the shares on our W2000SBS server. There are several casual users who do not log in to the domain. They access network shares by authenticating at time of connection to each share. This has worked fine for with clients running XP, Win7 and Win8 as recently as last week. Today casual XP users can authenticate a share connection, but Win7 and 8 users can not. They get a password failure message.

Over the weekend numerous Windows updates were applied to the W2000SBS server. It is possible that one of these updates broke the connection to Win 7/8 machines. I don't know if the WIn 7 / 8 machines have received updates since the last time this worked.

We are planning to move all of the shared data off of this server in the next several weeks, but in the mean time these casual users need access. Is there anything I might be able to do, short of rolling back the updates, that might allow these users to connect to the shares?

I'm willing to accept that it will not work with the last updates to W2000SBS if there is a logical reason other than that the OS is obsolete.

Thank you.
Who is Participating?
Seth SimmonsSr. Systems AdministratorCommented:
authentication mechanism is different; thus the windows 7/8 connection issues with older windows server versions that either don't support it (because it didn't exist then) or by default didn't use it

You cannot access a shared folder that is located on a Windows 2000 or Windows 98-based computer from a Windows 7-based computer

you could try rolling back the updates
BRT-TechAuthor Commented:
Thanks for the link Seth.  Sounds like one of the updates may have either changed the registry, or added NTLM V2. I'll give their suggested fix a try. If it doesn't work I'll probably just tell the users they are out of luck until we can migrate the data to up-to-date hardware/software.  One is an upper manager and has some clout to get things done. I really have no desire to spend much time on this.

I'll report back tomorrow and let you know if it worked.
BRT-TechAuthor Commented:
Interesting.   My server has three Control Sets. ContolSet001, ControlSet002 and CurrentControlSet. The value referenced by the KB article was set in ControlSet001, but not in 002 and Current. There is a good possibility one of the updates changed the Control Set breaking the compatibility mode.

I won't know for sure until I reboot tonight after hours and test with the user tomorrow, but I think you earned the points with an excellent KB reference link.
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

BRT-TechAuthor Commented:
Just a quick follow up. The registry change didn't help.  Users that log in to the domain do not have any problems regardless of client OS.

I convinced the user she needs to become a domain member by upgrading their OS to Win 7 Pro.
BRT-TechAuthor Commented:
Just closing out this old question.   We never resolved the problem, but upgraded the client to Win 7 Pro to authenticate with the server. All is well with shares using Pro and logged in to the domain.

Also - I did finally talk the owner into upgrading to Server 2012 Essentials. I am preparing the new machine now and will be retiring 2000 SBS soon.
BRT-TechAuthor Commented:
We didn't resolve the problem - but accepted that it wasn't going to work with the updated OS.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.