Server 2008 r2 can't ping Sharp printers


  • We have two sharp printers that we network print to, also some Samsungs and HPs. We recently changed the hardware of our server (HP ProLiant rack mounted) but kept all configuration the same. We can network print to the Samsungs but not to the 2 x Sharps, our printer lease co. have tested and we can install the printers locally but not through the network. We have changed port/cable/ip address/switch/drivers/stopped and started spooler  and even swapped the port of the Samsung that works with the one of the Sharp that doesn't but the Samsung continues to work and the Sharps continue not to. At the most basic level I can be on a workstation and ping the printer, I then remote onto the server on that same workstation and cannot ping the printer so it is basic communication between server and Sharp printer that is the issue. Have turned off virus protection briefly, checked printer and file sharing settings on firewall are enabled, all are on.  I am now at the end of my limited knowledge of these matters and have no idea how to proceed. We are in a perfect storm scenario where the print company and server installation company can point fingers at each other to no avail, meanwhile I have installed locally the printers to a handful of critical users but the majority of our users (the students) cannot unless I install on countless laptops.  Any suggestions would be most welcome, seems like I'm going to have to figure this one out on my own. Thanks.
    Thursday, May 02, 2013 8:44 AM

All replies

  • Hi, please post that to allow us to help;

    ipconfig /all from the server.

    ipconfig /all from the workstation.

    and a printscreen of the network configuration of the printer.

    (My first idea is a bad netmask)


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: |

    Tuesday, May 07, 2013 3:01 AM
  • Once you determine your network issue, there will no longer be a print issue.

    Alan Morris Windows Printing Team

    Tuesday, May 07, 2013 7:39 AM
  • Have print screens but won't let me put them up until this account has been verified! Hurry up Microsoft, want to solve this problem! Thanks.
    Thursday, May 09, 2013 12:29 PM
  • Add the ipconfig data.  No screen shot required.  You have a network problem here.  There are a bunch of good people here who have had to get there networking setup properly before they can get network printing functional.  Send the info you can.

    Alan Morris Windows Printing Team

    Thursday, May 09, 2013 7:33 PM
  • Finally got verified anyway but here are the details I think you want:

    ipconfig for server:

    ipv4 address:

    Subnet mask:

    Default gateway

    DNS servers and

    ipconfig for workstation:

    IPv4 address:

    Subnet mask:

    default gateway

    DHCP Server

    Sharp printer configuration

    IPv4 address:

    Subnet Mask :

    Default gateway:

    Primary Server

    Thanks Ruth

    Friday, May 10, 2013 8:39 AM
  • I'm just a print guy.  The server's IP is the same as the default gateway and DHCP of the client.

    I seems like the gateway for the server should be the same as the client and printer gateway.

    Alan Morris Windows Printing Team

    Friday, May 10, 2013 10:29 PM
  • I agree with Alan for the gateway.

    Something is wrong with the ping, as for a ping -> it should be a direct broadcast via your switch

    A confliting IP maybe, put a laptop on that IP and monitor with wireshark the network traffic. If it's not a double IP's problem it's then a switch problem.

    Just to be sure too you can post a "route print" from that server too, to be sure it does actually try in the LAN.

    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: |

    Monday, May 13, 2013 3:26 AM
  • Banana fingers strike again, sorry guys, Default gateway for server is  (not 11);

    ip for server is

    Monday, May 13, 2013 8:35 AM
  • If on the same network within the same scope, you have to isolate if it's a switch problem or a badly firewall setting somewhere.

    Use the portable wireshark in the worst case;

    Run it on your server and write in the filter; ip.src== || ip.dst==

    After try the ping. You should see attemp for the ping -> but no answer ( ->

    Unplug the sharp printer after, and put the IP into a laptop and plug it at the same exact place as the sharp is plugged (rj45). Run the wireshark again (on the server and the laptop).

    If you see nothing from, then your switch got a misconfiguration. If you see something, then the sharp printer got a network card problem. 

    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: |

    Thursday, May 16, 2013 1:39 AM