Sheridan Posted November 17, 2015 Posted November 17, 2015 Has anyone got this working with their Windows Print server? I've installed it on our 2012 Server and shared 2 printers, which now appear in the management console I deployed them to our test chromebook where they now appear - yet when I try to print from the chromebook it sticks at 'Printing..' and nothing else happens. Are there any other firewall ports that need to be opened? I've got 5222 open through the firewall from the print server but I can't find mention of any others.
fiza Posted November 17, 2015 Posted November 17, 2015 We go through London Grid and looking on our firewall rules that they implemented for us to allow Google Cloud print I see the following ; Source IP = my print servers internal IP Destination IP = 173.194.0.0/16 207.126.144.0/20 209.85.128.0/17 216.239.32.0/19 64.18.0.0/20 64.233.160.0/19 66.102.0.0/20 66.249.80.0/20 72.14.192.0/18 74.125.0.0/16 Ports = TCP 5222 We use papercut which makes google cloud print much easier.
Sheridan Posted November 17, 2015 Author Posted November 17, 2015 I've got 5222 open completely from our print server to test this and still no joy. Definitely no incoming ports need to be open?
edutech4schools Posted November 18, 2015 Posted November 18, 2015 I tried setting this up yesterday, I have the correct ports opened, installed Google Cloud print service on the print server, but when I print from a test client the job gets received on the Google printer Q but never makes it back in to the school.
maark Posted November 18, 2015 Posted November 18, 2015 I had problems when deploying from google console - they appeared under local destination on chromebook but would not print. Sharing them to a user or group worked - the user goes to print - destination - change and google cloud print. It still seems to stick on printing message but the job comes out. Beware if sharing to a group the owner of the group has to accept the sharing invitation on behalf of the group -I had no owners set on groups in google console initially.
CyberNerd Posted November 18, 2015 Posted November 18, 2015 We have it working in conjunction with Papercut. I don't recall the setup being particularly different than suggested above: port 5222 to the servers listed.
fiza Posted November 18, 2015 Posted November 18, 2015 I've got 5222 open completely from our print server to test this and still no joy. Definitely no incoming ports need to be open? None that I know of and its working for us but as I said we use Papercut.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now