Can ping back and forth, even see the machine thru Web Monitor but can't print to it. Made sure everything was reset to original settings when it supposedly worked, tried multiple setting variations on Fiery and C5100. Tried new cross over cable. All lights on for network card connections. Been a while since I've had to do a Fiery connection troubleshoot. About ready to suggest client remove the Fiery and use the internal set up if possible. Any suggestions?
Ricoh Pro C5100S and Fiery E42B Connection Issue
Collapse
X
-
-
Re: Ricoh Pro C5100S and Fiery E42B Connection Issue
Tried again, no luck.
Here's the thing that's odd IP Address for Server is 192.168.1.140
Copier is set to auto obtain but the IP address comes up 169.254.139.173 with Subnet mask 255.255.0.0 which I believe isn't correct.
On the older Fiery's the IP addresses would be the same and subnet would be 255.255.255.0, which at one point this one was.Comment
-
Re: Ricoh Pro C5100S and Fiery E42B Connection Issue
Both the C5100 and the Fiery have 2 Ethernet ports. The gigabit port is for connection between the Fiery and the C5100 only. You may have one or both of them connected wrong.Comment
-
Re: Ricoh Pro C5100S and Fiery E42B Connection Issue
Then that would leave me to believe there's some sort of problem with the network card in the copier. But at one point I could ping between the server and the copier and view the copier through Web Image monitor.but now I can't so I'm assuming there's some sort of cascade failure going on some where.Comment
-
Re: Ricoh Pro C5100S and Fiery E42B Connection Issue
I luckily have one just a few feet from me.
On back of copier, cable is plugged into center leftmost port, going to back of Fiery's RJ45 lowest port
Fiery RJ45 upper port is going to our network router
Copier has an IP range in system settings, interface settings in same IP range as fiery
Copier is 192.168.0.20 (example)
Fiery is 192.168.0.30 (example)
If its showing 169 thats usually APIPA which means its looking for a DHCP and can't find one meaning you'll need to set it statically or leave it on DHCP and maybe your cables are connected wrong which is why it can't find DHCP.
One thing that confuses me though is that you said you got on the WIM but I don't know how thats possible when it can't find the DHCP server. Did you do something between that?Comment
Comment