sharing USB printer

[dlw]

We have a win2k server, and a remote user with a USB printer. I'm trying to
get to the printer from the remote desktop. The remote user has XP Home,
they dial in to a RAS server, then RDP to the win2k server. We shared the
printer in XP, but cannot connect to it from the remote desktop, or anywhere.
We cannot ping the remote computer on the IP issued by the RAS server,
either. Is there any way I can get this to work?

[Vera Noest [MVP]]

You shouldn't need to share the printer, it should be redirected
automatically to the ts session.

Make sure that the client runs the latest rdp client, and apply the
registry changes from this article, if the local port is something
like DOT4:

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

Then let the user connect. If they printer still isn't autocreated
in the session, check your EventLog to find the reason. Most
probable cause is that the server doesn't have a driver fopr the
printer. If that's the case, map the printer to a native driver on
the server by creating a custom ntprintsubs.inf file. Details here:

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 ---

Post by dlw
We have a win2k server, and a remote user with a USB printer.
I'm trying to get to the printer from the remote desktop. The
remote user has XP Home, they dial in to a RAS server, then RDP
to the win2k server. We shared the printer in XP, but cannot
connect to it from the remote desktop, or anywhere.
We cannot ping the remote computer on the IP issued by the RAS server,
either. Is there any way I can get this to work?

[dlw]

Thank you, Vera, as usual your advice is right on. In this case, I
overlooked the obvious- the user did not have redirect checked in their
client settings, so no printer and no event message. Plus, I'm dealing with
disappearing event logs on the server, KB 829246, and trying to contact MS to
get that fix.
Anyway, I'm back on the right path now.
Thanks again.