Desktop printers unable to ping.

[grahamd22]

Hi All

 

We have moved from server 2012 R2 to server 2019, which is fine but moving our print server has not quite worked as all the MFP's moved across fine and working with PaperCut but the desktop printers have not they can't be pinged by the new servers, only the old servers and general desktop devices can ping them fine. If we can solve this then we should be able to get users to print with them using PaperCut as at the moment they are using a direct IP port configuration bypassing PaperCut.

Our 3rd party printing company can’t understand what is happening and we too are at a loss, do you have any ideas for this or what we can do to resolve this is issue?

[Foresthippy]

Wrong subnet mask on the new server? Just a thought...

[grahamd22]

the subnet mask is the same on the desktops as the MFP's.

[Davit2005]

the subnet mask is the same on the desktops as the MFP's.

 

What about the server, is that on the same subnet as the printers or different, is there any L3 ACL on core switches or is there a firewall in between the subnets.

 

Also try disabling the firewall on the server temporarily to see if that resolves.

[grahamd22]

it was in fact the default gateway had not been correctly transferred.

[Davit2005]

it was in fact the default gateway had not been correctly transferred.

 

I've seen worse happen when someone accidently configured the servers IP address the same as the networks default gateway. That was fun but they quickly realised jus as all our monitoring software started going hay wire