Wireless Printing with RDP connect to a Windows 2003 Terminal Server

This is the situation that I have. I have a HP 6980 Deskjet printer with a built in wireless print server. The drivers have been installed on the Terminal Server which has Windows 2003 Server on it. Also the print drivers have been loaded on individual laptops. All of the laptops have WinXP sp2. All of the laptops can print fine wireless to the printer when the laptops are not connected to the Terminal Server through RDP. The problem arises when connecting to the terminal server, only one laptop sees the printer wireless, but if the printer is connected directly to the laptops the laptops do recognize the printer. Is there some port or other add on the needs to be put on the other laptops so they can see the printer wireless when connected to the Terminal server? I disabled windows firewall just in case the was causing the problem, but it did not help. I have compared the working laptop with the ones that do not recognize the wireless printer through rdp, and everything looks the same. Help!
AtlasOilAsked:
Who is Participating?
 
GranModCommented:
PAQed with points refunded (500)

GranMod
Community Support Moderator
0
 
adamdrayerCommented:
Did you check NetBIOS over TCP/IP?  If the one that works has it enabled, then you should enable it on the other as well.  You can find this in the properties for the network connection.  Click the advanced button and look at the WINS tab.
0
 
Jay_Jay70Commented:
Hi AtlasOil,

Can the terminal server itself see the wireless printer and print to it

Cheers!
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
AtlasOilAuthor Commented:
Thanks for the responses, Adam the NetBIOS over TCP/IP is not enabled on the laptop that works. The default NetBIOS settting is selected.
0
 
AtlasOilAuthor Commented:
I will check and see if the terminal server can see the printer and print to it.
0
 
carl_legereCommented:
users profiles running on terminal server (the environment they receive when they login to TS) do not necessarily get printers until installed in each profile.

there are two techniques that work at the same time to populate the printer list in a TS session.  One is printers setup locally on the TS, you might have to make a user an admin, login as them, add the printer, log off and make them non-admin again.  The other way is that the TS session will take the physically connected default printer from the PC connecting with it for the TS session.  These show up in the printer list with session number and PC name in it.
0
 
AtlasOilAuthor Commented:
Thanks everybody for your help, I actually solved this myself. The HP printer is not using a Com, Lpt, or USB port. It is using an HP TCPIP port. On my laptop the following registry setting was setup, DWORD value named FilterQueueType was added to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF. But this was not added to the other laptops I was having problems with.

The follow MS Knowledgebase article explains what is necessary to do to enable Printers That Use Ports That Do Not Begin With COM, LPT, or USB .

http://support.microsoft.com/kb/302361/en-us

Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session
View products that this article applies to.
Article ID : 302361
Last Review : December 20, 2004
Revision : 4.4
This article was previously published under Q302361
SYMPTOMS
When you use Remote Desktop Connection or the Terminal Services Client version 4.0 or 5.0 to connect to another Windows-based computer from a computer that is not running Windows Server 2003, your local printers may not be redirected. As a result, your local printers are not available in the remote desktop or terminal services session.

For example, if your Windows XP-based computer has a multifunction print device using a DOT4 port, it may not be redirected in a remote desktop session to a Windows 2000- or Windows Server 2003-based computer.
CAUSE
This problem occurs because the printer port does not begin with COM, LPT, or USB. By default, printer port names that do not begin with COM, LPT, or USB are only redirected in Windows Server 2003. By default, multifunction print devices may not be redirected unless you are running Windows Server 2003 on your local computer because they use DOT4 ports.
RESOLUTION
To resolve this problem on a computer that is not running Windows Server 2003, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.