MP 171 Access Control Range

[sandmanmac]

Re: MP 171 Access Control Range

Those Access Control Ranges sure look like DHCP address ranges, and DHCP is turned on according to the config page.
You've probably already tried turning DHCP off, though.
Just for fun, I tried running tracert on one of the addresses to see who the range was assigned to, but my attempt timed out after 11 hops. Still, you might want to try tracert and see if it helps.

It always fun when i get into these network discussions that reinforce how little I really know about this stuff.
I do appreciate the input Gene, but honestly, I don't have a clue what a tracert is or how to break one down.
I finally realized there was an SP to enable telnet which I ahould have found sooner, and I was FINALLY able to log in there after resetting the Admin password, and I got the access range flushed.
My first ever telnet session! I thought I was home free, and was getting ready to celebrate, but I STILL can't access the WIM, or print.
Then I ran the commands to get the Web, Http, Diprint, etc, up, but still no luck.
Did I mention that I can (and always could) ping the machine, and I can ping my laptop from the machine too?
I'm posting a copy of the I/F report that may indicate to one of you experts what might still be going on- almost all of it means nothing to me.
At this point, I'm just sort of a dog with a bone. I can't seem to let it go

Thanks for all the advice!
Interface settings.pdf

[zed255]

Re: MP 171 Access Control Range

Looks like DHCP is active and is assigning itself an APIPA address (169.254.x.x / 255.255.0.0) due to there being no DHCP server serving the request for an address. You only posted page 3 of the Network Interface report, so I can't see if there's anything else going on.

[Oze]

Re: MP 171 Access Control Range

We just now had this very issue and fixed it.
Set the MFD to an IP address covered in the Access Control list.
Log in to the WIM from a desktop (or your laptop via crossover if you'd rather) and blow away the Access Control values in Device Configuration/Security.

[keithxxiii]

Re: MP 171 Access Control Range

OZE's method is the one we are doing whenever we face the same problem. It works like a charm

[slimslob]

Re: MP 171 Access Control Range

Looks like DHCP is active and is assigning itself an APIPA address (169.254.x.x / 255.255.0.0) due to there being no DHCP server serving the request for an address. You only posted page 3 of the Network Interface report, so I can't see if there's anything else going on.

I took another look at the configuration page. The 11.22.33.44 that is in bold type for the IP address is what Ricoh setts as an IP address when it cannot find the DHCP server.

[fredsp]

Re: MP 171 Access Control Range

Try this


If WIM is inaccessible:
- Currently configured network-related settings can be printed from the operation panel:
System Settings > Interface Settings > Print List
or
List/Test Print: Network Summary
- Access Control settings can also be checked, configured, and applied via telnet:
1) Access the MFP by telnet
2) Login as administrator
3) At the msh prompt (msh>), type:
access (to display the Access Control settings)
access flush (to remove any configure Access Control Ranges)
4) Logout

[fredsp]

Re: MP 171 Access Control Range

If WIM is inaccessible:
- Currently configured network-related settings can be printed from the operation panel:
System Settings > Interface Settings > Print List
or
List/Test Print: Network Summary
- Access Control settings can also be checked, configured, and applied via telnet:
1) Access the MFP by telnet
2) Login as administrator
3) At the msh prompt (msh>), type:
access (to display the Access Control settings)
access flush (to remove any configure Access Control Ranges)
4) Logout

[mikedci]

Re: MP 171 Access Control Range

Have you tried printing via usb?

Java and/or any programs installed?

user codes turned on?

[slimslob]

Re: MP 171 Access Control Range

If he is able to do a telnet session, IP configuration is OK.

In the original post he said that he tried telnet and could not connect with it either.

[mikedci]

Re: MP 171 Access Control Range

Might also be worth doing a telnet show command and posting the results here for the network experts to view.

once you telnet in the command is just show then you can cut n paste the results...


LANIER Maintenance Shell.
User access verification.
login:admin
Password:
User access verification ... OK.
LANIER MP 5500/LD255
Network Control Service Ver. 5.61
Copyright (C) 1994-2004 Ricoh Co.,Ltd. All rights reserved.
msh> show

also...and I only ask this because you said it was your first telnet session...you did logout y e s to make sure the changes were saved right?

[omorales]

Re: MP 171 Access Control Range

SSL configuration check.
To enter the test WIN (http: // ip) or (https: // ip).

[qbert69]

Re: MP 171 Access Control Range

I have had an instance where HTTPS was enabled and it threw a Diffie-Hellman error....I think it was in firefox....then I used tried to login with HTTPS in Internet Explorer and I was able to get into the WIM.

Good Luck!

[sandmanmac]

Re: MP 171 Access Control Range

also...and I only ask this because you said it was your first telnet session...you did logout y e s to make sure the changes were saved right?

That was It!
Thanks so much for that!
It's a bit embarassing that that was the last step I was missing.
some chnages I made saved but I noticed that "HTTP" wouldn't stay "up", and that's what unlocked it
There was still a ton of other stuff in there was disabled, but i was able to make the changes
I've never run acrooss a machine as LOCKED DOWN as this one!
I never thought there was anything technically wrong with the machine, so I wanted to follow through to learn some stuff even though the machine wasn't mine.

Thanks everyone for their input!

[Iowatech]

Re: MP 171 Access Control Range

I do appreciate the input Gene, but honestly, I don't have a clue what a tracert is or how to break one down.

If you call up a command window in Windows 98 - 10 (maybe even in older versions of Windows but I never tried them), then type tracert followed by an IP address or URL*, then press enter, tracert will "trace" the "route" through the network from your computer to the target, listing up to 30 addresses or URLs that the trace goes through.

It's like a much more verbal version of the ping command.

tracert is my favorite way to see whether a website is down or it's blocked somewhere else. As the internet is kind of like a mesh network (there are multiple paths through the net to almost anything), if the request times out after showing a few jumps either the address isn't connected to anything, or there's bigger problems between here and there. If it times out right away, it is likely my antivirus or something is blocking the site.

* I'm lazy, and usually just copy and paste the URL from the browser address bar or the bookmark/favorite properties.

[slimslob]

Re: MP 171 Access Control Range

If you call up a command window in Windows 98 - 10 (maybe even in older versions of Windows but I never tried them), then type tracert followed by an IP address or URL*, then press enter, tracert will "trace" the "route" through the network from your computer to the target, listing up to 30 addresses or URLs that the trace goes through.

It's like a much more verbal version of the ping command.

tracert is my favorite way to see whether a website is down or it's blocked somewhere else. As the internet is kind of like a mesh network (there are multiple paths through the net to almost anything), if the request times out after showing a few jumps either the address isn't connected to anything, or there's bigger problems between here and there. If it times out right away, it is likely my antivirus or something is blocking the site.

* I'm lazy, and usually just copy and paste the URL from the browser address bar or the bookmark/favorite properties.

When you use tracert, the first IP address returned is the local address of the first gateway. The second is normally ISP's gateway.