General discussion

Locked

Terminal Server printing issue

By haritswarup ·
I have 3 computers at a remote office, working on workgroup with each having their local printers. These computers use remote desktop to connect to the Terminal Server in the corporate office, which works on a domain. The local user accounts and password are matching with the domain, but they logon first to local computers, then using remote desktop they logon to terminal server.

After the users logon to terminal server, they are not able to print from there, however the printing works fine when they print from their local computers on to their local printers. It does not print from Terminal Server to their local printer.

Any ideas on how to enable this???

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by christophz In reply to Terminal Server printing ...

Would you post some additional information about your environmet?

Terminal Server OS/SP-Level?
Client OS, Remote Desktop Client Version?
Is there any error message popping up or do you see some eventlog entries?

Collapse -

by TonytheTiger In reply to Terminal Server printing ...

Are the drivers for the printers installed on the server?

Collapse -

by haritswarup In reply to Terminal Server printing ...

Yes, drivers are installed.

Terminal server is running on Windows 2000 Terminal Server.

Client is Windows 2000 Professional

But, the client location is NOT connected to the domain. They work on workgroup, whereas the Terminal Server is a part of Domain. The clients use Remote Desktop to connect to the Terminal Server.

Collapse -

by lmayeda In reply to Terminal Server printing ...

There are two possible reasons why your remote users are not able to route their reports to their local printers. 1) the same driver installed on the local machines must also be installed on the terminal server. (Same version, and operating system). I usually will download the driver to be installed on the local PC and also download the same driver to the terminal server. 2) Terminal servers do not like USB ports. You could either switch to a parallel cable if that is an option or within your workgroup you can share your printers and use the NET USE command to redirect the local printers to an LPT port. For example: your computer "computerA" has a HP6540 printer connected to your USB port, shared. On "computerB", go to the Command Prompt and issue the command: Net Use LPT2: \\computerA\HP6540 /persistent:yes
Then on computer B, add a printer, assign it to LPT2, name it HP6540XX and DO NOT SHARE. The Terminal server will be able to redirect reports to an LPTn port. ComputerB could also issue another NET USE LPT3: \\ComputerC\HP1200 /persistent:yes. I'm not sure if you're using a USB port if you can redirect your own printer to your LPT1 port... Net USE LPT1: \\computerA\HP6540 /persistent:yes. Then add printer, select LPT1 port, give it a unique name HP6540AA, do not share. In all cases, you must use the same driver on the local PC and on the Terminal server. Hope this helps.

Collapse -

by jhault In reply to Terminal Server printing ...

The other information that will help in diagnosing is what port are the printers attached to? and what is the actual port name?

If you are using a non LPT or COM printer port locally, there is a registry hack documented by Microsoft that resolves this issue.

If you are using an LPT or COM port, others have already asked for details of your configuration that will help. Plesae post the answers as soon as possible.

Collapse -

by haritswarup In reply to

Poster rated this answer.

Collapse -

by haritswarup In reply to Terminal Server printing ...

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums