JetDirect - Terminal Server problem

[Deanna Smith]

I am unable to get my HP 2200dn (with Jet Direct J4169a) to work on my Windows 2003 Terminal Server. It works fine locally. I have opened port 9100 on both firewalls. I have been able to get other printer servers to work in this environment, but can't seem to figure out what this JetDirect needs! Help would be greatly appriciated!!

[Thomas Bianco]

are either of the firewalls NAT? i think jet direct requires the ability to address bidirectionally.

when you say "it works fine locally", do you mean it works when you are on the console of the server, or it work when you connect it to your workstation?

look forward to working on this

[Deanna Smith]

We have T1 at both locations with WatchGuard SOHO fireboxes. I have forwarded on port 9100 at the JetDirect location, and only opened the port at the Server end. I have tried both forwarding to the Server or the JetDirect addresses at the Server end, but did not work.

Printer/JetDirect works locally for the workgroup that connects thru Terminal Services. However, only works on the workgroup level -- does not work in the Remote Desktop session.

Thank you for replying...I have really had a time finding help on this issue. It seems so few understand printing on TS. What puzzles me most is that I have been able to get other print servers to work (Hawking, IOGear) without any additional port configurations. I (obviously) do not understand what the JetDirect needs, and have been unable to get any answers! Thanks!

[Thomas Bianco]

ok, so you have two locations seperated by T1s to the internet and SOHO (probably nat) firewalls. let's isolate this into 2 problems.

1) can you connect to the jet directs from a workstation (on the same LAN as your server) by creating a standard TCP/IP port in the add printer wizard?

this will verifiy that windows printing works the way it should across the T1/firewall connect.

2) can you print from a terminal service session to a printer on the same lan as your server? create the printer on the server using the same proceedure as above.

this will tell us if there is a problem with the TS printing.

just for clarity, we are talking about a printer that is created on the server, not the (known buggy) terminal services redirected client-side printers, right?

[Deanna Smith]

For clarity I will name the locations: the TS location and the Sattelite location.

The JetDirect printer is at the Sattelite location where the pc's are a workgroup with no server. These pc's connect to the TS location thru Remote Desktop.

I have created this printer on the server solely to load drivers, as I normally do for printers that are not automatically detected (such as PhotoSmart printers). I did also try loading the "HP Network Wizard" software for the JetDirect...just to see if that would work (did not).

Yes, the printer works fine at the Sattelite location. But not thru terminal services.

[Thomas Bianco]

ok, it sounds like you are talking about the client side printer redirection. this is known to have issues.

take a look at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;264039
and see if this discribes your issue.

i strongly sugguest you create the printers on the server with some standard naming convention and ask the users to print to the server side printers. this is much simpler, and provides the same functionality.

[Deanna Smith]

Sure, however, these TS users need printed documents at THEIR location. This is a doctor's office and, for example, they need to print walk-out statements to give their patients.

There are 3 possible solutions to this problem, as I see it.

1) Forget the JetDirect and install it as a parallel...then that pc has to on TS at ALL times for anyone at the Satellite to print.

2) Install one of my other print servers (Hawking, IOGear, etc). These work MOST of the time...which is why we decided to buy an HP with a JetDirect...thinking it would be more reliable.

And this one I have not yet tried...
3) Make the Terminal Server a Print Server also.

I would have prefered to figure out how to make the JetDirect work, but perhaps it will not. I have phoned HP support. The tech I spoke to advised me they have no documentation concerning Terminal Services and the JetDirect.

Again, thanks for trying to help!

[Deanna Smith]

Ok...I have it working. Here is the solution, should anyone else need it:

At the Terminal Server, configure the HP printer's TCP/IP port to be the WAN IP of the remote location. Also, open port 9100 on any firewall.

At the remote location, configure the firewall to forward requests on port 9100 to be forwarded to the IP of the JetDirect printer.

There is not a need to install the printer locally on the remote pc's, unless they need it when NOT connected to the Terminal Server.

[Steve Anderson_5]

Deanna,

What a totally functional, yet simply solution for what I thought would be a problem requiring a 3rd party printer server software solution. We run MS Terminal services over a VPN and mapping an Ip printer port directly on the server was not something I had considered. Thank you for your clarity.