Dale Pontius <(E-Mail Removed)> wrote:
> I picked up a flea-market hardware print spooler, but need to find out
> it's IP address before I can get any further. The documentation is
> heavily oriented toward their proprietary software, but there is a web
> server in there, and if I can just connect, I can start from there.
> The lights all light in the correct ways, and the price was right, but
> there is no hardware reset button. I need to get in, in order to do
> anything.
>
> Is there a fast/simple way to discover the IP address of an unknown
> appliance, given the knowledge that it DOES have one?
Sadly, there is no reliable fast way of doing this. I found myself in
your exact same situation with a Dick Smith (rebadged) no-name parallel
port-ethernet print controller that came with a Windows setup program.
(I gave in and just used the windows program to configure it with an
initial address)
My device didn't ship with DHCP enabled (which to my mind is silly, but
seeing as its a consumer device, understandable, as most consumers don't
have the ability to assign static addresses via DHCP).
There are three IP ranges I would scan for. First, make sure your
default route is set to the network in question so all packets will go
out the correct interface. Also check that you don't have any firewall
enabled on your computer.
The ranges are as follows.
192.168.{0,1,254}.0/24 (this is three ranges)
169.254.0.0/16 (this is the zero-conf range, also used for
unconfigured devices)
192.168.0.0/24
172.16.0.0/12
10.0.0.0/8
224.0.0.0/8 (link-local multicast, there is a chance unconfigured
devices may listen to particular multicast addresses)
Scanning this one may be rather difficult, as they're unlikely
to respond to pings, and ICMP port unreachables won't be sent
for UDP on multicast, IIRC.
OK, so its considerably more than three, but these are the ranges I
would scan in order. If you're doing this with nmap, I would suggest you
change the timing to be Aggressive.
And if you do end up falling back to the Windows applet, you might try
sniffing the network to see what its doing.
The reason why there is no easy, fast way to find this is because it
makes it easier for (other) people to map/scan networks.
And of course, sniffing the network as you power on the device may
occasionally be enlightening. Esp if the device has something like
Appletalk enabled (it will send advertisements)
--
Cameron Kerr
(E-Mail Removed) :
http://nzgeeks.org/cameron/
Empowered by Perl!