spower22
asked on
RDP connects Drives but remote printer not available
RDP from on domain to another, connects with issues but I have both the shard local drives and printer checked on the connection but when the user try to connect the windows warning -
The follow local resources will be made available to the remote computer. This may be potentially unsafe.
- disk drives
etc. etc. but no reference to the printer. I'm connecting on port 3394 which is the only thing different from usual. Any suggestions? Thanks
The follow local resources will be made available to the remote computer. This may be potentially unsafe.
- disk drives
etc. etc. but no reference to the printer. I'm connecting on port 3394 which is the only thing different from usual. Any suggestions? Thanks
And please read this thread as you violated TS's first rule of thumb: do NOT install printer drivers on a Terminal Server.
https://www.experts-exchange.com/questions/22957768/Terminal-Server-printing-problems.html
This thread has a lot of relevant information for your particular issue.
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
https://www.experts-exchange.com/questions/22957768/Terminal-Server-printing-problems.html
This thread has a lot of relevant information for your particular issue.
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
ASKER
Hi,
I'm RDP'ing between two XP pc's so surely the 'host' has to have the printer drivers installed or am I misunderstanding your post?
I'm RDP'ing between two XP pc's so surely the 'host' has to have the printer drivers installed or am I misunderstanding your post?
Between two XP PCs, yes. You need the driver on both machines. Same driver.
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
ASKER
It's installed on both PC's The remote PC is configured to print to a network printer (HP4050n pcl6 driver) and the driver is installed on the host but the printer is not installed as such but when I connect the warning only mentions drive sharing and no virtual printer connection is created. I've configured it numerous times before without issue so this one is baffling me...
If you change the printer to be a local printer instead of a network one (by simply setting the port to LPT1:) does it work then?
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
ASKER
no
ASKER
my mistake, it does create the virtual printer when i choose lpt instead of the ip port. this isn't much good to me though as it's a network printer...
ASKER
If I change the port from lpt to the ip port once the virtual printer has been established then it will print to the network printer but once I disconnect and reconnect the problem returns.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks, i'll give try it and report back
Have you even enabled printer redirection on the rdp client?
for that go to start-->run-->mstsc, click on the "local resources" tab and make sure that "printers" is checked.
for that go to start-->run-->mstsc, click on the "local resources" tab and make sure that "printers" is checked.
Note that you should NOT install the printer driver on the TS unless you do know the driver is FULLY compatible with Windows Server 2003 AND works properly under Terminal Services.
Do you see any errors on the TS event log at the time you connect?
And finally, are you using the latest RDP client?
If using an older version this article applies in case your printer is using a different port on the client.
http://support.microsoft.com/kb/302361
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services