Re: I can't see the client printer.
- From: "Jim Vierra" <jvierra@xxxxxxx>
- Date: Thu, 21 Apr 2005 19:03:10 -0400
That is the wrong version. It's for XP
Embedded.
The 5.2 client is no longer available on the MS
site for some reason. It is on the Windows 2003 CD.
Here is a message from an MSFT tech concerning this
issue. It pretty much covers all of the issues.
I understand properly, when you remote
desktop to the Windows 2003
terminal server the local TCP/IP printer is not redirected. There is no
Event 1111 in the event log.
Before we go any further, I would like to confirm which remote desktop
client you used to connect to the terminal server. Did you use the remote
desktop client included in Windows XP? Based on my research, TCP/IP
printers are not redirected by default on Windows XP; while they are
redirected on Windows Server 2003. For Windows XP client, you can refer to
the following Microsoft Knowledge Base article to add the FilterQueueType
registry value to FFFFFFFF on Windows XP client to force all printer ports
to be redirected:
HKCU\Software\Microsoft\Terminal Server
Client\Default\AddIns\RDPDR\FilterQueueType
(DWORD) 0xFFFFFFFF
For more information, please refer to the following Microsoft Knowledge
Base article:
Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not
Redirected in a Remote Desktop or Terminal Services Session
http://support.microsoft.com/?id=302361
Meanwhile, you can download and install the Remote Desktop Connection
client for Windows Server 2003 on the Windows XP computer to test this
issue. It can be installed from the
"%systemroot%\system32\clients\tsclient\win32" folder on a Windows Server
2003 computer.
Dose it work now? If this problem continues, please refer to the following
steps to check if the port is redirected correctly.
1. Open the Control Panel->Printers folder in the Terminal Session.
2. Click File->Server Properties.
3. Click the Ports tab and check if the TSxxx port is created for the
printer.
In addition, please check the event log on the terminal server to see
whether you receive any error messages and ensure the following items:
1. You must enable the printer redirection on the RDP client. (You have
done it.)
2. You must enable the printer redirection on the terminal server.
Start => Terminal Services Configuration => Connetions => Double click on
"RDP-TCP", click "client settings", and make sure the following check boxes
had NOT been checked in the "disable the following" tab:
Windows Printer Mapping
LPT port Mapping
COM port Mapping
terminal server the local TCP/IP printer is not redirected. There is no
Event 1111 in the event log.
Before we go any further, I would like to confirm which remote desktop
client you used to connect to the terminal server. Did you use the remote
desktop client included in Windows XP? Based on my research, TCP/IP
printers are not redirected by default on Windows XP; while they are
redirected on Windows Server 2003. For Windows XP client, you can refer to
the following Microsoft Knowledge Base article to add the FilterQueueType
registry value to FFFFFFFF on Windows XP client to force all printer ports
to be redirected:
HKCU\Software\Microsoft\Terminal Server
Client\Default\AddIns\RDPDR\FilterQueueType
(DWORD) 0xFFFFFFFF
For more information, please refer to the following Microsoft Knowledge
Base article:
Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not
Redirected in a Remote Desktop or Terminal Services Session
http://support.microsoft.com/?id=302361
Meanwhile, you can download and install the Remote Desktop Connection
client for Windows Server 2003 on the Windows XP computer to test this
issue. It can be installed from the
"%systemroot%\system32\clients\tsclient\win32" folder on a Windows Server
2003 computer.
Dose it work now? If this problem continues, please refer to the following
steps to check if the port is redirected correctly.
1. Open the Control Panel->Printers folder in the Terminal Session.
2. Click File->Server Properties.
3. Click the Ports tab and check if the TSxxx port is created for the
printer.
In addition, please check the event log on the terminal server to see
whether you receive any error messages and ensure the following items:
1. You must enable the printer redirection on the RDP client. (You have
done it.)
2. You must enable the printer redirection on the terminal server.
Start => Terminal Services Configuration => Connetions => Double click on
"RDP-TCP", click "client settings", and make sure the following check boxes
had NOT been checked in the "disable the following" tab:
Windows Printer Mapping
LPT port Mapping
COM port Mapping
--
Jim Vierra
"Kane" <kane@xxxxxxxxxxxxxxxxx> wrote in
message news:Ofhb7ejRFHA.3496@xxxxxxxxxxxxxxxxxxxx...
> When I verified
the version of my RDP client (mstsc.exe) under system32 > folder, I found that it is showing 5.1.2.x version, not the one you
> mentioned 5.2. Therefore I downloaded this version
> (Q828665_XPE_SP2_X86_ENU.exe) from Microsoft site. However; when I
> installed it, I got the following error message.
>
> "WEUpdate cannot retrieve information needed for setup from database."
>
> I am wondering, if the latest version of RDP client being updated by XP SP2?
> Because I recently upgrade to SP2.
>
> "Jim Vierra" <jvierra@xxxxxxx> wrote in message
> news:uOxnCHfRFHA.1236@xxxxxxxxxxxxxxxxxxxx...
>> The printer is there but the settings for redirection are probably not set
>> right at the client or at the server. Be sure the client has set to
>> redirect printers and that the server is not blocking.
>>
>> What version of RDP is on the client? Try downloading and installing 5.2.
>>
>> --
>> Jim Vierra
>>
>> "Kane" <kane@xxxxxxxxxxxxxxxxx> wrote in message
>> news:eshDF4cRFHA.3288@xxxxxxxxxxxxxxxxxxxx...
>>> Hi Jim;
>>>
>>> Yes, it works after I shared the printer from a client workstation, then
>>> I can see it again on Terminal Servers. Why it works after shared the
>>> printer. Suppose, it will see the local printer too as long as TS and
>>> the client workstation has the same printer driver, right?
>>>
>>> Thanks!
>>>
>>> "Jim Vierra" <jvierra@xxxxxxx> wrote in message
>>> news:%23b7$t7GRFHA.3868@xxxxxxxxxxxxxxxxxxxx...
>>>> Share printer on client workstation.
>>>>
>>>> --
>>>> Jim Vierra
>>>> http://msdn.microsoft.com/theshow/Episode048/default.asp
>>>> "Kane" <kane@xxxxxxxxxxxxxxxxx> wrote in message
>>>> news:%2346vHgGRFHA.3868@xxxxxxxxxxxxxxxxxxxx...
>>>>> Hi;
>>>>>
>>>>> Eventhough I installed the same printer driver on both of the Terminal
>>>>> Server and the client workstation. I still cannot see the client
>>>>> printer once she is logon to TS. I am pretty sure that in Remote
>>>>> Desktop Connection client program, the Printers has been selected in
>>>>> Local Resources and the setting in Active Directory and the Terminal
>>>>> Services Configuration are done.
>>>>>
>>>>> What else should I check?
>>>>>
>>>>> Thanks!
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
- References:
- I can't see the client printer.
- From: Kane
- Re: I can't see the client printer.
- From: Jim Vierra
- Re: I can't see the client printer.
- From: Kane
- Re: I can't see the client printer.
- From: Jim Vierra
- Re: I can't see the client printer.
- From: Kane
- I can't see the client printer.
- Prev by Date: Terminal Server session creation failed
- Next by Date: Searching Users Recycle Bins
- Previous by thread: Re: I can't see the client printer.
- Next by thread: trouble establishing connection with local printers in TS
- Index(es):
Relevant Pages
|
Loading