Edit:I am running windows 7, 64 bits.
I have Telnet Client installed, and if I go to c:\windows\system32 i do find the file "telnet.exe"; if I click it, telnet runs perfectly.
However, if I type telnet in cmd prompt, it gives me the "command not recognized" message.
I think it's because c:\windows\system32\cmd.exe is actually running files from windows\sysWOW64 (which also has a cmd.exe), and so I tried copying telnet.exe to this folder; When I type telnet in the cmd line (regardless of which cmd.exe i use) I no longer get an error message, and instead get... well, nothing. It just sits there, like when awaiting input, but if I type something (e.g., "quit") it once again does nothing and awaits input.
Finally, I tried, in windows\sysWOW64, deleting telnet.exe, creating a telnet.lnk shortcut to telnet.exe in system32, and creating a telnet.bat file in windows\sysWOW64, that runs telnet.lnk. Now, if I double click telnet.bat, telnet start perfectly (in a system32\cmd.exe window); if I type telnet in cmd prompt (again, doesn't matter which) it runs telnet.bat whith no problems at all (checked this testing other commands), but returns "Acess denied" when opening Telnet.lnk.
So,
-- telnet is installed and runs when double clicking
-- shortcuts to it work perfectly if double clicked
-- neither telnet nor shortcuts (nor files calling shortcuts) can be run from either cmd prompt.
And that is how far i've gone. So, yeah... Any ideas?
where telnet.exe
say? I just enabled the Telnet Client under Windows Features. Telnet.exe, a 64-bit program, was duly added to Windows\System32. No 32-bit version was to be found in Windows\SysWOW64. Typingtelnet
at the cmd prompt worked perfectly as expected. Don't know what the problem is at your end.