No Mapped Drives with TS on Windows 2003 R2

I'm not sure what I'm missing on my new Windows Server 2003 R2 Terminal
Server, but for some reason none of my clients' mapped drives show up when
the connect. Mapped drives show up fine when logging into a local client.
There aren't any Group Policies preventing it, so I'm hoping someone can give
me some tips on what I can look for in troubleshooting this.

Thanks.

 

Have you checked the local configuration on the server, in tscc.msc?
Any errors or warnings in the EventLog?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TWFya3M3MA==?= <Marks70@discussions.microsoft.com> wrote
on 10 aug 2009:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I'm not sure what I'm missing on my new Windows Server 2003 R2
> Terminal Server, but for some reason none of my clients' mapped
> drives show up when the connect. Mapped drives show up fine when
> logging into a local client. There aren't any Group Policies
> preventing it, so I'm hoping someone can give me some tips on
> what I can look for in troubleshooting this.
>
> Thanks.<!--colorc--><!--/colorc-->

 

Hi,

Other than confirming that "Drive mapping" was unchecked under "Disable the
following" under the Client Settings tab, I wasn't sure what else to check.
Is there anything else within the connection properties that must be
configured to allow mapped drives?

Also, in the Security Event log, there are a couple errors similar to the
following, but I don't know if it has anything to do with the mapped drive
issue:

----------
Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 8/10/2009
Time: 11:06:58 AM
User: DOMAIN\tester
Computer: SERVER
Description:
Object Open:
Object Server: SC Manager
Object Type: SC_MANAGER OBJECT
Object Name: ServicesActive
Handle ID: -
Operation ID: {0,468888722}
Process ID: 412
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: SERVER$
Primary Domain: DOMAIN
Primary Logon ID: (0x0,0x3E7)
Client User Name: tester
Client Domain: DOMAIN
Client Logon ID: (0x0,0x1BEF29AE)
Accesses: DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
Connect to service controller
Create a new service
Enumerate services
Lock service database for exclusive access
Query service database lock state
Set last-known-good state of service database

Privileges: -
Restricted Sid Count: 0
Access Mask: 0xF003F
----------

Thanks for your help.


"Vera Noest [MVP]" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Have you checked the local configuration on the server, in tscc.msc?
> Any errors or warnings in the EventLog?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting:
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?TWFya3M3MA==?= <Marks70@discussions.microsoft.com> wrote
> on 10 aug 2009:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > I'm not sure what I'm missing on my new Windows Server 2003 R2
> > Terminal Server, but for some reason none of my clients' mapped
> > drives show up when the connect. Mapped drives show up fine when
> > logging into a local client. There aren't any Group Policies
> > preventing it, so I'm hoping someone can give me some tips on
> > what I can look for in troubleshooting this.
> >
> > Thanks.<!--colorc--><!--/colorc-->
> <!--colorc--><!--/colorc-->