Re: Cisci 2811

Soylent · 05-14-2009, 02:48 PM

Quote:

Originally Posted by Cellus

There are two standard methods of accessing the user interface for a Cisco router - direct console connection via serial cable, or via telnet. There is no "web interface" so to speak.

Cisco routers are complex, the interface is pure command-line and somewhat esoteric, and doing anything without knowing what you are doing can wreck things badly. I highly recommend you pick up a manual before you even dare tinkering around with anything. Any book relating to Cisco routers and IOS should be fine - the IOS interface is pretty much universal for all of their routers, so you do not need a book for a specific make or model.

Addendum: Cisco routers are not like your Linksys/D-Link/Netgear baby Home/SOHO routers. Cisco routers are enterprise-grade routers, and approaching them with the same nonchalance as your home router would be a bad idea.

What about enabling the http server? She can just
ip http server
ip http authentication local
no ip http secure-server

Then just browse to the router's ip with internet explorer.

Prometheus_Fire · 07-05-2009, 04:10 AM

Hi Soylent,

Some Cisco devices don't support a web interface. Some you'd access via SDM if you weren't comfortable with the CLI. I personally would strongly recommend gaining some familiarity with the CLI before tackling router configuration.

Cellus advice still applies. Aside from the fact that your commands would allow insecure access to an enterprise level active networking device, just because you have access to a GUI doesn't negate the requirement for routing configuration knowledge.

Even with a web-based GUI, it's still easy to screw up your network config if you don't know what you're doing.

Regards,

Pro

07-05-2009, 04:10 AM	#2 (permalink)
Prometheus_Fire Registered User Join Date: Jan 2007 Posts: 134 OS: Win2K, WinXP, Win Vista, Win2K3, Win2K8, IOS	Re: Cisci 2811 Hi Soylent, Some Cisco devices don't support a web interface. Some you'd access via SDM if you weren't comfortable with the CLI. I personally would strongly recommend gaining some familiarity with the CLI before tackling router configuration. Cellus advice still applies. Aside from the fact that your commands would allow insecure access to an enterprise level active networking device, just because you have access to a GUI doesn't negate the requirement for routing configuration knowledge. Even with a web-based GUI, it's still easy to screw up your network config if you don't know what you're doing. Regards, Pro __________________ Scintillate, scintillate, asteroid minific; Feign do I fathom your nature's specific Exaltedly set on the aether capacious A reasonable facsimile of a gem carbonaceous. Last edited by Prometheus_Fire; 07-05-2009 at 04:14 AM. Reason: One other thing.