Can't print to local printer with RDC session

  • Thread starter Thread starter M Wright
  • Start date Start date
M

M Wright

Have a Windows XP Pro client connected via Remote Desktop
Connection to a Windows 2000 SP 4 Server. Client has a
HP 4500 printer on LAN of client, while server has HP
5000 on LAN of server. The client connects right to an
application on the server (the Programs tab of RDC
settings has a program selected to start), but, when
attempts to print, cannot print to client-local printer
(HP4500), though can print to the server-local printer
(HP5000). The server has the HP4500 driver installed
that is used by client. The client can't even see the
HP4500 as a print option within the applications print
dialog box (only the HP5000). All of the Macintosh
clients that use the server can print to thier respective
local printers (and the W2K server shows all of
the "session printers" for each of the Mac clients,
though not for the Win client), but the only Windows
client cannot. All clients (Mac/Win) have printer
selected as a local resource to use during the RDC
session in the RDC configuration. The server TS settings
have client session settings used, and does not
have "disable Windows printing" selected.
Any ideas?
TIA. M. Wright
 
Is there a message in the EventLog about the server not being able
to create the printer because the driver is unknown? If that is
the case, then you probably have a (small) difference in driver
names (they must match *exactly* for redirection to occur).

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
 
No message in event log about redirection failure.

Though I did read that article: 239088 - Windows 2000
Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

and was going to follow the steps, the fact that I don't
get the event log message entry makes it appear that I
may have a different problem.

All the Macintosh computers are able to connect to thier
local printers, just the only Windows client cannot,
which seems odd.

I even added the printer to the server that is on the
remote network with the hope that the remote user could
select it within the application on the Terminal services
server, and print through the VPN, but the print job just
hangs and fails.

TIA for any more help on this.
 
-----Original Message-----
Have a Windows XP Pro client connected via Remote Desktop
Connection to a Windows 2000 SP 4 Server. Client has a
HP 4500 printer on LAN of client, while server has HP
5000 on LAN of server. The client connects right to an
application on the server (the Programs tab of RDC
settings has a program selected to start), but, when
attempts to print, cannot print to client-local printer
(HP4500), though can print to the server-local printer
(HP5000). The server has the HP4500 driver installed
that is used by client. The client can't even see the
HP4500 as a print option within the applications print
dialog box (only the HP5000). All of the Macintosh
clients that use the server can print to thier respective
local printers (and the W2K server shows all of
the "session printers" for each of the Mac clients,
though not for the Win client), but the only Windows
client cannot. All clients (Mac/Win) have printer
selected as a local resource to use during the RDC
session in the RDC configuration. The server TS settings
have client session settings used, and does not
have "disable Windows printing" selected.
Any ideas?
TIA. M. Wright
.
Click to expand...

You should try adding a new network printer even though
the printer is local. First make sure that on your
client's local machine that (print sharing is enabled) in
network neighborhood properties. Next logon to the server
and in add new printer you have to select add a network
printer, and then on the next screen select (type printer
name or click next to browse). Of course this will take
you to all the shared printers on your network based on
computer name. Using your client's computer name, expand
the plus sign and select the printer listed under the
client's computer name.
 
Please included the history of the thread in your follow-up, all
of the context is gone now.

Is it correct that only one client has this problem?
Are there other clients with the exact same printer that get their
printer redirected automatically?
This may seem a stupid question, but have you checked the settings
for printer redirection on the client?
I seem to recall that the client starts the TS session with a pre-
configured initial application. Have you checked if the printer is
redirected when the client connects to the full desktop?
Which version of the rdp-client do you use? Have you tried to
upgrade to the latest (5.2)?

http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-
4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en
 
Vera: Answers to your questions:

Yes, only one client having this problem, as their is
only one Windows Client (Windows XP Pro) at the remote
sites.

Yes, other clients at the same site using the same local
(to site) printer and do get the printer re-direction,
and all of those clients are Macs. And Macs at another
site are able to connect to thier local printer also.

Re: Printer settings, the Remote Desktop Connection
client on the WinXP Pro, in "Local Resources" tab, "Local
Devices" section, "Printers" is checked. Also, on the
servers, the setting to "Disable Connecting to Windows
printers" is NOT checked, and the setting to use the
client connection settings IS set.

As you said, the client does connect to a pre-configured
initial application. But, I did try to connect as
a "desktop" session also, and still no redirection of
printer. No matter when I use the pre-configured initial
app to print, or connect to the desktop, and try to print
out of, say, WordPad, the only printers that appear to me
are the ones in the same LAN as the TS server. Yet, when
I go to tehe TS server, I can see all of the redirected
printers for all of the Macintosh clients. And when I
log in through a Mac RDC session, I can see all of the
redirected printers and local (to TS server) printers in
the Mac print dialog box.

The version of RDC client is the one that comes installed
with WinXP Pro, so I will upgrade that one in morning
(when the WinXP Pro system is restarted, as I am doing
this troubleshooting remotely, and the unit is off now).

