Can't access W2K shares after approx 24 hours

[news.microsoft.com]

Hi

I have couple of WinXP Pro pcs, connected to W2K Server.

Just reinstalled W2K server (with AD) recently due to HDD crash.

Now I find after approx 24 hours the WinXP pc's don't have permission to
access the shared directories on W2K server. When they login to the domain
they have permissions and no problems.

However after 24 hours or so (not sure exactly how long - seems to be
overnight some time this hapens) all the WinXP pc's can't access the shares.
They can see the domain + W2K server in 'Microsoft Widonws Network' in
windows explorer however don't have permission to view the shares. When I
clikc the shared directory, a popu box asks for username + password, but I'm
logged into the domain as Administrator and have max possible rights.

Any clue to this weird problem please?

Thanks
Harry

 

[Lanwench [MVP - Exchange]]

Hi

I have couple of WinXP Pro pcs, connected to W2K Server.

Just reinstalled W2K server (with AD) recently due to HDD crash.

Now I find after approx 24 hours the WinXP pc's don't have permission
to access the shared directories on W2K server. When they login to
the domain they have permissions and no problems.

However after 24 hours or so (not sure exactly how long - seems to be
overnight some time this hapens) all the WinXP pc's can't access the
shares. They can see the domain + W2K server in 'Microsoft Widonws
Network' in windows explorer however don't have permission to view
the shares. When I clikc the shared directory, a popu box asks for
username + password, but I'm logged into the domain as Administrator
and have max possible rights.

Any clue to this weird problem please?

Thanks
Harry

My first question is, why aren't all your users logging out when they leave
at the end of the day? They should be!

Second - have you seen
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q138365&

 

[harry]

I'll try that now

Thank you!


"Lanwench [MVP - Exchange]"

 

[Steven L Umbach]

When you reinstalled, did you rebuild the domain or was this an additional domain
controller?? The proper way to reinstall a dead dc is to restore via Directory
Services restore Mode from a backup that includes the System State. I would run
netdiag and dcdiag on your domain controller looking for configuration problems and
run netdiag on one of those clients next time it "disconnects" to see if it reports
errors such as failed tests. Dns misconfiguration is the usual culprit in that the
domain controller needs to point to itself or the pdc fsmo as it's only preferred dns
server and the domain clients need to point only to AD domain controllers running dns
for the domain [they all do by default in W2K]. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
http://support.microsoft.com/default.aspx?scid=kb;en-us;301423 -- how to install
netdiag and dcdiag. Same goes for netdiag on non servers.

 

[harry]

if the autodiconnect doesn't solve it I'll check out detdiag & dcdiag.

Thanks for your help.

When you reinstalled, did you rebuild the domain or was this an additional domain
controller?? The proper way to reinstall a dead dc is to restore via Directory
Services restore Mode from a backup that includes the System State. I would run
netdiag and dcdiag on your domain controller looking for configuration problems and
run netdiag on one of those clients next time it "disconnects" to see if it reports
errors such as failed tests. Dns misconfiguration is the usual culprit in that the
domain controller needs to point to itself or the pdc fsmo as it's only preferred dns
server and the domain clients need to point only to AD domain controllers running dns
for the domain [they all do by default in W2K]. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
http://support.microsoft.com/default.aspx?scid=kb;en-us;301423 -- how to install
netdiag and dcdiag. Same goes for netdiag on non servers.

Hi

I have couple of WinXP Pro pcs, connected to W2K Server.

Just reinstalled W2K server (with AD) recently due to HDD crash.

Now I find after approx 24 hours the WinXP pc's don't have permission to
access the shared directories on W2K server. When they login to the domain
they have permissions and no problems.

However after 24 hours or so (not sure exactly how long - seems to be
overnight some time this hapens) all the WinXP pc's can't access the shares.
They can see the domain + W2K server in 'Microsoft Widonws Network' in
windows explorer however don't have permission to view the shares. When I
clikc the shared directory, a popu box asks for username + password, but I'm
logged into the domain as Administrator and have max possible rights.

Any clue to this weird problem please?

Thanks
Harry

 

[Roger Abell]

You are best off checking your DNS support, rather than
tweaking what may be one symptom. If it is invalid DNS
support you will sooner than later need to get this fixed.

--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA

if the autodiconnect doesn't solve it I'll check out detdiag & dcdiag.

Thanks for your help.

When you reinstalled, did you rebuild the domain or was this an

additional

domain
controller?? The proper way to reinstall a dead dc is to restore via Directory
Services restore Mode from a backup that includes the System State. I would run
netdiag and dcdiag on your domain controller looking for configuration problems and
run netdiag on one of those clients next time it "disconnects" to see if it reports
errors such as failed tests. Dns misconfiguration is the usual culprit

in
that the

domain controller needs to point to itself or the pdc fsmo as it's only preferred dns
server and the domain clients need to point only to AD domain

controllers
running dns

for the domain [they all do by default in W2K]. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
http://support.microsoft.com/default.aspx?scid=kb;en-us;301423 -- how

to

install
netdiag and dcdiag. Same goes for netdiag on non servers.

When

I

but

I'm

 

[harry]

Thanks

It appears autodisconnect may not be the problem after all since it is set
at 65,535 which is in fact longer than the actual workstation timeouts (and
for some reason the server resets autodisconect itself to 65,535
automatically form time to time even though I set it to 0xffffffff from the
command line).

I'll look at DSN now.

You are best off checking your DNS support, rather than
tweaking what may be one symptom. If it is invalid DNS
support you will sooner than later need to get this fixed.

--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA

if the autodiconnect doesn't solve it I'll check out detdiag & dcdiag.

Thanks for your help.

When you reinstalled, did you rebuild the domain or was this an

additional

domain
controller?? The proper way to reinstall a dead dc is to restore via Directory
Services restore Mode from a backup that includes the System State. I would run
netdiag and dcdiag on your domain controller looking for configuration problems and
run netdiag on one of those clients next time it "disconnects" to see

if
it reports

errors such as failed tests. Dns misconfiguration is the usual culprit

in
that the

domain controller needs to point to itself or the pdc fsmo as it's

only
preferred dns

server and the domain clients need to point only to AD domain

controllers
running dns

for the domain [they all do by default in W2K]. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
http://support.microsoft.com/default.aspx?scid=kb;en-us;301423 -- how

to

install
netdiag and dcdiag. Same goes for netdiag on non servers.

Hi

I have couple of WinXP Pro pcs, connected to W2K Server.

Just reinstalled W2K server (with AD) recently due to HDD crash.

Now I find after approx 24 hours the WinXP pc's don't have

permission

to When but