mm

I have a similar problem with the same printer model HP4100N only after SP3
was installed on Terminal Server W2K.

I posted this today. If you find anything else plese let me know.

Hi,

I have a foxpro 6 app that is running off a mapped drive on a file/print
server access via Terminal server.

The printer is captured to Lpt1 via share name i.e. \\servername\sharename

The printer is also set as default which is a HP4100N.

Print jobs used to work but have suddenly stopped not long ago. Everything
else prints (excel, notepad, forpro database) but this particular app simply
sends print jobs to 'no where' via a Terminal Server session.

If I log in as admin via the console (directly onto the console of the TS)
the printers work for these remote sites. If I log in as admin via a TS
client session the print jobs don't work.

file/print NT4, TS Windows 2000 SP3 server, clients are W2K Pro SP3, Remotes
sites have file/print W2K SP3 servers (3 sites) where the printers are
installed.

I have checked the security - besides - excel files print why wouldn't the
foxpro app not print then?

I have tried all possible drivers (off W2K cd, HP downloads, HP beta).
Installing a HP 5150 printer on this server and the prints work!

It's either the HP 41000N or the TS or a bad marriage between printer model
and Terminal Services (HP certifies printer to be TS compatible)?

It may also be the Dell Open Manage app since SP3 was installed?

Anyone have ideas?

Please send direct reply to mm@cleanaway.com.au

Thank you