At first, I had issues because Windows 7 doesn't install the Telnet client by default (also, SuperUser has a thread). So, after installing it (and restarting, like Windows asked, though completely unnecessary), I opened a command prompt, and went to run my new Telnet program.
I enter telnet, and receive:
C:\Users\[USER]>telnet 'telnet' is not recognized as an internal or external command, operable program or batch file.
"That's odd," I think to myself. So, in Windows explorer, I navigate to \Windows\System32 and see telnet.exe sitting in that folder. If I double-click on the executable file, the Telnet command prompt opens for me without a problem. So, I return to my Windows Command Prompt, and enter:
C:\Users\[USER]>\Windows\System32\telnet.exe '\Windows\System32\telnet.exe' is not recognized as an internal or external command, operable program or batch file.
And then (
grep comes from cygwin):
C:\Users\ryan\Desktop>dir \Windows\System32 | grep telnet
I've disabled UAC and have no idea why my Command Prompt is lying to me. Anyone experience something similar?
Also, I've found that I can create a Windows shortcut to telnet, which will point to the right file and successfully open the Telnet prompt.
To recap: In Windows 7, I have installed Telnet and can see it in my System32 folder, but cannot run it via a Command Prompt.