TransWikia.com

Windows preventing running of Telnet client

Super User Asked by palswim on January 7, 2021

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 WindowsSystem32 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]>WindowsSystem32telnet.exe
'WindowsSystem32telnet.exe' is not recognized as an internal or external command,
operable program or batch file.

And then (grep comes from cygwin):

C:UsersryanDesktop>dir WindowsSystem32 | 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.

3 Answers

I no longer have this problem. Whether Microsoft fixed something or I did something, I don't know. If I encounter it again, I will re-open this question.

Correct answer by palswim on January 7, 2021

go to registry key HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Options, then create a new key named telnet.exe, then create a string value named Debugger and set value to Block.

Answered by Wasif Hasan on January 7, 2021

At the moment you think you put it in c:windowssystem32

and you are having trouble running it from the command prompt.

forget the path environment variable for now. You have a weirder problem that you can't seem to even run it directly.

A good thing to do then, is Go to windowssystem32
C:>CD WindowsSystem32
C:WindowsSystem32>telnet any luck? probably not Make a directory C:blah

Open windows explorer. Copy telnet.exe to that directory

Open a command prompt

C:>CD Blah
C:Blah>Dir

See if it lists telnet there

Try dir /a Does it list it now?

Try c:blah>attrib

That should list files a bit like dir, but showing attributes.

If you manage to put it somewhere where you can see it in the command prompt, then copy it to a few toy directories, and eventually into c:windowssystem32 and wipe your brow.. and try to figure out what's going on or what happened!

I don't have windows 7, but See if this happens for any other EXE files.. or is it just telnet.exe maybe windows 7 is playing games with that one exe file. If it is you should be able to find out! If you copy files into the directory, do you find the command prompt shows the others but not telnet.exe? make it a directory of your creation without much in it, so you can see what you're doing.

Answered by barlop on January 7, 2021

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP