General discussion

Locked

Terminal Server - Remote System Printer

By philldmc ·
I am running a Windows 2003 Standard server with terminal services. Two of my clients who RDP in want to use their local printer as their default printer.

I have configured this and it works. However when they log off and back in the printer needs to be reconfigured. What do I need to do to get the server to automatically remember this printer and make it the default printer every time this person logs in without having to go throught all the steps again?

This conversation is currently closed to new comments.

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

All Comments

Collapse -

by zaferus In reply to Terminal Server - Remote ...

I have seen this issue before, the easiest way I know of to fix the issue is to share their printers and have the printers installed on the server over from their system printers.

On the server set permissions so only they can print to their perspective printers. This will prevent others from printing jobs to their local printers.

Then when they log in they can select their printers to print to.

-Z

Collapse -

by gpratt In reply to Terminal Server - Remote ...

This is pretty straight forward, but there are some steps that must be done on the terminal server to ensure that the configuration is correct:

1) In Terminal Services Configuration, go to Client Settings, make sure that "Use connection settings from user settings" is NOT checked.

2) Select "Connect client printers at logon" and "Default to main client printer"

3) Make sure that "LPT port mapping is not disabled.

This should solve your problem with the users.

Garry

Collapse -

by philldmc In reply to

I had already configured those settings. Thanks.

Collapse -

by mjost In reply to Terminal Server - Remote ...

The server would not remember anything other than what the RDP from XP workstation connecting has installed and its default status. If you are saying that the local resource printer option is not staying selected then recreate the under administrator and save. If it is always checked and it is being disabled check the to see if it is being disabled by the Terminal Services Group Policies.

Hope this helps.

Collapse -

by mjost In reply to Terminal Server - Remote ...

The server would not remember anything other than what the RDP from XP workstation connecting has installed and its default status. If you are saying that the local resource printer option is not staying selected then recreate the under administrator and save. If it is always checked and it is being disabled check the to see if it is being disabled by the Terminal Services Group Policies.

Hope this helps.

Collapse -

by philldmc In reply to

for some reason this response showed up 2 additional times.

Collapse -

by mjost In reply to Terminal Server - Remote ...

The server would not remember anything other than what the RDP from XP workstation connecting has installed and its default status. If you are saying that the local resource printer option is not staying selected then recreate the under administrator and save. If it is always checked and it is being disabled check the to see if it is being disabled by the Terminal Services Group Policies.

Hope this helps.

Collapse -

by philldmc In reply to

for some reason this response showed up 2 additional times.

Collapse -

by lmayeda In reply to Terminal Server - Remote ...

If you've successfully printed from the client session, then the print drivers for the local printers have been installed on the server. However, to "keep" the printer visible from one session to another, I create a printer on a server where it is shared, then on the local client, I add a printer pointing to the print server and using an LPT port. Also on the local printer, in command mode, I issue the NET USE command to assign an LPT port to that printer. For example: on the server, the printer is: ServerXXX\Xerox470 . The command would be : NET USE LPT2: \\ServerXXX\Xerox470 persistent:yes
The NET USE command redirects the printer from the server to LPT2. (Note: when defining this local printer, select LPT2). The only problem I've seen, is on occasion, the NET USE command will disconnect and I've had to delete the statement and re-enter it.

Back to Networks Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums