I, too, have a user using Terminal Server thru a Windows 2000 server.  Her HP 1000 printer is not supported, and I was wondering if the Dell Model J740 is a supported printer with Terminal Server.

I am sorry I don't have an answer for your question.

 

Mr Forum Moderator;

The issue has nothing to do with using the J740 as a Network Printer.  I have one user who has the J740 connected to her PC and she uses the Remote Desktop Connection in WinXP Pro to connect to our Windows Terminal Server.  This is not the same as using the J740 as a network printer.

I do have other users do this with Epson USB printers, and another using a Lexmark Laser via USB who have no printing issues from the remote connection.

However, the j740 will not print the jobs via the remote connection back to the local PC.

The printer is created in teh remote session but the print jobs will not print locally.

Mark

BeeJayGA,

The J740 is not a networkable printer and as such cannot be used as a network printer.  To allow use by other systems on the same network you can select to share the printer using windows file and printer sharing.  To set up the printer and share it across the network please see the following link.

http://support.dell.com/us/en/kb/document.asp?dn=1081464

 

Respectfully,

Hello --- is this thing on?

It's been 2 weeks and still no reply from the Forum Moderator.  This would lead me to beleive Dell has no clue and cannot help me make their printer work in a Remote Desktop Setting.

Mark

Mark:

Did anyone answer your question? I have a client with a Brother 5050 printer and it keeps dropping everytime he logs out of terminal services.  I can log in on TS and print his jobs on his printers with no problems. I'm in Chicago and he is in New York.

Trying to find out why.

Gary

 

 

The printer DOES appear when connected, there is just no redirection happening.  I do have the driver loaded on the WIN2000 Server.

You mentioned an updated driver, it's a Dell J740 printer - Does Dell or Lexmark have a new updated driver?

What happens is the printer job shows up in the HOST printer queue and once there is cannot be deleted nor will it print.  I can only clear out the queue by rebooting the server.

Given that how do I make this printer work when remotely connected?

There are a number of factors that may prevent the default client printer
from showing up as the default printer at the Remote Desktop host machine:

1) the printer redirection box may not be checked.

2) If the host machine is XP Pro, and SP1 has not been applied, there is a
bug which can prevent this redirection from working. This is resolved by
applying SP1 at the XP Pro host machine.

3) If the host machine does not have a driver available for the printer you
have at home, the redirection won't happen. In this case, there should be
an error message in the system event log on the host machine.

The fix for this is to install the driver for your printer at the host
machine. You should find a signed (i.e. certified for compatibility) driver
for your printer from the manufacture for the OS of the host
machine--Windows 2000 or XP. Install this driver on the host machine--it
doesn't matter that the printer is not physically present, nor does it
matter that you may use a type of connection at home which is not present or
available at work--just install as though the printer is there on LPT1. You
can, if you wish, delete the printer after installing. If you see a dialog
box asking whether the OS should delete the files for the printer driver,
say NO. This will leave the driver available for RD usage, but not visible
otherwise.

4) Your printer at home may be a multifunction device using a DOT4 port to
communicate. The DOT4 port is not redirected
by default. If you follow the directions in this KB article carefully:
http://support.microsoft.com/default.aspx?scid=kb;en-us;302361

you may be able to overcome this: Look at the very end of the article for
instructions about how to see whether your printer is connected via a DOT4
port. You will need to reboot your computer after making the registry
change suggested in the article before testing whether it works.