+ Reply to Thread
Results 1 to 10 of 10

Thread: 0x2104

  1. Senior Member flipmad's Avatar
    Join Date
    Jan 2008
    Posts
    186
    #1

    Default 0x2104

    I have a 1721 router here that the register is set to 0x2104, but it is currently password protected. When I power it up and try a CRTL-BREAK I am not getting prompted to ROMMON mode to clear the password or change the confreg.

    Any ideas?
    Reply With Quote Quote  

  2. SS -->
  3. Senior Member flipmad's Avatar
    Join Date
    Jan 2008
    Posts
    186
    #2
    I was actually able to crack the password. but in this situation what would have been the fix? I looked around but I couldnt find anything?
    Reply With Quote Quote  

  4. Senior Member flipmad's Avatar
    Join Date
    Jan 2008
    Posts
    186
    #3
    The sh ver shows
    Configuration register is 0x2102

    But i am now getting an error message

    Mar 1 00:10:47.183: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (t
    ftp://255.255.255.255/hami-1-confg) failed

    wtf?
    Reply With Quote Quote  

  5. Senior Member flipmad's Avatar
    Join Date
    Jan 2008
    Posts
    186
    #4
    i just did a wri erase and now im not getting the error messages. The config-reg is good. I need to do a little more resaech. Just thought i'd see if any of you encountered this issue before
    Reply With Quote Quote  

  6. Network Dummy
    Join Date
    Feb 2008
    Posts
    41

    Certifications
    A+, Net+, CCNA, CCNP, CCIE #22769
    #5

    Default Re: 0x2104

    Quote Originally Posted by blake15
    I have a 1721 router here that the register is set to 0x2104, but it is currently password protected. When I power it up and try a CRTL-BREAK I am not getting prompted to ROMMON mode to clear the password or change the confreg.

    Any ideas?
    Did you mean to set the value to 2142 and not 2104?
    Reply With Quote Quote  

  7. Senior Member flipmad's Avatar
    Join Date
    Jan 2008
    Posts
    186
    #6
    No 0x2142 is the password break to bypass the startup config.

    It was in 0x2104 and I was getting the above. I was able to figure out the password because it was an old router of ours and able to change it back to 0x2102, so essentially 0x2142 was not needed.

    But for it to be initially in 0x2104, it is still password protected and it will not allow me to CTRL+BREAK and I was getting all sorts of crazy messages
    Reply With Quote Quote  

  8. was here.
    Join Date
    Apr 2008
    Posts
    4,504
    #7
    0x2104 is netboot. Break doesn't work because the flag to disable it is on.
    Reply With Quote Quote  

  9. ...loading... gorebrush's Avatar
    Join Date
    Apr 2005
    Location
    UK
    Posts
    2,728

    Certifications
    CCIE:R&S, CCNP:R&S, CCNA:S, MCSE, MCSA:M, MCTSx2
    #8
    Normal = 2102
    Reply With Quote Quote  

  10. Village Idiot dtlokee's Avatar
    Join Date
    Mar 2007
    Location
    NJ
    Posts
    2,389

    Certifications
    CCIE #19991 R+S, CCNA, CCNP, CCIP, CCVP, CCSP, CCSI, MCSE NT4.0, 2000, 2003, + Messaging and Security, MCDBA, MCSD, MCAD
    #9
    The "crazy messages" were from autoinstall trying to get a configuration.
    Reply With Quote Quote  

  11. Senior Member flipmad's Avatar
    Join Date
    Jan 2008
    Posts
    186
    #10
    So my question is, if it was set to 0x2104 and we did not know the password to the box. The CTRL+BREAK is disabled, how do i change it back to 0x2102 or 0x2142. I just so happened to be able to use several password combinations and get into the box, but if I wouldnt have, then I would have been locked out?
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks