I am trying to install the drivers for an xerox xc570 with an EX fiery through wifi with a macbook with os leopard.
The driver installs but at the step you have to select your'e printer on the network, nothing appears.
All the wifi pc's with windows are seeing the list of printers fine.
I tryed to type either of the printer or fiery ip adresses and the driver finds nothing.
Solved! Go to Solution.
The problem seems to prevent me from completing the driver setup.
I can't print with the mac.
Unfortunately I don't have access to the main router, so I guess it's a lost battle...
Anyway Thanks for your'e time Joe
Put the IP of the printer in the address bar of whatever device you want to print from.
If it works, we can figure out printing, if it does not, the network is blocking something.
So if it fails to print but loads the webpage, you need to discover what ports are blocked and why. To start, you just telnet those ports individually, which can be done on PC (Command Prompt) or Mac (Terminal)
Once Terminal or Command prompt is open, you would test general connectivity. So lets say the Fiery is on IP 192.168.1.100 for simplicity sake.
Type in ping 192.168.1.100 and hit enter, if you get a response, you have connectivity, and if you have connectivity, we can test if ports are open.
Printer ports are on port 9100 (RAW/HP Jet direct), port 515 (LPR/LPD) and port 631 (IPP/mDNS/Bonjour)
to test them, simply type telnet 192.168.1.100 9100 (just change 9100 to 515 then 631 to test the rest)
A good response is nothing (Just a blinking cursor usually)with this, if you get a response it means it was blocked, you would see something like this(Note I used a port I knew would fail to get a response here):
Now Cisco, and they owned Linksys till 2013, as well as some other manufacturers do block mDNS/IPP when going wired to wireless or vice versa. So anything wired works, but a wireless device technically on the same LAN will fail to a wired device.
But those issues do not occur with the other ports here. And realistically speaking, port 515 is better anyway, and works from Windows and Mac just fine.
If there is no connection in any way but ping gets a response, my guess would be that the router is assigning DHCP leases and that needs to be disabled on the 2nd router, then everything should be rebooted. Also, if the 2nd router is a bridge, and it sounds like it might be, make sure that the devices on the old router and new router both are using the same Gateway address, because if when you connect to router 2, and you get a different gateway than those on router 1, even ping will fail.