Re: Problem with network drives disappearing after logoff / logon

Hi,

Pls check the system time on file server and DCs. You may need to re sync
the time on file server.

Best regards,

"Allyn" wrote:

I'm going to say it's tentatively fixed. I looked at another domain I'm
administering, and I noticed that inside the Group Policy Management for the
Default Domain Policy, the domain was listed in the Links section on the
Scope tab. I don't know how this dropped off, but I re-added it to the
problem domain, and it appears to be working OK. I'm going to let this drop
off as I have enough other things to do, but I'm really curious why the
drives were being disconnected, even with no logon/logoff script applied.

Thanks for the response, and I'll keep in mind the echo statement going
forward.



"Pegasus [MVP]" wrote:


"Allyn" <Allyn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:530195E7-15B8-4C85-B7DF-6E5123DB4761@xxxxxxxxxxxxxxxx
I'm troubleshooting a small domain with one Win2K3 and one Win2K domain
controllers. Recently, we've started encountering problems with users
losing
every network drive upon logging back into the domain. The login script
run
fine for every user when I manually point it to
\\servername\sysvol\...\login.vbs, and all drives re-appear. Log off and
back
on, and all drives are missing. I've removed the login script from the
group
policy, and there is not a logoff script, and even after the drives are
remapped and a user log offs and back on, the drives are once again
missing.

The only recent change is that we've gone from Symantec Corp to Trend
Micro,
so there is a Trend Micro batch files under the user account that has the
contents:

\\SERVERNAME\OFCSCAN\AUTOPCC

This only checks that Trend is installed, and installs it if it isn't
present.

This problem didn't start at the exact same time as trend, but it was
noticed within a couple of days. I'm sure there is another issue, but I
don't
know where to look next.

Thanks for any advice.


Put some wscript.echo statements into your logon script and add a msgbox
statement at the end so that you can see what's going on. If you have an "on
error resume next" statement in the script then you must remove it while
debugging.



.

Relevant Pages

  • Re: Problem with network drives disappearing after logoff / logon
    ... Default Domain Policy, the domain was listed in the Links section on the ... drives were being disconnected, even with no logon/logoff script applied. ... The only recent change is that we've gone from Symantec Corp to Trend ...
    (microsoft.public.windows.server.general)
  • Re: Problem with network drives disappearing after logoff / logon
    ... and all drives are missing. ... I've removed the login script from the ... The only recent change is that we've gone from Symantec Corp to Trend ...
    (microsoft.public.windows.server.general)
  • Re: Backups: rsync, software RAID, other strategies?
    ... I use the following configuration on my file server. ... typical rsync that will mirror the source to the ... You can also purge the backup by removing ... >of the drives as a backup for the other. ...
    (freebsd-questions)
  • Re: Script initiate a drive connection?
    ... Network & Software Integration ... Dim objWMI, objPing, colPings, ServerOnline, Result ... in a script the double click on a disconnected drive. ... automatically connect map drives on boot up.) ...
    (microsoft.public.windows.server.scripting)
  • Re: Script initiate a drive connection?
    ... I tried this script and received an error "The NTVDM CPU has ... Dim objWMI, objPing, colPings, ServerOnline, Result ... Network & Software Integration ... automatically connect map drives on boot up.) ...
    (microsoft.public.windows.server.scripting)