Ricoh mpc300 Network Connection failure

[Jama]

Ricoh mpc300, it pings via CMD, also prints via USB ok, but cant connect via network, when auto obtain, it shows 169.254.137.1 also mask 255.255.0.0.. Either static Ip not connecting at all but pings 100%. Copying and other function working perfect including printing via USB cable. Any lead to this will be highly appreciated.

[Phil B.]

Ricoh mpc300, it pings via CMD, also prints via USB ok, but cant connect via network, when auto obtain, it shows 169.254.137.1 also mask 255.255.0.0.. Either static Ip not connecting at all but pings 100%. Copying and other function working perfect including printing via USB cable. Any lead to this will be highly appreciated.

so you have RJ45 AND a usb connected?

print out internal settings page is IEEE 802.11 enabled?

most machines cannot have RJ45 and usb active at the same time

169.xxx.xxx.xxx IS NOT a VALID network address.

what does config page show as the machine IP?

have you tried with a laptop and NEW RJ45 cable?


Phil B. " The Dentist "

[mikadonovan]

And subnet mask is normally 255.255.255.0, not 255.255.0.0.

[bsm2]

input a hard ipadress and retest.

Machine should have a static ip address anyway.

Also check for a duplicate ip address

[slimslob]

Disconnect the network cable and try pinging again. If ping goes through you have something on that IP address.

[slimslob]

And subnet mask is normally 255.255.255.0, not 255.255.0.0.

I have had accounts with multiple locations each with its own subnet where 255.255.0.0 was necessary. I even had one where all the print devices were on a different subnet than the computers.

[Oze]

And subnet mask is normally 255.255.255.0, not 255.255.0.0.

When a Ricoh can't connect via DHCP Mika it gives that bullshit I.P. and subnet....255.255.0.0

[slimslob]

When a Ricoh can't connect via DHCP Mika it gives that bullshit I.P. and subnet....255.255.0.0

so you have RJ45 AND a usb connected?

print out internal settings page is IEEE 802.11 enabled?

most machines cannot have RJ45 and usb active at the same time

169.xxx.xxx.xxx IS NOT a VALID network address.

what does config page show as the machine IP?

have you tried with a laptop and NEW RJ45 cable?


Phil B. " The Dentist "

It is not Ricoh, it is Microsoft. The IP address valid and it and the subnet are not bullshit. Actually 169.254.xxx.xxx is a private address space reserved by Microsoft for Windows computers and connected printers that are on a local network that does not have a DHCP. Since the third octet is random a subnet mask of 255.255.0.0 s required.

[Oze]

It is not Ricoh, it is Microsoft. The IP address valid and it and the subnet are not bullshit. Actually 169.254.xxx.xxx is a private address space reserved by Microsoft for Windows computers and connected printers that are on a local network that does not have a DHCP. Since the third octet is random a subnet mask of 255.255.0.0 s required.

And yet.....it shall hithertoforth be known as a bullshit I.P. address.........because it's not the one I want

[MikeACS]

The 4-ish times I've seen DHCP bring up a 169. IP address the issue was with the wiring connecting the copier to the modem, like a bad switch, or the port of the modem itself being defective (No power on the line gave 11.22.33.44, but power with a bad connection gave the 169 address). If it's reasonable I'd try directly connecting the copier to the modem and see if DHCP picks up something different, or test the lines if you've got the equipment. That being said I wasn't able to ping a set static IP when I dealt with mine, so I'm not sure about that.