Local Resouce - Disk Drives Missing

  • Thread starter Thread starter To Old To . . .
  • Start date Start date
T

To Old To . . .

Guest
New Server 2003R2, when connecting to Server though RDP, the local drives can
not seen. On my other servers they are. Any suggestions?
Thanks in advance.
 
Re: Local Resouce - Disk Drives Missing

On 11 okt, 09:20, To Old To . . . <ToOl...@discussions.microsoft.com>
wrote:
> New Server 2003R2, when connecting to Server though RDP, the local drives can
> not seen. On my other servers they are. Any suggestions?
> Thanks in advance.

Hi there,

You can't see your local computer harddrives mapped into your terminal
session? Go to the options of your terminal services client ( or - if
you have a RDP file on your desktop - rightclick on the file an select
edit ) , click on "local resources" and click on the button More. In
this menu you can select all drives you want to have mapped in your
terminal server session. It is possible that this option is disabled
server-side by a GPO. By default it is possible in administrative
connections to connect local resources to your terminal services
though. Are you running your terminal server in application mode or in
administrative mode by the way?

Kind Regards,

Oscar Disch
 
Re: Local Resouce - Disk Drives Missing

Thank you for your reply.
I am running in Administrative mode. In RDP it is selected to map local
drives.


"siqdiz@gmail.com" wrote:

> On 11 okt, 09:20, To Old To . . . <ToOl...@discussions.microsoft.com>
> wrote:
> > New Server 2003R2, when connecting to Server though RDP, the local drives can
> > not seen. On my other servers they are. Any suggestions?
> > Thanks in advance.
>
> Hi there,
>
> You can't see your local computer harddrives mapped into your terminal
> session? Go to the options of your terminal services client ( or - if
> you have a RDP file on your desktop - rightclick on the file an select
> edit ) , click on "local resources" and click on the button More. In
> this menu you can select all drives you want to have mapped in your
> terminal server session. It is possible that this option is disabled
> server-side by a GPO. By default it is possible in administrative
> connections to connect local resources to your terminal services
> though. Are you running your terminal server in application mode or in
> administrative mode by the way?
>
> Kind Regards,
>
> Oscar Disch
>
>
 
Re: Local Resouce - Disk Drives Missing

Have you checked whether driver redirection is disabled in GPO on the
server?


--
This posting is provided "AS IS" with no warranties, and confers no rights.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"To Old To . . ." <ToOldTo@discussions.microsoft.com> wrote in message
news:C5B03207-7137-4689-B8FC-D85FB8201A11@microsoft.com...
> Thank you for your reply.
> I am running in Administrative mode. In RDP it is selected to map local
> drives.
>
>
> "siqdiz@gmail.com" wrote:
>
>> On 11 okt, 09:20, To Old To . . . <ToOl...@discussions.microsoft.com>
>> wrote:
>> > New Server 2003R2, when connecting to Server though RDP, the local
>> > drives can
>> > not seen. On my other servers they are. Any suggestions?
>> > Thanks in advance.
>>
>> Hi there,
>>
>> You can't see your local computer harddrives mapped into your terminal
>> session? Go to the options of your terminal services client ( or - if
>> you have a RDP file on your desktop - rightclick on the file an select
>> edit ) , click on "local resources" and click on the button More. In
>> this menu you can select all drives you want to have mapped in your
>> terminal server session. It is possible that this option is disabled
>> server-side by a GPO. By default it is possible in administrative
>> connections to connect local resources to your terminal services
>> though. Are you running your terminal server in application mode or in
>> administrative mode by the way?
>>
>> Kind Regards,
>>
>> Oscar Disch
>>
>>
 
Re: Local Resouce - Disk Drives Missing

No. It is a new installation, no different than any other installation that I
have done. I will check to see, but by default it should be ok.

Thanks, I will look at it and let you know


"Rong Chen [MSFT]" wrote:

> Have you checked whether driver redirection is disabled in GPO on the
> server?
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "To Old To . . ." <ToOldTo@discussions.microsoft.com> wrote in message
> news:C5B03207-7137-4689-B8FC-D85FB8201A11@microsoft.com...
> > Thank you for your reply.
> > I am running in Administrative mode. In RDP it is selected to map local
> > drives.
> >
> >
> > "siqdiz@gmail.com" wrote:
> >
> >> On 11 okt, 09:20, To Old To . . . <ToOl...@discussions.microsoft.com>
> >> wrote:
> >> > New Server 2003R2, when connecting to Server though RDP, the local
> >> > drives can
> >> > not seen. On my other servers they are. Any suggestions?
> >> > Thanks in advance.
> >>
> >> Hi there,
> >>
> >> You can't see your local computer harddrives mapped into your terminal
> >> session? Go to the options of your terminal services client ( or - if
> >> you have a RDP file on your desktop - rightclick on the file an select
> >> edit ) , click on "local resources" and click on the button More. In
> >> this menu you can select all drives you want to have mapped in your
> >> terminal server session. It is possible that this option is disabled
> >> server-side by a GPO. By default it is possible in administrative
> >> connections to connect local resources to your terminal services
> >> though. Are you running your terminal server in application mode or in
> >> administrative mode by the way?
> >>
> >> Kind Regards,
> >>
> >> Oscar Disch
> >>
> >>
>
>
 
