Unable to telnet after upgrade to 7.0 3

[Gem257]

Prior to our switch being upgraded to 7.0 I could telnet through Procomm to our sig server and receive the "cslogin" prompt and work through CLI when I needed. We were at 5.0 before the upgrade.

Now I don't get a response from the same IP address anymore. I've tried procomm, PuTTy, and Hyperterm. The IP addresses haven't changed. I'm guessing this has to do with the introduction of the UCM server and the role it plays. I'll be searching NTPs after I post this.

Anyone have any ideas?

 

[janaya]

I think you have to use an ssh connection when connecting to the system at 7.0. We are putting one in soon, but the ones that I have seen all use the ssh connection over secure crt.

 

[Gem257]

Thanks, I'll look into SSH to connect and see what happens.

 

[Tman45]

Nortel should have shut down telnet anyway as SSH is the 'new' way to go. SSH was added by default in 5.0 (maybe earlier) - you have to do a keygen before it becomes active and usable (just in case you can't SSH either). We don't have 7.0 so I am not aware of the 'no telnet' issue. You won't be able to use Procomm anymore because it can't do SSH, but you can use PuTTY or secure crt as mentioned (or a handfull of other apps - like ZOC and WRQ reflections if you need more functionality).

 

[Wane47]

i havn't seen rls 7 but on rls 6 telnet was turned off by default. On rls 6 you could login to signaling server and turn it back on by typing "harden on" " harden off" would turn it back off.

 

[guycable2]

actually you can use the commands

harden telnet on
harden telnet off

when logged into the sig server to turn telnet on or off

works in 6.0 or 7.0

 

[Gem257]

Thanks to all of you. PuTTy with SSH works great, I'll just have to bid procomm plus farewell for accessing this site.