Server 2003 (where is it?) Generic Text Only Driver different than XP???

[louis sorbera]

We are having a problem with printers installed on XP PCs that connect to a
Windows 2003 Server, using Terminal Services. We installed the printer on
the PC using the Generic / Text Only definition on the COM1 port.(this
identical configuration has worked flawlessly on NT4 TSE, and Windows 2000
with Win 95, 98, NT and XP clients)

We then connect to the printer from the terminal server.

Whenever the PC is shutdown, it is necessary to first print a test page from
the PC (test page) before the printer connected via the 2003 Server will
print anything but blanks.

NOTE: Printing from the test page via the connection on the server does not
help, it must be from the local PC for the server connection printer to
work.

NOTE: It is no longer possible to change the printer driver on the connected
printer on the Server as it was in NT4 and 2000.

NOTE: All testing was done with the Windows Test Page.

NOTE: We also have HP Laser 4 printers configured on the LPT1 which work
flawlessly.

We changed the driver to Epson FX-80 which is a compatible bit mapped
driver, but that did not help.

Is the problem with Serial client printing?

 

[louis sorbera]

Thanks for the tip, however I'm not sure how I would use it.

I know that you can substitute drivers, let's say for instance an HP4 for an
HP6P, but what should the faked out printer be for Generic / Text Only?

The other peculiar thing is that until the user prints from her station
locally, it prints blank pages (the correct number) from the server, but
after printing the test page locally, it is fine from the server.

Also, doesn't it load up the driver from the station? It wrns you about
viruses when loading a driver from a connect to type printer i.e., rather
than local.

It seems like such a fundamental problem, i.e., Microsoft printing to a
printer on another station, that it is not possible it doesn't work.

 

[louis sorbera]

We've attempted contacting the manufacturer of the printer but they have not
responded.

We tried the Epson FX-80 on the PC (Local driver) but it responded the same.

The HP 4 definitely would not work. All we need is a very dumb ASCII output
to the printer. We're talking ancient stuff here, which is what makes this
so frustrating.

This is technology that has worked in the "Terminal Services" environment
since the very first Windows version was produced by Citrix on NT 3.51.

The other thing that is frustrating is that it feeds a print job, but it is
blank, so you know it is getting something.

The only thing different is Windows 2003.

 

[louis sorbera]

Dear Chia-Kai Hsu
Thanks for getting back with me. I'd like to forward the following info for
your review and/or submission to Microsoft for their answer, if applicable,
prior to any discussion of the issue.

On this same 2003 Server is another Station which does not exhibit the
problem reported.

There are 2 differences I want to submit to help pinpoint why this is not
working. One is directly an issue you must address. The other might require
input from Microsoft.

The working PC has an SE250 vs., an SE300 on the non-functioning PC. The
other difference is that the printers on the working station are configured
using the IP address for the station and not the Computer Name, however, it
should be noted that the PC that exhibits the problem has an HP Laser
configured using the computer name and there is seemingly no problem with
using the computer name vs. IP address for the HP Printer.

This leaves the difference between the SE250 and SE300 as the only remaining
problem. Do you agree? Is there a problem with compatibility with Windows
2003 Server and the SE300? Is there a problem with compatibility with
Windows 2003 Server and the SE300 in a Terminal Services environment?
Thanks,
Louis