Workstation logon problem

Recently upgraded from Server 2000 to SBS 2003. Everything was fine the
first two weeks, but then started experiencing a problem on a couple of
(Windows 2000) workstations. If the user logs off, but leaves the computer
turned on overnight, there is no issue. However, if the computer is turned
off, even for a few minutes, and then is turned back on again, there is a
connectivity problem after booting up. The user . . . any domain user,
including the administrator . . . can log on to the domain, but (regardless
of the user) there is no access to the server. If using either a mapped
network drive or browsing the network to gain access to the server a login
screen pops up asking for a UserID and password. No UserID/Password
combination (including the Administrator account) is allowed to access the
server. To regain full connectivity, the only fix found so far is to
disjoin the workstation from the domain (change to "workgroup" workgroup and
remove the computer from the domain at the server) and then rejoin it. That
works until the next time the computer is shut down, and then we're back to
square one.

IP addresses all seem fine, regardless of whether static or dynamic
addressing is used. Both local (Exchange) email and internet email, as well
as web access, are fine. It's only the issue of accessing shared folders on
the server. Network Associates E-policy Orchestrator had been running
overnight, but we've tried disabling that and get the same results. Has
anybody experienced anything like this before?

go to this link first:
http://www.microsoft.com/hardware/br...s_fileone.mspx

If it doesnt work, i think you have to do the following:

1-Do what you have mentioned before (convert to workgroup then back to domain)
2-on the AD users and computers, reset that computer account.
3-Try to record the SID of that PC after each transaction.

"WF Peifer" wrote:

> Recently upgraded from Server 2000 to SBS 2003. Everything was fine the
> first two weeks, but then started experiencing a problem on a couple of
> (Windows 2000) workstations. If the user logs off, but leaves the computer
> turned on overnight, there is no issue. However, if the computer is turned
> off, even for a few minutes, and then is turned back on again, there is a
> connectivity problem after booting up. The user . . . any domain user,
> including the administrator . . . can log on to the domain, but (regardless
> of the user) there is no access to the server. If using either a mapped
> network drive or browsing the network to gain access to the server a login
> screen pops up asking for a UserID and password. No UserID/Password
> combination (including the Administrator account) is allowed to access the
> server. To regain full connectivity, the only fix found so far is to
> disjoin the workstation from the domain (change to "workgroup" workgroup and
> remove the computer from the domain at the server) and then rejoin it. That
> works until the next time the computer is shut down, and then we're back to
> square one.
>
> IP addresses all seem fine, regardless of whether static or dynamic
> addressing is used. Both local (Exchange) email and internet email, as well
> as web access, are fine. It's only the issue of accessing shared folders on
> the server. Network Associates E-policy Orchestrator had been running
> overnight, but we've tried disabling that and get the same results. Has
> anybody experienced anything like this before?
>
>
>

"Maamoun" <(E-Mail Removed)> wrote in message
news:0DDD5262-6FF5-484D-B43D-(E-Mail Removed)...
> go to this link first:
> http://www.microsoft.com/hardware/br...s_fileone.mspx
>
> If it doesnt work, i think you have to do the following:
>
> 1-Do what you have mentioned before (convert to workgroup then back to
domain)
> 2-on the AD users and computers, reset that computer account.
> 3-Try to record the SID of that PC after each transaction.

Sounds good. Any suggestions as to how to track the SID on the PC? Is
there a registry setting that I can access easily?

On the windows server 2003 the registry key is:
HKLM\SYSTEM\CurrentControlSet\Services\NWCWorkstat ion\Parameters\Logon

The SID for the user starts with S:

Example: "S-1-5-21-1004336348-1177238915-682003330-512"

"WF Peifer" wrote:

> "Maamoun" <(E-Mail Removed)> wrote in message
> news:0DDD5262-6FF5-484D-B43D-(E-Mail Removed)...
> > go to this link first:
> > http://www.microsoft.com/hardware/br...s_fileone.mspx
> >
> > If it doesnt work, i think you have to do the following:
> >
> > 1-Do what you have mentioned before (convert to workgroup then back to
> domain)
> > 2-on the AD users and computers, reset that computer account.
> > 3-Try to record the SID of that PC after each transaction.
>
> Sounds good. Any suggestions as to how to track the SID on the PC? Is
> there a registry setting that I can access easily?
>
>
>

I forget,

Before you try that, you have to notice that the SID subkey appears in the
registry when you install Client Service for NetWare.

For More Info, see :

http://www.microsoft.com/technet/pro...f6373a5ab.mspx

"WF Peifer" wrote:

> "Maamoun" <(E-Mail Removed)> wrote in message
> news:0DDD5262-6FF5-484D-B43D-(E-Mail Removed)...
> > go to this link first:
> > http://www.microsoft.com/hardware/br...s_fileone.mspx
> >
> > If it doesnt work, i think you have to do the following:
> >
> > 1-Do what you have mentioned before (convert to workgroup then back to
> domain)
> > 2-on the AD users and computers, reset that computer account.
> > 3-Try to record the SID of that PC after each transaction.
>
> Sounds good. Any suggestions as to how to track the SID on the PC? Is
> there a registry setting that I can access easily?
>
>
>