Re: Local Resouce - Disk Drives Missing

Hi,

- On your *local* machine, open regedit and check for a
REG_DWORD that corresponds to the problem server's
name/ip address under the following path and if it exists,
delete it:

HKCU\Software\Microsoft\Terminal Server Client\Local Devices

After deleting the above launch the RD client, double-check
that Drive mapping is enabled and connect to your problem
server

- On the Server in Terminal Services Configuration (tscc.msc)
verify Drive mapping is *unchecked* on the Client tab of the
RDP-Tcp Properties

- Verify that C:\WINDOWS\system32\drprov.dll on the server
has correct permissions

- Check that the RDP Network Provider is in the registry and
has the correct keys and values (compare to a working server,
*some* of the required keys appear below):

HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_RDPNP
HKLM\SYSTEM\CurrentControlSet\Services\RDPNP

- Check that the Microsoft Terminal Services network provider
is listed first in the binding order. This is under Network
Connections, Advanced, Advanced Settings, Provider Order tab

- Compare TS-related registry keys and values to a working
server, if you see a difference that you think may be important,
please post

- While logged on via TS with Drive Mapping enabled, if you
click Start-->Run and type \\tsclient\c what is the exact text of
the error?

-TP

To Old To . . . wrote:
> No. It is a new installation, no different than any other
> installation that I have done. I will check to see, but by default it
> should be ok.
>
> Thanks, I will look at it and let you know
 
Re: Local Resouce - Disk Drives Missing

I will check that out, thank you for the reply



"TP" wrote:

> Hi,
>
> - On your *local* machine, open regedit and check for a
> REG_DWORD that corresponds to the problem server's
> name/ip address under the following path and if it exists,
> delete it:
>
> HKCU\Software\Microsoft\Terminal Server Client\Local Devices
>
> After deleting the above launch the RD client, double-check
> that Drive mapping is enabled and connect to your problem
> server
>
> - On the Server in Terminal Services Configuration (tscc.msc)
> verify Drive mapping is *unchecked* on the Client tab of the
> RDP-Tcp Properties
>
> - Verify that C:\WINDOWS\system32\drprov.dll on the server
> has correct permissions
>
> - Check that the RDP Network Provider is in the registry and
> has the correct keys and values (compare to a working server,
> *some* of the required keys appear below):
>
> HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_RDPNP
> HKLM\SYSTEM\CurrentControlSet\Services\RDPNP
>
> - Check that the Microsoft Terminal Services network provider
> is listed first in the binding order. This is under Network
> Connections, Advanced, Advanced Settings, Provider Order tab
>
> - Compare TS-related registry keys and values to a working
> server, if you see a difference that you think may be important,
> please post
>
> - While logged on via TS with Drive Mapping enabled, if you
> click Start-->Run and type \\tsclient\c what is the exact text of
> the error?
>
> -TP
>
> To Old To . . . wrote:
> > No. It is a new installation, no different than any other
> > installation that I have done. I will check to see, but by default it
> > should be ok.
> >
> > Thanks, I will look at it and let you know
>
 
Re: Local Resouce - Disk Drives Missing

Well thank you very much, that did the trick.



"TP" wrote:

> Hi,
>
> - On your *local* machine, open regedit and check for a
> REG_DWORD that corresponds to the problem server's
> name/ip address under the following path and if it exists,
> delete it:
>
> HKCU\Software\Microsoft\Terminal Server Client\Local Devices
>
> After deleting the above launch the RD client, double-check
> that Drive mapping is enabled and connect to your problem
> server
>
> - On the Server in Terminal Services Configuration (tscc.msc)
> verify Drive mapping is *unchecked* on the Client tab of the
> RDP-Tcp Properties
>
> - Verify that C:\WINDOWS\system32\drprov.dll on the server
> has correct permissions
>
> - Check that the RDP Network Provider is in the registry and
> has the correct keys and values (compare to a working server,
> *some* of the required keys appear below):
>
> HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_RDPNP
> HKLM\SYSTEM\CurrentControlSet\Services\RDPNP
>
> - Check that the Microsoft Terminal Services network provider
> is listed first in the binding order. This is under Network
> Connections, Advanced, Advanced Settings, Provider Order tab
>
> - Compare TS-related registry keys and values to a working
> server, if you see a difference that you think may be important,
> please post
>
> - While logged on via TS with Drive Mapping enabled, if you
> click Start-->Run and type \\tsclient\c what is the exact text of
> the error?
>
> -TP
>
> To Old To . . . wrote:
> > No. It is a new installation, no different than any other
> > installation that I have done. I will check to see, but by default it
> > should be ok.
> >
> > Thanks, I will look at it and let you know
>
 
Back
Top