TS 2000 and XP Pro client printing issue

[bjleicht]

I have a Windows 2000 member server running Terminal
Services. I have a client who is running XP Pro and
connects using Remote Desktop. They have a Brother 9700
Multifunction printer attached to their pc using usb
port. I have not disabled any mapping on the Terminal
Server Configuration. When they connect their printer
does not show up. I have another client that uses Windows
2000 Pro with the same printer and it shows up fine and
they are able to print it. What do I need to do to get
the printer to work with the XP client?

TIA

 

[Vera Noest [MVP]]

Check the name of the port on the client. You might have to make a
registry change on the client to get the port redirected.
Check the EventLog on the TS as well. If you see an Event 1111,
you might have to map the driver to a native driver on the server.

302361 - Printers That Use Ports That Do Not Begin With COM, LPT,
or USB Are Not Redirected in a Remote Desktop or Terminal Services
Session
http://support.microsoft.com/?kbid=302361

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

 

[Guest]

It's possible that they have different client drivers, so the one that doesn't work has a driver that isn't installed on the server. For example, if two users have LaserJet 4100 printers, but one installs as a "HP LaserJet 4100 Series" and the other installs it as a "HP LaserJet 4100 Series PCL 6" but the server only has the driver for the "HP LaserJet 4100 Series PCL 6", the other client's printer won't get auto-created

Check the system event log on the server for event ID 1111, which will tell you what driver is required. Once you have that info you can map the requested driver to the one that's already installed (using a user defined inf file), instead of adding more drivers to your server

Detailed info here
http://www.workthin.com/tsp.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- bjleicht wrote: ----

I have a Windows 2000 member server running Terminal
Services. I have a client who is running XP Pro and
connects using Remote Desktop. They have a Brother 9700
Multifunction printer attached to their pc using usb
port. I have not disabled any mapping on the Terminal
Server Configuration. When they connect their printer
does not show up. I have another client that uses Windows
2000 Pro with the same printer and it shows up fine and
they are able to print it. What do I need to do to get
the printer to work with the XP client?

TI

 

[Frank Neuner]

-----Original Message-----
Check the name of the port on the client. You might have to make a
registry change on the client to get the port redirected.
Check the EventLog on the TS as well. If you see an Event 1111,
you might have to map the driver to a native driver on the server.

302361 - Printers That Use Ports That Do Not Begin With COM, LPT,
or USB Are Not Redirected in a Remote Desktop or Terminal Services
Session
http://support.microsoft.com/?kbid=302361

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---


.

I think this is some compatibility issue that Microsoft is
not admitting to. I had the same problems and simply
solved the problem by removing XP and installing 2000.
I used the same printer driver and it worked with 2000 but
NOT in XP. Same client.

 

[Vera Noest [MVP]]

I think this is some compatibility issue that Microsoft is
not admitting to. I had the same problems and simply
solved the problem by removing XP and installing 2000.
I used the same printer driver and it worked with 2000 but
NOT in XP. Same client.

That's a weird way of solving a problem that is well-documented
and has a simple solution......
What you have experienced is probably that the driver name on XP
is not *exactly* the same as the driver name on Windows 2000
(client and server). Event the slightest mismatch in the name
causes the autocreation not to work. The solution is easy: just
map the name of the driver on the client to the name of the driver
on the server to make the printer autocreate.

No need to go back to an older version of the OS.

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088