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 in 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...