Server Accesibility Problem

[Nando Kidd]

I have a Windows 2000 Server which is a Primary Domain
Controller (PDC). One of my workstations (Windows XP Pro)
Logs in to the server ok, but losses access rights to the
server at any moment yielding the error message:
["\\Server_name" is not accesible. You might not have
permission to use this nerwork resource]. When I Log-in
and run an application on the server immediately it works,
but if left alone or simply not accessing anything on the
server for a period of time, then I'm not able to access
the server and receive the above error. If I log-off then
log-in again, the access rights are restored. I don't
restart, just a simple log-off and log-in solves the issue
for the moment. The network and NIC are OK because I can
ping the server successfully. NO firewalls installed on
either machine. I disabled the option to disconect
inactive session both on server and workstation. Made
sure that both the user and computer (workstation) exist
in the domain's active directory. User is also a member
of administrators' group, so priviledge shouldn't be a
problem.

Any ideas what the problem could be?

 

[Steven Umbach]

I don't know if that is the only XP Pro computer on your domain or the only one
you are having a problem with, but there have been reported problems with XP Pro
computers in a W2K domain if smb signing is used [I don't know if it has been
fixed yet or is waiting for XP SP2]. I would first look in the Local Security
Policy of the XP computer in security options and make sure that the two options
for digitally sign communications (always) are disabled. If you can not disable
that at the local level, then you may have to disable it at the domain/OU level.
Then run secedit /refreshpolicy machine_policy /enforce on the domain controller
and then reboot the XP computer. If that does not help, try to temporarily
disable all four options for digitally sign communications in Domain Security
Policy and Domain Controller Security Policy and for any OU where it may be
configured for computers in the OU. I would also check the lan manager
authentication level for the XP computer and set it to be "send ntlmv2 responses
only" which is a safe but compatible level to use in a domain. If none of that
helps look at the article below on changing the registry setting on the client
computer to force it to use TCP for kerberos which I doubt is the problem but
may be worth a try if nothing else seems to work.

First before the above though, double check that dns is configured correctly on
the computer in that it is using ONLY the W2K domain controller as it's
preferred dns server in tcp/ip properties as shown by ipconfig /all and run
netdiag on it looking for any failed tests/fatal warnings and check for messages
in Event Viewer that may help pinpoint the problem. I know you said that there
is no personal firewall on the computer but double check that the built in ICF
firewall for XP Xpro is also disabled. Also check the nic settings, and try
using 100 as network speed instead of auto and check that the nic is not going
into a power down mode after a certain idle time if there is such a setting for
it. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;244474
http://support.microsoft.com/default.aspx?scid=kb;en-us;321708

I have a Windows 2000 Server which is a Primary Domain
Controller (PDC). One of my workstations (Windows XP Pro)
Logs in to the server ok, but losses access rights to the
server at any moment yielding the error message:
["\\Server_name" is not accesible. You might not have
permission to use this nerwork resource]. When I Log-in
and run an application on the server immediately it works,
but if left alone or simply not accessing anything on the
server for a period of time, then I'm not able to access
the server and receive the above error. If I log-off then
log-in again, the access rights are restored. I don't
restart, just a simple log-off and log-in solves the issue
for the moment. The network and NIC are OK because I can
ping the server successfully. NO firewalls installed on
either machine. I disabled the option to disconect
inactive session both on server and workstation. Made
sure that both the user and computer (workstation) exist
in the domain's active directory. User is also a member
of administrators' group, so priviledge shouldn't be a
problem.

Any ideas what the problem could be?