offline files drive not mapped when offline

I'm using XP Pro. I have two drives (T: & U mapped to shares on a 2003 SBS
server. I have marked files on both drives to be available offline. When I
synchronize, it shows both drives being synchronized.

However, if I power down, unplug the network cable, power up, and login,
only the U: drive is mapped. If I go to Network Neighborhood and drill down
many levels, I can get to the files that are normally on the T: drive, but
that is unfriendly.

How can I get the T: drive to be mapped when I'm working offline?

Thank you.
Jerry K

I believe the reason is that you may have a Logon script which maps the T:
drive, but not persistently; drive U: may have been mapped persistently, or
by using the Map Drive GUI with the "reconnect at logon" checkbox selected.
Each time you logoff, this is disconnected.

You can map a drive persistently at a command prompt as follows (using X as
a drive, for example):

net use X: \\servername\sharename /persistent:yes

If any spaces in the path name, enclose the path in quotes. e.g.,
"\\servername\share name"

HOWEVER, before you do this, you may want to see if you have logon script(s)
that are mapping these drives by looking either in RSOP.msc User
Configuration\Windows Settings\Scripts\Logon or in
"%systemroot%\system32\Group Policy\User\Scripts\Logon".



--
JCB\1059


"jerryk" wrote:

> I'm using XP Pro. I have two drives (T: & U mapped to shares on a 2003 SBS
> server. I have marked files on both drives to be available offline. When I
> synchronize, it shows both drives being synchronized.
>
> However, if I power down, unplug the network cable, power up, and login,
> only the U: drive is mapped. If I go to Network Neighborhood and drill down
> many levels, I can get to the files that are normally on the T: drive, but
> that is unfriendly.
>
> How can I get the T: drive to be mapped when I'm working offline?
>
> Thank you.
> Jerry K
>
>

That was it. Thank you.

"JCB" wrote:

> I believe the reason is that you may have a Logon script which maps the T:
> drive, but not persistently; drive U: may have been mapped persistently, or
> by using the Map Drive GUI with the "reconnect at logon" checkbox selected.
> Each time you logoff, this is disconnected.
>
> You can map a drive persistently at a command prompt as follows (using X as
> a drive, for example):
>
> net use X: \\servername\sharename /persistent:yes
>
> If any spaces in the path name, enclose the path in quotes. e.g.,
> "\\servername\share name"
>
> HOWEVER, before you do this, you may want to see if you have logon script(s)
> that are mapping these drives by looking either in RSOP.msc User
> Configuration\Windows Settings\Scripts\Logon or in
> "%systemroot%\system32\Group Policy\User\Scripts\Logon".
>
>
>
> --
> JCB\1059
>
>
> "jerryk" wrote:
>
> > I'm using XP Pro. I have two drives (T: & U mapped to shares on a 2003 SBS
> > server. I have marked files on both drives to be available offline. When I
> > synchronize, it shows both drives being synchronized.
> >
> > However, if I power down, unplug the network cable, power up, and login,
> > only the U: drive is mapped. If I go to Network Neighborhood and drill down
> > many levels, I can get to the files that are normally on the T: drive, but
> > that is unfriendly.
> >
> > How can I get the T: drive to be mapped when I'm working offline?
> >
> > Thank you.
> > Jerry K
> >
> >

I have a question that is related

say you have a log on script such at

net use x: /delete
net use x: \\servername\sharename /persistent:yes

Would this work as a log on script even though the drive is mapped or would
there stil be issues?



"jerryk" wrote:

> That was it. Thank you.
>
> "JCB" wrote:
>
> > I believe the reason is that you may have a Logon script which maps the T:
> > drive, but not persistently; drive U: may have been mapped persistently, or
> > by using the Map Drive GUI with the "reconnect at logon" checkbox selected.
> > Each time you logoff, this is disconnected.
> >
> > You can map a drive persistently at a command prompt as follows (using X as
> > a drive, for example):
> >
> > net use X: \\servername\sharename /persistent:yes
> >
> > If any spaces in the path name, enclose the path in quotes. e.g.,
> > "\\servername\share name"
> >
> > HOWEVER, before you do this, you may want to see if you have logon script(s)
> > that are mapping these drives by looking either in RSOP.msc User
> > Configuration\Windows Settings\Scripts\Logon or in
> > "%systemroot%\system32\Group Policy\User\Scripts\Logon".
> >
> >
> >
> > --
> > JCB\1059
> >
> >
> > "jerryk" wrote:
> >
> > > I'm using XP Pro. I have two drives (T: & U mapped to shares on a 2003 SBS
> > > server. I have marked files on both drives to be available offline. When I
> > > synchronize, it shows both drives being synchronized.
> > >
> > > However, if I power down, unplug the network cable, power up, and login,
> > > only the U: drive is mapped. If I go to Network Neighborhood and drill down
> > > many levels, I can get to the files that are normally on the T: drive, but
> > > that is unfriendly.
> > >
> > > How can I get the T: drive to be mapped when I'm working offline?
> > >
> > > Thank you.
> > > Jerry K
> > >
> > >

Kevin C <KevinC@discussions.microsoft.com> wrote:
> I have a question that is related
>
> say you have a log on script such at
>
> net use x: /delete
> net use x: \\servername\sharename /persistent:yes
>
> Would this work as a log on script even though the drive is mapped or
> would there stil be issues?

Hi - you have an existing new message of your own pertaining to this, and
have replies in there - please don't start new threads (esp as "me too"
replies in other threads).

>
>
>
> "jerryk" wrote:
>
>> That was it. Thank you.
>>
>> "JCB" wrote:
>>
>>> I believe the reason is that you may have a Logon script which maps
>>> the T: drive, but not persistently; drive U: may have been mapped
>>> persistently, or by using the Map Drive GUI with the "reconnect at
>>> logon" checkbox selected. Each time you logoff, this is
>>> disconnected.
>>>
>>> You can map a drive persistently at a command prompt as follows
>>> (using X as a drive, for example):
>>>
>>> net use X: \\servername\sharename /persistent:yes
>>>
>>> If any spaces in the path name, enclose the path in quotes. e.g.,
>>> "\\servername\share name"
>>>
>>> HOWEVER, before you do this, you may want to see if you have logon
>>> script(s) that are mapping these drives by looking either in
>>> RSOP.msc User Configuration\Windows Settings\Scripts\Logon or in
>>> "%systemroot%\system32\Group Policy\User\Scripts\Logon".
>>>
>>>
>>>
>>> --
>>> JCB\1059
>>>
>>>
>>> "jerryk" wrote:
>>>
>>>> I'm using XP Pro. I have two drives (T: & U mapped to shares on
>>>> a 2003 SBS server. I have marked files on both drives to be
>>>> available offline. When I synchronize, it shows both drives being
>>>> synchronized.
>>>>
>>>> However, if I power down, unplug the network cable, power up, and
>>>> login, only the U: drive is mapped. If I go to Network
>>>> Neighborhood and drill down many levels, I can get to the files
>>>> that are normally on the T: drive, but that is unfriendly.
>>>>
>>>> How can I get the T: drive to be mapped when I'm working offline?
>>>>
>>>> Thank you.
>>>> Jerry K