How can I reset the Web Image Monitor?

[Jeremy-Ricoh]

Hello All,
I have a Ricoh Aficio SP C420DN, it's a rather new device to the market, and new to me. During my testing of the web image monitor I seem to have set something incorrectly, and now I can't reach it over the network.

When using Static IP address or DHCP the device is un-ping-able from my computer.

This all started happening after I set some things in the Web Image monitor. Unfortunately, I don't remember what I did (it's been a few days).
Is there anyway to reset everything in the WIM without actually logging in to the WIM?

I tried deleting the user codes, but it looks like that only resets the items set on the front panel of the device.

USB works fine.

[schooltech]

What settings are shown on the configuration page that you print out? Settings such as ip addy, etc.

Maybe you somehow disabled the tcp/ip protocol; the config. page will tell you that.

You should be able to config. the printer through the control panel-as much as that can sometimes suck.

[Jeremy-Ricoh]

Right now it's on the DHCP, using the corp network.

On the Config page it says
IP address : 172.27.183.183
Gateway : 172.27.183.129
Subnet : 255.255.225.128
Host Name : RNPCF2AEF

If I ping 172.27.183.183 it returns "Request timed out"
If I ping rnpcf2aef it returns "157.55.143.176" "Request timed out".

When on a private network (using 10.0.0.4 printer, and 10.0.0.8 computer) it does the same thing "Request timed out".

[Jeremy-Ricoh]

Oh friggen heck..
So I thought to my self, maybe IPSec is on?
It was, so I disabled it, and now all is happy.

Do you think it could be a problem with the firmware not liking IPsec?

[schooltech]

IPSec is a layer 3 protocol, having to do with VPN's. Even though you have a 172.27.x.x. addy, that still is a private-range addy. 172.16-172.31 is a class b address used for non-routable addressing. So, technically, you are still on a private network. Anything in 10.x.x.x is because it is in a class A range.

It must have been looking to be involved in tunneling encrypted packets to a non-VPN setup. Not exactly sure there, but it obviously did not like it.

That's an oddball subnet for a Class B network, but it will work-it's just reducing the nodes on 'that' particular network.


Brings back networking memories of college courses & an old IT job I had. Man, how much you quickly forget if not in it on a daily basis.