Mapping printers via Remote Desktop

[oztrailrider]

Hi all,

I have a business client with a weird printing issue. The customers have a workgroup network in their local office that has a network printer connected via an IP port to their local server running XP Pro. All the client machines are configured to use the shared network printer.

They run an application that is hosted on a Windows server 2003 terminal server in another office and use remote desktop to access it. Remote desktop also maps their local printer to the terminal services session whenever they connect. This has been working fine until recently. Now it seems that sometimes local machines on the network cannot create the mapped printers on the terminal server. They try logging on/off again several times and the printers still will not get created. They have even tried restarting their local machines to no avail.

I have been there twice now for this issue and both times I have walked in and logged off the terminal server, logged back in and the printers are there. There is an issue though and it seems to affect random machines intermittently. Any suggestions?.

[abe]

maybe two users using the app and both trying to map the printer at the same time

[LunchBox]

Last time I had a similar issue the user(s) had multiple printers in the control panel. As a result the printer it would map or not map but either way it would never print.

I deleted all printers for each user in question. Then (this happened multiple times) I deleted all drivers and any remnants of the printer for that specific user (cant remember now but I may also have gone to the registry). I stopped and restarted the printer queue both on the server and the local printer. After all this the issues went away.