Skip to main content

How to recovery/reset cisco routers password?


I've encounter customer forget their router password when I've got to change their old one with new one after they upgraded their Internet Line.
Then I need to recovery/reset that password because of I need to check current router configuration to configure new router.
OK...below is the steps to recovery/reset the cisco router,


Step 1
Connect your laptop and router by using console port.
Boot the router and interrupt the boot sequence as soon as text appears on the screen by pressing Ctrl and Break keys together.
Step 2
Change the configuration register to ignore contents of NVRAM by keyin "confreg 0x2142"
Step 3
Reload the router by keyin "reset"
Step 4
Enter privileged mode by keyin "enable"
Step 5
Copy startup-config into running-config by keyin "copy start run"
Step 6
Change the password by keyin configure terminal, "username" "password" and "enable secret new password" (put new password that you want to reset in "password" and "new password" places.)
Step 7
Reset configuration register back to default value by keyin "config-register 0x2102"
Step 8
Save the configuration by key in "copy run start"

Now, recovery/reset the router password is successfully done.
Although the above steps are for 1700 and 2600 series router, I've used on other some router and still can use.
If you want to know in more detail for this, please go through cisco website and check.
Here I've take sample screen-shots done with Cisco 1841 router for your reference.












May you all be happy.
(Be knowledgeable, pass it on then)


Comments


  1. Thank you so much for sharing this worth while to spent time on. You are running a really awesome blog. Keep up this good work

    HP Officejet 4650 Wireless Setup

    ReplyDelete
  2. i faced this problem many time and always confused how to reset or recover password, but you helped me out, thanks for solution, now Router Configuration is very easy for me

    ReplyDelete
  3. I deleted my automobile decomp because they're problematic as you mentioned. Also make certain you update your intake boot to the design with the alloy clamp. The plastic consumption clamps have a reputation for loosening and causing an air flow that will burn off the Saw down. Last, there's an noodle update kit to your carburetor in case you've obtained the Walbro. In case you've got the Zama carbohydrate I think you're fine.
    Chainsaw Sharpeners Chainsaw Sharpeners

    ReplyDelete
  4. Nice Information , Thanks For The Great Content

    Get started to Install, Setup, Connect, Print from your 123 hp setup printers. Easy to Download driver & Printer software from HP Envy,HP Officejet,HP Officejet Pro,HP Deskjet Printer Setup Driver Installation

    For More Support

    123.hp.com/Setup|123hp com/oj8049|123.hp.com/oj3830|123.hp.com/oj4650 | 123.hp.com/Setup ojpro|ojpro6968|
    ojpro6970|123.hp.com/ojpro6968|123.hp.com/ojpro6970|123.hp.com/ojpro6978|123.hp.com/ojpro8600|123.hp.com/ojpro8710|123.hp.com/ojpro8720

    ReplyDelete

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, S