Access to shares lost after install of XP SP2

Last December a client of mine got a new laptop and we connected it to the
SBS 2000 network. I did not put on the firewall client as using the proxie
settings provided everything we needed. I did this with two laptops that they
got at that time.

Last month, one of them was not able to print and took forever to log in. I
discovered it was basicly hanging trying to authenticate and would eventual
time out. If the laptop was not connected to the network it logged in just
fine with the cached credintials. When I did a run line \\serverName I would
normally get a list of shares but it would come up after a long time with a
blank window. I did everything I could think of then resorted to building it
from scratch. Once I did that it worked fine so I proceeded to load patches
and service pack2 and more patches. I then found that I lost my
authentication again to the server. So again I rebuilt it and would test
authentication after each of the updates. After the Service Pack 2 update was
applied, that was when I lost authentication.

Is there a patch that needs to be appliced to the SBS 2000 server so that an
XP SP2 client can authenticate?

Thanks for any help you can provide.

Duncan
Mon Sep 12 04:02:55 CDT 2005

In article <7615EC54-71D5-4203-AED1-3DAF2E7C7F54@microsoft.com>,
GWRiderNW@discussions.microsoft.com says...
> Last December a client of mine got a new laptop and we connected it to the
> SBS 2000 network. I did not put on the firewall client as using the proxie
> settings provided everything we needed. I did this with two laptops that they
> got at that time.
>
> Last month, one of them was not able to print and took forever to log in. I
> discovered it was basicly hanging trying to authenticate and would eventual
> time out. If the laptop was not connected to the network it logged in just
> fine with the cached credintials. When I did a run line \\serverName I would
> normally get a list of shares but it would come up after a long time with a
> blank window. I did everything I could think of then resorted to building it
> from scratch. Once I did that it worked fine so I proceeded to load patches
> and service pack2 and more patches. I then found that I lost my
> authentication again to the server. So again I rebuilt it and would test
> authentication after each of the updates. After the Service Pack 2 update was
> applied, that was when I lost authentication.
>
> Is there a patch that needs to be appliced to the SBS 2000 server so that an
> XP SP2 client can authenticate?

