This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
There is a problem I am running into that I wanted to debug using TELNET and nvram show commands to see what has gotten hosed, but to my surprise:
C:\WINDOWS\system32>telnet 192.168.1.1 Connecting To 192.168.1.1...Could not open connection to the host, on port 23: Connect failed
On my old RBR50, I could enable TELNET on http://192.168.1.1/debug.htm, then telnet to it, and use nvrom show/set/commit to fix certain issues. Now I can't?? I don't see the telnet checkbox on the debug page... Hrmpf.
Tuna
PS: I will post about my actual problem separately. Didn't want to mix issues in one post.
That's very unfortunate. I understand that some customers without proper knowledge & skillset could go into their router and screw it up, but given that the firmware is not bug free, this takes away the ability to use telnet not only from customers who know what they are doing, but also reduces the tech support over the phone to a "reset your device" or "here is your refund, we'll send you another one" (i.e. software-reset vs. hardware-reset) by taking away a tool they could have used to support the customer.
I believe the reason NG is removing Telnet from there product is for security reasons as Telnet is insecure. There maybe a future alternative however I have no idea if or when that may come about.
