XP Clients using W2K Terminal Services - Strange Printer Issue

[Guest]

I am running W2K Terminal Services and have several users that were connecting from home using W98 and W2K computers using the Remote Desktop connection. They were working fine, printers and all. They used mostly older HP Deskjets which work great.

The problem is: They bought new computers with either XP home or professional and now their printers will not redirect like they used to. Like I said above, the printers are not new and have automatically redirected beautifully in the past.

So, what can I do? Is this an issue of XP clients using a W2K Terminal Server? Or is there something else going on?

Please help! This will only get worse!

 

[Vera Noest [MVP]]

Probably a mismatch in the printer driver name on the client and
the server.

Example: if the driver name on W98 and W2K was "HP DeskJet", but
on XP it is "HP DeskJet Series", then the TS won't recognize the
printer and won't sutocreate it. Driver names must match *exactly*
and are case sensitive.
This should be logged in the EventLog.

The solution is to creade a custom ntprintsubs.inf file with the
correct driver name substitution.

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

 

[Yuri Palagin]

Dear Vera,

I seem to have a similar situation with printers not autocreating in
terminal session from a few machines. But there is nothing in the logs about
that. I do trace the printers which are not recognized automatically by the
server, and I include them in the ntprintsubs.inf file, and it works fine.
But sometimes printers are not autocreated, and there is no chance to trace
that because eventviewer logs reveal nothing.

Here's my previous post, describing some details:


Hello everybody!

I am having this problem on several client machines.

A win2k+SP4 terminal server in a win2k domain environment. A client
(mstsc,
build 2600) connects to the terminal server via a WAN with restricted
tcp/udp ports (netbios, rpc, smb - all blocked). The client has one local
printer (hp1200) and a few network printers within his LAN.
In the domain user properties the "Connect client printers at logon"
setting
is on, and so is the mstsc setting (concerning automatically connecting
printers on the remote server). Also, in the RDP-Tcp properties on the
server, both "Use connection settings from user settings" and "Windows
printer mapping" are on.

Nonetheless, when the client connects, his local printer is not connected
in
the session, though his network printers are. No errors/warnings in the
log,
other clients using hp1200 printers on the same server ok. The hp1200
driver
is mapped to HP LaserJet Series II using the method described in KB239088.

When I have the same problem within the LAN, I resolve it by sharing the
client printer and connecting to it via network from within the terminal
session. But in a WAN with restricted protocols I cannot do that.

So how do I resolve that?

Thank you for any keys and ideas...

ypal


"Vera Noest [MVP]" <[email protected]> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ
× ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ: