Guest Anna Posted August 24, 2007 Posted August 24, 2007 Multiple XP users are experiencing their mapped network drive (\\servername\username) which unmaps itself even after they were succesfully able to map the drive.
Guest Newbie Coder Posted August 24, 2007 Posted August 24, 2007 Re: Drive Mappings Problem Anna, If you're using AD then use the logon/loff scripts -- Newbie Coder (It's just a name) "Anna" <Anna@discussions.microsoft.com> wrote in message news:E2DC1E13-273B-4C61-9582-299A95C3A8E1@microsoft.com... > Multiple XP users are experiencing their mapped network drive > (\\servername\username) which unmaps itself even after they were succesfully > able to map the drive.
Guest Anna Posted August 24, 2007 Posted August 24, 2007 Re: Drive Mappings Problem 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" <Anna@discussions.microsoft.com> wrote in message > news:E2DC1E13-273B-4C61-9582-299A95C3A8E1@microsoft.com... > > Multiple XP users are experiencing their mapped network drive > > (\\servername\username) which unmaps itself even after they were succesfully > > able to map the drive. > > >
Guest Newbie Coder Posted August 24, 2007 Posted August 24, 2007 Re: Drive Mappings Problem 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/documentation/windows/xp/all/proddocs/en-us/net_use.mspx?mfr=true Example: Net Use Z: \\ServerName\Directory /persistant:yes -- Newbie Coder (It's just a name) "Anna" <Anna@discussions.microsoft.com> wrote in message news:FAC8F9F0-3370-4CD0-97D6-76B66BEC400A@microsoft.com... > 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" <Anna@discussions.microsoft.com> wrote in message > > news:E2DC1E13-273B-4C61-9582-299A95C3A8E1@microsoft.com... > > > Multiple XP users are experiencing their mapped network drive > > > (\\servername\username) which unmaps itself even after they were succesfully > > > able to map the drive. > > > > > >
Guest John John Posted August 24, 2007 Posted August 24, 2007 Re: Drive Mappings Problem 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/documentation/windows/xp/all/proddocs/en-us/net_use.mspx?mfr=true > > Example: > > Net Use Z: \\ServerName\Directory /persistant:yes >
Guest Newbie Coder Posted August 24, 2007 Posted August 24, 2007 Re: Drive Mappings Problem 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" <audetweld@nbnet.nb.ca> wrote in message news:uKJhLXp5HHA.3916@TK2MSFTNGP02.phx.gbl... > 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/documentation/windows/xp/all/proddocs/en-us/net_use.mspx?mfr=true > > > > Example: > > > > Net Use Z: \\ServerName\Directory /persistant:yes > >
Recommended Posts