Some Client Printer Mapped, Some Not

[Mike Simone]

Hello All -

We currently have a W2K SP3 server used just as a Terminal Server for
remote access for our out-of-town offices. Both can connect fine, but
when the second office connects, their local printer does not map. I
was able to get it printing by installing the printer (HP 2200
LaserJet) locally on the server and changing the port from LPT1 to
TS001 on the server. Of course, this only worked until the next day,
when they reconnected and inherited new TS ports.

The client that maps printers fine is an older Compaq desktop running
Win98 and connecting via shared DSL. The client that doesn't map
printers is a new HP Evo desktop running WinXP Pro and connecting via
dial-up. Both client connect to their printers via parallel cables on
LPT1, although the troublesome client shares that printer via switch
box with the call accounting machine in that office.

The obvious difference seems to be the connection speed - have other
users experienced similar problem? Or am I missing something else?

Any help would be greatly appreciated!

Sincerely,

Mike Simone

 

[Mike Simone]

Matthew -

Thanks for the reply! I do get messages in eventlog about not
recognizing the driver, which is very odd considering that the term
server connects to a networked printer of the same model here in the
main office just fine. (I am assuming I need to have the W2K drivers
installed on the server, not the WinXP ones the client would use. If
I'm wrong please let me know.)

Sure enough though, the ntprint.inf file doesn't have the 2200 listed,
so I will try the regedit and .inf changes in the MSKB article you
suggested.

Thanks again,

Mike Simone

 

[Matthew Harris [MVP]]

It all depends on the OS that is hosting the printer.
Different OSes identify the printer differently, and the
terminal server (even though it has the correct Windows
2000 printer drivers on it) doesn't know what printer
drivers match with which printers.

-M