Print to my remote office

[tk421]

I've got a setup between two offices here. the main office has a 2k server running terminal services. the 2 clients at the remote office connect to terminal services to perform most of their daily functions.

problem is, there are some problems for the users at the remote office (call it office 2) printing to their own printer (at office 2). I decided to install the printer on the Terminal Server, that way it'd be available within TS sessions. well, that is proving more difficult than i thought.

It is a HP 1200 networked printer. i've opened up all the ports in the router that i think i need, and HP Web Jetadmin finds the printer, but then reports:

Device communication error
bad packets received
transmission errors

It sees the printer just fine, but can't print because of these errors. These are the ports I've opened:

9100
161
162
631
67
68
69
427
443

don't think i need them all, but i'm trying to find the right one here. anyone know what i need to do to get my win 2k terminal server connected to my remote printer? thanks.

[NooNoo]

Have a read here is the printer in question usb?

[tk421]

i'll read up there. the printer has a builtin jetdirect card. i'm trying to use the hp web jetadmin to configure the printer. (incidentally, i've also tried the regular hp install network printer wizard, but it fails with an error, and suggests to use the web jetadmin).

[Gollo]

Originally posted by NooNoo
Have a read here is the printer in question usb?

Nope. It's a network based printer (has the network card installed)

Anyways how about having the terminal service grab the printer and then share it (kinda redundant I know) but that should solve the problem of not being able to print remotley as the terminal client sends all that info through it's port(s). Cheers.

[tk421]

>>how about having the terminal service grab the printer and then share it

This was my plan originally. But it doesn't seem to work reliably. Sometimes it connects, but because it's a networked printer, TS client doesn't pick it up all the time. (TS printers only get connected reliably when they're local printers, I've experienced.)

[Gollo]

Can you capture the printer to a port say LPT2 and then have the computer think that it is local? This might help on the reliability side. Cheers.

[tk421]

i guess i could just do that. if i can't figure out how to do it this way then i probably will.

[tk421]

FYI: found out that the little jetdirect box that comes bundled with the LJ 1200 printer i was working with (i think it's the 170x) isn't capable of IPP, which is what is required apparently for Internet printing. I have to upgrade to the 300x or higher.

I'm working on getting the printer to be seen as "local" so it will work in Terminal Services.

[SpongeBob]

here is what you do....

setup VPN access to your network via public internet. (all cisco router and firewalls can do it, so can most other manufactures)

Windows 2000 server also has "dial in" via VPN capable.

then connect to work through a encrypted VPN, which make your hom PC just like if it was plugged into a cat5 drop at work!

map to the printer by it's internal ip or print server, and print away.

I do this to print my timesheets while i'm gone on vacaction or out sick!

very handy alos if you are on call over weekend and want to work from home.

(add VNC to your servers and you have 99% remote admin powers and security via VPN!!!)