It works for me. And I just tested this as I was working on an SSH bug. With what client are you seeing this problem? If Windows, make sure you have access to run cmd.exe as well as telnet.exe exists in your path.
The way telnet is executed on Windows is to try and write a topotel.bat file to your home directory on your client. The contents of which will be:
Then that batch file is executed. If that batch file cannot be written, then the following command will be tried:
cmd /k telnet
If the client is Solaris, then the following command will be executed:
xterm -e telnet
You may also see errors in the Java Plug-in console related to this.
We use signed Java applets to invoke commands locally on the client. If you refused this access at one point, that may cause the problem. Go to your Java Plug-in Control Panel, and remove all certificates relating to Cisco. Then, clear out your Cache under the Cache tab. then restart your browser, accept all certs, then see if you can spawn telnet from an applet.
Of course, make sure you test the local commands I sent you previous work when executed manually. As you have observed, the Device Center link simply uses a telnet:// URL where as Campus actually executes commands locally on the client.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...