Jim Phillips wrote:
> Wirt Atmar <[log in to unmask]> writes:

> > To find out if your printer does support HTTP, simply type on your
> browser:
> >
> >            http://192.168.1.100
> >
> > (or whatever the address of your printer is). If it doesn't
> > support HTTP, it will tell you. If it doesn't, telnet into the
> > printer using your favorite terminal emulator. Virtually all
> > network capable printers support telnet administration.
>
> No http, but they do support telnet.  But, how do I know if an NAT
> is setup in the router or not?  We don't do the router stuff, MCI
> handles that for us.  FWIW, if I telnet into the router it asks for
> a password, which I do not have.

My my, you are a trusting soul.  <cisco-bias> I would insist on read
only telnet access and/or the read community string.  As it stands, you
cannot validate the status of your line (is it really down on your end,
or is MCI throwing you a line?  Are you dropping packets?  How many?
What's the error rate?  If it's frame relay, how many burst packets are
getting zapped?  How often?  Are you getting the CIR you are paying
for?).  As for http, the router can do that too with the proper version
and configuration.  Where is NAT?  You *should* know!
Is it dynamic?  Static?  A combination?  Is it overloading a pool?
Typically you do the NAT, although I could also buy into MCI giving you
RFC1918 addresses and using an unnumbered serial port to get to them,
but I would doubt they want to offload the NAT overhead to their border
router [that would be hideous]).  </cisco-bias>

You would be surprised what your upstream provider won't tell you.

Jeff Kell <[log in to unmask]>