3300 Locked out of Telnet access

[MontanaTed]

We have a 3300 and normally get access to it through the GUI. I recently figured out we could telnet in with the default usernames and passwords. Since this is a security hole I wanted to change the telnet usernames and passwords to match the GUI usernames and passwords. I telnetted in under the "system" username and used RESEt Usernames to change system, install, maint1, and maint2. Now I'm locked out of telnet, it won't let me in with the default password or the password for the account I can log in to through the GUI. I can still get in through GUI no problem.

How can I fix?

 

[Webmany]

It sounds like you were telnetting into the call control in the 3300, which is based on a SX2000. This is considered a no-no.

Try installer and sx2000

 

[MontanaTed]

Yes, I wasn't aware it was a no-no to do that. I was assuming it worked the same as the SX-2000. I've changed usernames and passwords on the SX-2000 several times and never had an issue. installer/sx2000 did not work, any other ideas?

 

[paterson]

Blow it away, install new software, and restore your backup. You did do a backup before making these changes didn't you?

 

[MontanaTed]

Yeah a backup, that probably would have been a smart thing to do.... Doh!

 

[Lundah]

If you simply perform a backup and restore from the ESM (web) interface, the system-level telnet username & password is reset to the default values.

 

[MontanaTed]

Thanks Lundah. So assuming all goes well and I get the default usernames and passwords back, we're supposed to just leave them as is?

 

[Lundah]

Only the system-level is reset, the rest will remain whatever they were. But system allows you to change the rest.

It's definitely good practice to change them, but be sure to record them somewhere so this doesn't happen again.

 

[MontanaTed]

Well that's what got me into this mess (logging in as system and changing the rest). I was changing them for better security. I wasn't aware that telnetting in was a no-no. Still not sure why, I've been telnetting into our sx2000 for years to do everything and never had a problem.

 

[Lundah]

The reason it's not recommended is if you make a change via telnet while someone else is editing the same form via ESM, you can corrupt the database.