My advice would be to 'rejoin' the computer to the domain. To do this
(and I'm hoping someone can better my solution) you simply:
* change the logon to a Workgroup logon, and then
* change the logon back to the domain (rejoin the domain)

The problem is that as a <username>.<domain> folder already exists under
"Documents & Settings" - it will make a new one (and you'll lose the old
settings).

I'm hoping someone might be able to suggest an easy way around that
problem (the old files under that old folder can still be copied accross
manually, but, for eg. you'll lose the desktop background).

Perhaps there is a smart way of renaming things - anyone???

But certainly, I think rejoining the computer to the domain will fix
your problem.

--
Duncan

Duncan
Mon Sep 12 04:03:05 CDT 2005

In article <7615EC54-71D5-4203-AED1-3DAF2E7C7F54@microsoft.com>,
GWRiderNW@discussions.microsoft.com says...
> Last December a client of mine got a new laptop and we connected it to the
> SBS 2000 network. I did not put on the firewall client as using the proxie
> settings provided everything we needed. I did this with two laptops that they
> got at that time.
>
> Last month, one of them was not able to print and took forever to log in. I
> discovered it was basicly hanging trying to authenticate and would eventual
> time out. If the laptop was not connected to the network it logged in just
> fine with the cached credintials. When I did a run line \\serverName I would
> normally get a list of shares but it would come up after a long time with a
> blank window. I did everything I could think of then resorted to building it
> from scratch. Once I did that it worked fine so I proceeded to load patches
> and service pack2 and more patches. I then found that I lost my
> authentication again to the server. So again I rebuilt it and would test
> authentication after each of the updates. After the Service Pack 2 update was
> applied, that was when I lost authentication.
>
> Is there a patch that needs to be appliced to the SBS 2000 server so that an
> XP SP2 client can authenticate?
>
> Thanks for any help you can provide.

Perhaps Michael's advice might help, re another post he replied to:

Hello,

Your old version of the server creates a unique ID per each computer and
user account on the system. When you created the new version of the
server, the ID's of the local workstations do not appear or match what
is on the new server, hence you need to unjoin and rejoin. This deletes
the domain information on the local machine and recreates a new account
on the network server with a new ID. Doing this, now means, a user
logging on is not using the locally stored profile, rather a new profile
from the server as the user has a new ID and is treated as a different
person to the original person. They may have the same logon name but the
ID is different. Servers work with the ID's not the names and the
ntuser.dat file etc will all nolonger correspond with the logged in
users information.

there are various migration kits available for profiles. You can also
copy the users old profile to the local default user profile (on the
workstation) and when you log on for the first time, merge this with the
new logon profile.

Other than this, you can manually copy over internet favorites and many
other items but not everything can be transplanted in this way.


Vandenberghe Filip wrote:

> Hello
> can some tell me how to fix this problem i have.
> had crash on the server ,
> reinstalled from scratch.
> all settings are the same ,
>
> still users can not logon this domain.
> if i unjoin the the previous domain and reconect user can logon but all
> settings from user are lost
>
> best regard
>
>

--
Michael J. Jenkin MVP - SBS, Senior Systems Engineer
Visit http://www.mickyj.com

Microsoft Most Valued Professional, Microsoft's Windows Server Systems -
Small Business Server
MVP's do not work for Microsoft. If this email was generated in a
newsgroup, please reply only to the newsgroup.
Note: The contents of my postings and responses here represent my
personal opinions and do not necessarily reflect the views, thoughts or
feelings of Microsoft or any of its employees.
http://mvp.support.microsoft.com


--
Duncan

GWRiderNW
Mon Sep 12 21:06:01 CDT 2005

I guess I should have cleared that up before hand but before I rebuilt the
system, I did delete and create new profiles and tried other user accounts
and this did nothing. I even changed the computer name and deleted the system
from the domain before adding it. I added it from the computer and tried
again from the server. Nothing worked. So I resorted to rebuild.

After rebuilding the system, I would only log in to the computer with the
Domain Administrator account and it worked fine up to the point of installing
Service Pack 2. All security patches prior to the install of Service Pack 2
did not restrict the access to authenticate. I am fairly sure that it is an
issue with SP2. I thought before it come out there was talk of a patch for
the SBS 2000 server you needed to apply before updating the XP clients to SP2.

More help please? :)



"Duncan McC" wrote:

> In article <7615EC54-71D5-4203-AED1-3DAF2E7C7F54@microsoft.com>,
> GWRiderNW@discussions.microsoft.com says...
> > Last December a client of mine got a new laptop and we connected it to the
> > SBS 2000 network. I did not put on the firewall client as using the proxie
> > settings provided everything we needed. I did this with two laptops that they
> > got at that time.
> >
> > Last month, one of them was not able to print and took forever to log in. I
> > discovered it was basicly hanging trying to authenticate and would eventual
> > time out. If the laptop was not connected to the network it logged in just
> > fine with the cached credintials. When I did a run line \\serverName I would
> > normally get a list of shares but it would come up after a long time with a
> > blank window. I did everything I could think of then resorted to building it
> > from scratch. Once I did that it worked fine so I proceeded to load patches
> > and service pack2 and more patches. I then found that I lost my
> > authentication again to the server. So again I rebuilt it and would test
> > authentication after each of the updates. After the Service Pack 2 update was
> > applied, that was when I lost authentication.
> >
> > Is there a patch that needs to be appliced to the SBS 2000 server so that an
> > XP SP2 client can authenticate?
> >
> > Thanks for any help you can provide.
>
> Perhaps Michael's advice might help, re another post he replied to:
>
> Hello,
>
> Your old version of the server creates a unique ID per each computer and
> user account on the system. When you created the new version of the
> server, the ID's of the local workstations do not appear or match what
> is on the new server, hence you need to unjoin and rejoin. This deletes
> the domain information on the local machine and recreates a new account
> on the network server with a new ID. Doing this, now means, a user
> logging on is not using the locally stored profile, rather a new profile
> from the server as the user has a new ID and is treated as a different
> person to the original person. They may have the same logon name but the
> ID is different. Servers work with the ID's not the names and the
> ntuser.dat file etc will all nolonger correspond with the logged in
> users information.
>
> there are various migration kits available for profiles. You can also
> copy the users old profile to the local default user profile (on the
> workstation) and when you log on for the first time, merge this with the
> new logon profile.
>
> Other than this, you can manually copy over internet favorites and many
> other items but not everything can be transplanted in this way.
>
>
> Vandenberghe Filip wrote:
>
> > Hello
> > can some tell me how to fix this problem i have.
> > had crash on the server ,
> > reinstalled from scratch.
> > all settings are the same ,
> >
> > still users can not logon this domain.
> > if i unjoin the the previous domain and reconect user can logon but all
> > settings from user are lost
> >
> > best regard
> >
> >
>
> --
> Michael J. Jenkin MVP - SBS, Senior Systems Engineer
> Visit http://www.mickyj.com
>
> Microsoft Most Valued Professional, Microsoft's Windows Server Systems -
> Small Business Server
> MVP's do not work for Microsoft. If this email was generated in a
> newsgroup, please reply only to the newsgroup.
> Note: The contents of my postings and responses here represent my
> personal opinions and do not necessarily reflect the views, thoughts or
> feelings of Microsoft or any of its employees.
> http://mvp.support.microsoft.com
>
>
> --
> Duncan
>

Duncan
Mon Sep 12 21:37:25 CDT 2005

In article <30107B58-0D98-4A4B-B28C-88A7778F4F7D@microsoft.com>,
GWRiderNW@discussions.microsoft.com says...
> I guess I should have cleared that up before hand but before I rebuilt the
> system, I did delete and create new profiles and tried other user accounts
> and this did nothing. I even changed the computer name and deleted the system
> from the domain before adding it. I added it from the computer and tried
> again from the server. Nothing worked. So I resorted to rebuild.
>
> After rebuilding the system, I would only log in to the computer with the
> Domain Administrator account and it worked fine up to the point of installing
> Service Pack 2. All security patches prior to the install of Service Pack 2
> did not restrict the access to authenticate. I am fairly sure that it is an
> issue with SP2. I thought before it come out there was talk of a patch for
> the SBS 2000 server you needed to apply before updating the XP clients to SP2.
>
> More help please? :)