Given that the Mac's can connect, but the WinXP Pro
cannot probably means that I am probably missing some
very fundamental, but haven't found it yet. Not sure why
I am not even getting the error messages in event log,
either. To the RDC session, it appears that there is no
redirection, but that client appears to be in the TS
server LAN (and able to print to TS server LAN printer
without issue).

Also (in case this helps), this WinXP Pro client was
first configured in the LAN of the TS Server, meaning
that I configured the Printer (using the VPN to the LAN
that will be the clients home to connect to the printer
for initial configuration) and testing the RDC connection
while still on the TS servers LAN. Once everything
worked, I packed up the WinXP Pro, and sent it to the
remote site. I first used the HP 4500 PCL 6 driver on
the WinXP, but then shifted over to the HP 4500 PS driver
which is native to the Win2000 TS server. I only mention
this in case my configuration of this system in a LAN
remote from it's home LAN , but which coincides with the
TS Server LAN, created any unusual dependancy that is
preventing the normal operation of the Printer through
RDC. I know that is a stretch, but thought I would add
that info anyway.

Thank you very much with all of the help so far, and the
quick responses.
-----Original Message-----
Please included the history of the thread in your follow- up, all
of the context is gone now.

Is it correct that only one client has this problem?
Are there other clients with the exact same printer that get their
printer redirected automatically?
This may seem a stupid question, but have you checked the settings
for printer redirection on the client?
I seem to recall that the client starts the TS session with a pre-
configured initial application. Have you checked if the printer is
redirected when the client connects to the full desktop?
Which version of the rdp-client do you use? Have you tried to
upgrade to the latest (5.2)?

http://www.microsoft.com/downloads/details.aspx? FamilyID=a8255ffc-
4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---


.
Have a Windows XP Pro client connected via Remote
Click to expand...
Desktop
Connection to a Windows 2000 SP 4 Server. Client has a
HP 4500 printer on LAN of client, while server has HP
5000 on LAN of server. The client connects right to an
application on the server (the Programs tab of RDC
settings has a program selected to start), but, when
attempts to print, cannot print to client-local printer
(HP4500), though can print to the server-local printer
(HP5000). The server has the HP4500 driver installed
that is used by client. The client can't even see the
HP4500 as a print option within the applications print
dialog box (only the HP5000). All of the Macintosh
clients that use the server can print to thier respective
local printers (and the W2K server shows all of
the "session printers" for each of the Mac clients,
though not for the Win client), but the only Windows
client cannot. All clients (Mac/Win) have printer
selected as a local resource to use during the RDC
session in the RDC configuration. The server TS settings
have client session settings used, and does not
have "disable Windows printing" selected.
 
Mmm, strange, epecially that you don't get any events.

Have you checked that the names of the drivers are exactly the
same on the client and the server? You might still need an entry
in ntprintsubs.inf like :

"HP Color LaserJet 4500 Series PS" = "HP Color LaserJet 4500"
(check names on your system)

The move to another LAN seems to be part of the puzzle, although I
don't really understand how. It's still the same domain, I assume?
Just to rule it out, have you checked the permissions on the
printer?
 
Vera:

Re: The Domain question: We don't have Active Directory
setup (as we are 2/3 Mac and 1/3 Windows, just have taken
the time to set up AD). So, there isn't a common
domain. In the remote site where the lone XP Pro client
is, there is only one other windows box (Win98) (rest are
all Macs), and haven't tried to put RDC on that yet to
see if it will work on Win98.

Re: The printer driver names. Am I to use the printer
name that shows up in the printer setup? I really don't
have an HP 4500 printer in the TS server LAN, so I just
installed an HP 4500 driver using LPT for port, then
deleted the printer after the driver was installed. But
the name of the printer on the TS server is "HP C
LaserJet 4500-PS (Microsoft Windows 2000)" (the added
name in parethesis is apparently to distinguish another
printer on that server named "HP C LaserJet 4500-PS
(Hewlett Packard)" (so wonder if I have non-TS compatible
driver causing problems, though the Mac's are still able
to print), so I will use that name in the .inf file. The
name of the printer in the WinXP Pro client is "HP C
LaserJet 4500-PS".

I will check the permissions on the HP 4500 as soon as I
determine how. It is an HP 4500N, so directly attached
to network with internal printer server. Therefore, does
not have a seperate host server hosting it.

Thank you.

Merrick
 
More info: I now have three WinXP computers that do not
appear to allow printer redirection. One in the remote
location, and two in the LAN of the TS-Server. At first
I thought that clients in the LAN of thet TS-Server would
not show the redirected printers, but saw that Mac's in
the TS-Server LAN do, so why shouldn't the WinXP Pro
computers? When the TS-Server local Mac connects, it
shows all of the printers that the Mac has assigned as
redirected printers, even though they are on the same LAN
and TS-Server and the printers attached to TS-server.
But the two WinXP Pro computers on the TS-Server LAN only
show the TS-Server printers when RDC to TS-Server (still
on same LAN). All of the printers (in both the remote
LAN and the LAN with TS-Server are HP network printers
(with internal print servers). Is this something that
will effect matter? TIA.
 
Back
Top