NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
enable telnet on R6300v2
Model R6300v2, stock firmware V1.0.4.24_10.0.87. OS: Win7/64 on my desktop. I'm trying to get telnet access to the router. I have tried the telnetenable, telnetenable2, and telnetgear utili...
For others:
http://www.antinode.info/nte/index.html
Download & extract nte-05/nte-05_win.zip
Run it from the Windows CLI.
Apologies. The link wasn't. However, I did find your exefile and ran it, with this result:
debug: 0xffffffff .
MAC0: >04A1512574CA<.
MAC1: >04A1512574CA<.
user: >admin<.
pass: >Fl1bberdeg1bbet<.
getaddrinfo():
ai_family = 2, ai_socktype = 0, ai_protocol = 17
ai_addrlen = 16, ai_addr->sa_family = 2.
ai_flags = 0x00000004.
ai_addr->sa_data[ 2: 5] = 10.0.0.1
dns_resolve() sts = 0.
sock = 128, FD_SETSIZE = 64,
FD_ISSET( sock, &fds_rec) = 1.
pre-select(1). sock = 128.
pre-recvfrom(). sock = 128.
recvfrom() bc = 3.
s_addr: 0100000a .
recvfrom() addr: 10.0.0.1
41 43 4b ACK
nte: Received ACK message. Telnet access should be enabled.
pre-select(1). sock = 128.
select(1) sts = 0.
AND THAT GOT ME IN. THANK YOU! Have the # prompt and "nvram show" tells me what I need.
For others:
http://www.antinode.info/nte/index.html
Download & extract nte-05/nte-05_win.zip
Run it from the Windows CLI.
> Apologies. The link wasn't. [...]
I'll bite. "The link wasn't" _what_?
> pass: >Fl1bberdeg1bbet<.
You might want to change that.
> For others:
> [...]
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.)