Terminal Server Printing

Greetings. Got a problem I'm working on, hoping someone can help. We're
having some issues printing from a UNIX Server, hoping someone can help.
Here's the situation:
We have remote offices that use Microsoft Windows Remote Desktop Client to
connect to a Windows 2003 Terminal Server. From this server they run a
program on a UNIX server. When they try to print to their own printer located
in the remote office (both local and networked) from the program on the UNIX
server, it does not work. It appears to be sending the print job, but nothing
happens. We've tested printing from the Terminal Server to the remote printer
and it works fine. It's only the UNIX printing that is failing.

What can we do to allow this terminal server to see the remote network? If
we can get this working, we should be able to get the network printers to
work, as we can ping them and add these remote addresses in the UNIX server.
But at the moment we can't ping the rmeote netowrk. There is no money to
spend on new hardware, so new firewalls are not an option. They just have
basic Linksys Firewalls.

Any ideas??? Thanks.

MPW

Hello,

I think that you can solve your problem by installing Print Services for Unix.
With this addon of Windows Server 2003 the Windows Print Server
"understands" Unix print tasks.

"MPW" schrieb:

> Greetings. Got a problem I'm working on, hoping someone can help. We're
> having some issues printing from a UNIX Server, hoping someone can help.
> Here's the situation:
> We have remote offices that use Microsoft Windows Remote Desktop Client to
> connect to a Windows 2003 Terminal Server. From this server they run a
> program on a UNIX server. When they try to print to their own printer located
> in the remote office (both local and networked) from the program on the UNIX
> server, it does not work. It appears to be sending the print job, but nothing
> happens. We've tested printing from the Terminal Server to the remote printer
> and it works fine. It's only the UNIX printing that is failing.
>
> What can we do to allow this terminal server to see the remote network? If
> we can get this working, we should be able to get the network printers to
> work, as we can ping them and add these remote addresses in the UNIX server.
> But at the moment we can't ping the rmeote netowrk. There is no money to
> spend on new hardware, so new firewalls are not an option. They just have
> basic Linksys Firewalls.
>
> Any ideas??? Thanks.
>
> MPW
>

Found a workaround:
Created a local printer on ther terminal server using lpt2. Shared their
remote printer on the TS. Mapped LPT2 to this shared printer using net use
lpt2 \\terminalserver\sharedname.

Then they were fine.

"GeorgZ" wrote:

> Hello,
>
> I think that you can solve your problem by installing Print Services for Unix.
> With this addon of Windows Server 2003 the Windows Print Server
> "understands" Unix print tasks.
>
> "MPW" schrieb:
>
> > Greetings. Got a problem I'm working on, hoping someone can help. We're
> > having some issues printing from a UNIX Server, hoping someone can help.
> > Here's the situation:
> > We have remote offices that use Microsoft Windows Remote Desktop Client to
> > connect to a Windows 2003 Terminal Server. From this server they run a
> > program on a UNIX server. When they try to print to their own printer located
> > in the remote office (both local and networked) from the program on the UNIX
> > server, it does not work. It appears to be sending the print job, but nothing
> > happens. We've tested printing from the Terminal Server to the remote printer
> > and it works fine. It's only the UNIX printing that is failing.
> >
> > What can we do to allow this terminal server to see the remote network? If
> > we can get this working, we should be able to get the network printers to
> > work, as we can ping them and add these remote addresses in the UNIX server.
> > But at the moment we can't ping the rmeote netowrk. There is no money to
> > spend on new hardware, so new firewalls are not an option. They just have
> > basic Linksys Firewalls.
> >
> > Any ideas??? Thanks.
> >
> > MPW
> >