2
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
Nothing.
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.
more info on that here http://superuser.com/questions/110760/why-isnt-telnet-enabled-by-default-in-windows-7
– Kara Marfia – 2010-10-14T22:07:35.480Maybe my answer is late, but this has to do with 64bit operating system. I can guess you are having 64 bit of windows 7. What was going on, that in order to support 64 bit and 32 bit side by side, windows created something called "virtual directory" I don't know the details about it, but what I know that you can find stuff in explorer window, but you cannot find it in CMD window. and the reason is , on 64, some stuff are stored in another directory, and all 64 bit programs are able to see a virtual version of "system32" which combine the real system32 and the other directory, where old program – None – 2012-01-17T21:04:44.913