It's not how you survive the storm, but how you dance in the rain...
Lori Cook wrote:
To spawn Remote Desktop, the string passed into the method below is "mstsc.exe /f /v:", "ip_address" set to the IP address of the system and "additional" is empty.
To spawn Telnet, the string passed into the method below is "telnet.exe ", "ip_address" set to the IP address of the system and "additional" is the port desired.
It's not how you survive the storm, but how you dance in the rain...
Lori Cook wrote:Printed out the buffer for the two invocations. The IP address/port removed to protect the innocent. Quotes added around the copy/paste of data.
Telnet invocation: "telnet.exe <address> <port>"
Remote desktop invocation: "mstsc.exe /f /v:<address>"
Took the telnet invocation and pasted into the Search programs and files field of the Start menu and...Got a telnet window/connection.
So...blanks are in the proper place for both invocations. One requires a port, hence the additional field. And either invocation pasted into the Search programs and files field works.
Lori Cook wrote:So...blanks are in the proper place for both invocations.
Lori Cook wrote:Any help appreciated...
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
It's not how you survive the storm, but how you dance in the rain...
It's not how you survive the storm, but how you dance in the rain...
Lori Cook wrote:Final analysis - you cannot launch telnet within another program, batch file, etc. on Windows 7 (and Vista?). The Windows Security will not let you do it. You have to use some other application or interface to do telnet.
The only time you can run telnet is from within a Windows command window and/or from the Run field of the Startup Menu.
Sigh.
My solution - run a batch file that spawns off a PuTTY telnet session.
Don't get me started about those stupid light bulbs. |