Anything in the Event Log that you can post here?

--
Duncan

GWRiderNW
Wed Sep 14 17:40:03 CDT 2005

Nothing in either server or client logs. Indicators are that the explorer
window before SP2 shows all the server's shares and after SP2 the explorer
window still opens after a very long time but the window is empty. So it
knows the server is there but it is not authenicating or timing out on
authentication to know to show any shares. Testing is done by typing
\\ServerName from a run line.

Do you have to have the SBS client installed once you have SP2? Non of the
other sytems that are running SP2 are running into this.

-John

"Duncan McC" wrote:

> In article <30107B58-0D98-4A4B-B28C-88A7778F4F7D@microsoft.com>,
> GWRiderNW@discussions.microsoft.com says...
> > I guess I should have cleared that up before hand but before I rebuilt the
> > system, I did delete and create new profiles and tried other user accounts
> > and this did nothing. I even changed the computer name and deleted the system
> > from the domain before adding it. I added it from the computer and tried
> > again from the server. Nothing worked. So I resorted to rebuild.
> >
> > After rebuilding the system, I would only log in to the computer with the
> > Domain Administrator account and it worked fine up to the point of installing
> > Service Pack 2. All security patches prior to the install of Service Pack 2
> > did not restrict the access to authenticate. I am fairly sure that it is an
> > issue with SP2. I thought before it come out there was talk of a patch for
> > the SBS 2000 server you needed to apply before updating the XP clients to SP2.
> >
> > More help please? :)
>
> Anything in the Event Log that you can post here?
>
> --
> Duncan
>