I wrote last week and furnished you with incorrect
information. Rep offsite has Dell notebook running
Windows XP Professional with ONLY USB port for printing.
Has HP printer with ONLY USB connection capability. Has
wireless network at home; both printer and computer are
connected directly into wireless hub; under printer
properties, Ports tab, printer port is listed
as "IP_92.168.0.10" with description of "Standard TCP/IP
port". Still can't print when connected to our office
Windows Server 2000 terminal server. Reply to previous
question referred to a DOT4 port type, which is not the
case here (as the printer is not connected to the computer
but to the hub).

If the printer is not autocreated at all, then it's a driver
problem. Check the Eventlog on the TS to see the exact name of the
printer driver on the client, and map it to a native driver on the
server.

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

"Nancy Shelgren" <(E-Mail Removed)> wrote in
news:12d7501c44352$9270c5e0$(E-Mail Removed):

> I wrote last week and furnished you with incorrect
> information. Rep offsite has Dell notebook running
> Windows XP Professional with ONLY USB port for printing.
> Has HP printer with ONLY USB connection capability. Has
> wireless network at home; both printer and computer are
> connected directly into wireless hub; under printer
> properties, Ports tab, printer port is listed
> as "IP_92.168.0.10" with description of "Standard TCP/IP
> port". Still can't print when connected to our office
> Windows Server 2000 terminal server. Reply to previous
> question referred to a DOT4 port type, which is not the
> case here (as the printer is not connected to the computer
> but to the hub).