Posts: 31
Joined: 11.Jan.2005
From: Hampshire, UK
Status: offline
Greetings,
I have a printer (172.29.88.107) sat inbetween our firewall (172.29.88.2)and our gateway (172.29.88.11). This is all fine but the problem is i need to print to that printer from our internal network (192.168.0.*) which i have solved by adding it as a shared printer on our isa server so it can be printed to from inside and outside the network.
However, i need to move this printer inside our network range so i can relocate it to the relevant office since it is currently plugged straight into the lea supplied router in order for our accounting program to print to it. The accounting program is run via a citrix connection to the local council system and uses ip printing to print.
The problem is, i cannot move this printer into our range without loosing the ability to print from outside.
Posts: 31
Joined: 11.Jan.2005
From: Hampshire, UK
Status: offline
thanks for replying
yes thats how it happens, and the printer driver is installed their end to print to the ip address of the printer, which works fine if the printer is on their 172.29.*.* range, however when i have tried to move this inside our firewall it wont work.
Of course it will work. That how Citrix printing is supposed to work.
They need to get a Citrix Tech in there to set up printing.
I deal with this daily, me being a local consultant in Bermuda & head office is in London. All the Citrix clients here have local printers that receive the print jobs from their Citrix sessions in London.
The Firewall should not come into it if you are forwarding the correct Citrix protocols.
Posts: 31
Joined: 11.Jan.2005
From: Hampshire, UK
Status: offline
even if the address range is different? Problem i sthey keep claiming its because of a different address range and our firewall is the problem but i dont have the knowledge to say to them no it isnt.
Yes, even if the address is different. That's what Citrix is for....
That's why you need to get a Citrix guy to look at it. The printing gets done over the Citrix session, not independently. Eff all to do with the firewall.