This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have tried the telnetenable, telnetenable2, and telnetgear utilities, to no avail. The unit just refuses the connection. Also tried port 223. No joy.
10.0.0.1/debug.htm raises a 404.
If I flash to a previous firmware version (and which one?), will the access — or custom settings — "stick" when upgrading back to current?
I could flash with dd-wrt, but on a previous unit I could not get the USB storage/NAS to work in spite of doing everything By The Book. (My shares were visible but inaccessible in Windows' file explorer, and the NAS was completely invisible on my other system on the LAN, so I'd like to stay with the stock firmware if I can.)
I opened a ticket with Netgear support — a week ago. No response at all.
Suggestions re enabling telnet welcome..... TY in advance.
"tried" + "to no avail" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
Which MAC address are you specifying? (You want the LAN-port MAC address.)
> Also tried port 223. No joy.
"tried" _what_ on "port 223"? I wouldn't expect anyone to be listening there.
> 10.0.0.1/debug.htm raises a 404.
Also not amazing. There is one on my D7000 (V1.0.1.64_1.0.1) but it doesn't offer a Telnet-enable function. There is a "Module Debug" page, "/debug_mbm.htm", with an "Enable Telnet Server" control which does nothing obvious, other than leading to a "403 Forbidden" error page. Hence, I use that "nte" program. If nothing else, it provides potentially useful error messages.
pro3$ nte m=50:6A:03:E9:AE:86 n=10.0.0.1 u=admin p=password ! LAN MAC. nte: Received ACK message. Telnet access should be enabled.
pro3$ nte m=50:6A:03:E9:AE:87 n=10.0.0.1 u=admin p=password ! WAN MAC. nte: FAIL. No ACK message received
My apologies. The brevity of my description assumed others had run into the same issue.
Tried means: In PuTTY — the router's current address (10.0.0.1) on Port 23, "Telnet" radio button selected, option for "Close on exit" set to Never Result: Black PuTTY window. Dialogbox errmsg "PuTTY Fatal Error" (titlebar) and "Network error: Connection refused" (Port 223 was suggested by someone elsewhere as an alternative for these routers)
In telnetenable2 — (yes, this is the MAC addy of the router seen from the LAN) telnetenable2 10.0.0.1 04A1512574CA admin [my router pwd] returns "starting ..." "creating pkt..." "sending pkt..." "done." But still can't telnet to router. Same err as above.
In telnetgear.exe — Router local IP, MAC addy, setup login & password, and hit Connect "ERROR 10060: :Connection timed out."
Is there anythying else I can try? And do you know where I can find a Windows version of nte? Thank you.
> [...] do you know where I can find a Windows version of nte?
There's a link on the web page:
NTE 0.5 Executable Kit o Windows executables kit:
If you use the NTE Windows executables which I built, then you may also need to install the appropriate Microsoft Visual C++ 2010 SP1 Redistributable Package. For details, see:
Was there any actual problem with the original link provided here, or the link on that page to the Windows executable kit?
> Run it from the Windows CLI.
As the web page says (and I thought that the README made sufficiently clear), "[...] and has a command-line interface". So, yes, on Windows, you'd want to use a Command Prompt or PowerShell window to run it.
> Solved! [...]
It's always gratifying to see credit given where it's due.
<< I'll bite. "The link wasn't" _what_? >> My eyes aren't good, so I could not find the link to net.exe in the page you referenced in your answer here.
However, I did a query and found your page describing it and links to the makefiles & executables. Thank you for your work.
<< > pass: >Fl1bberdeg1bbet<.
You might want to change that. >> Did. Also changed the admin login name to something random, which is one of the things I wanted to do in the first place.
I am trying to break into my wnr2000v3, but the connection is refused. antinode, will you look at a nte.exe report in PM, or should I open a new topic in that unit's forum?
> I am trying to break into my wnr2000v3, but the connection is refused.
When you did what, exactly? Copy+paste is your friend. I believe that I read that older hardware might use a TCP connection instead of UDP. Some of the other (older) programs out there might do that; mine is UDP-only.
> [...] will you look at a nte.exe report in PM, or should I open a new > topic in that unit's forum?
Either one should work. With a little effort, you could probably deduce my e-mail address, or use the form at antinode.info. If it is a UDP v. TCP problem, then I probably wouldn't care enough to do much about it soon. (It works with all my hardware, so far as I know.)
