Multiple XP users are experiencing their mapped network drive
(\\servername\username) which unmaps itself even after they were succesfully
able to map the drive.

Anna,

If you're using AD then use the logon/loff scripts

--
Newbie Coder
(It's just a name)



"Anna" <(E-Mail Removed)> wrote in message
news:E2DC1E13-273B-4C61-9582-(E-Mail Removed)...
> Multiple XP users are experiencing their mapped network drive
> (\\servername\username) which unmaps itself even after they were succesfully
> able to map the drive.

I am using AD and have the drive mappings in the logon scripts but for some
reason the drive mappings intermittently disappear.

"Newbie Coder" wrote:

> Anna,
>
> If you're using AD then use the logon/loff scripts
>
> --
> Newbie Coder
> (It's just a name)
>
>
>
> "Anna" <(E-Mail Removed)> wrote in message
> news:E2DC1E13-273B-4C61-9582-(E-Mail Removed)...
> > Multiple XP users are experiencing their mapped network drive
> > (\\servername\username) which unmaps itself even after they were succesfully
> > able to map the drive.
>
>
>

Anna,

What I suggest you also do is run a batch file on startup too locally

Net Use... See here but use the '/persistant:yes' at the end:

http://www.microsoft.com/resources/d....mspx?mfr=true

Example:

Net Use Z: \\ServerName\Directory /persistant:yes

--
Newbie Coder
(It's just a name)


"Anna" <(E-Mail Removed)> wrote in message
news:FAC8F9F0-3370-4CD0-97D6-(E-Mail Removed)...
> I am using AD and have the drive mappings in the logon scripts but for some
> reason the drive mappings intermittently disappear.
>
> "Newbie Coder" wrote:
>
> > Anna,
> >
> > If you're using AD then use the logon/loff scripts
> >
> > --
> > Newbie Coder
> > (It's just a name)
> >
> >
> >
> > "Anna" <(E-Mail Removed)> wrote in message
> > news:E2DC1E13-273B-4C61-9582-(E-Mail Removed)...
> > > Multiple XP users are experiencing their mapped network drive
> > > (\\servername\username) which unmaps itself even after they were
succesfully
> > > able to map the drive.
> >
> >
> >

I think you mean *persistent:yes* In any case it is usually recommended
*not* to use the persistent:yes switch if you run the batch file at
every startup. Deleting all persistent connections and running a batch
file to establish them at every log is often a fix to problems with
persistent connections.

John

Newbie Coder wrote:

> Anna,
>
> What I suggest you also do is run a batch file on startup too locally
>
> Net Use... See here but use the '/persistant:yes' at the end:
>
> http://www.microsoft.com/resources/d....mspx?mfr=true
>
> Example:
>
> Net Use Z: \\ServerName\Directory /persistant:yes
>

John John,

A typo by me but the user had a link to all switches

But the user can also use a switch to configure a username too if they wish.

Me personally would rather map the home directory etc within AD then run a batch
locally to map general shares. Its less likely to fail where XP is concerned. If
the users are nailed down sufficiently then there are no problems

Don't forget the registry also holds the Mapped Network Drive MRU
(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Map
Network Drive MRU) list too. Is that also classed as 'dangerous'?

With 2000 you could have at least use the lanmanager registry key for a timeout
for disconnection...

--
Newbie Coder
(It's just a name)


"John John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I think you mean *persistent:yes* In any case it is usually recommended
> *not* to use the persistent:yes switch if you run the batch file at
> every startup. Deleting all persistent connections and running a batch
> file to establish them at every log is often a fix to problems with
> persistent connections.
>
> John
>
> Newbie Coder wrote:
>
> > Anna,
> >
> > What I suggest you also do is run a batch file on startup too locally
> >
> > Net Use... See here but use the '/persistant:yes' at the end:
> >
> >
http://www.microsoft.com/resources/d....mspx?mfr=true
> >
> > Example:
> >
> > Net Use Z: \\ServerName\Directory /persistant:yes
> >