Open GoogleCodeExporter opened 9 years ago
are you connecting via local ip? eg. 192.168.x.x? or hostname eg. nas?
or remote ip or a dyndns hostname? if remotely you need to make sure port 23 is
enabled on your router.
Ted
Original comment by ted.cho...@gmail.com
on 11 Apr 2011 at 3:48
I'm using dyndns hostname remotely, I left the ip In the DMZ. I Torrent access
and administration normally, but do not have Telnet remote access. Locally,
even using the dyndns works normally. Thanks Ted for your attention.
Original comment by neuronio...@gmail.com
on 13 Apr 2011 at 1:53
since you are using remote hostname, first try telnet locally, via ur ip, eg.
192.168.1.1, and if that works, its then a internet connection problem.
If telnnet to 192.168.1.1 works succesfully, go to this page:
http://www.dyndns.com/support/tools/openport.html
and test ur port 23, post your response here; for telnet to connect right, the
result should be:
72.208.x.x:23 is open and accepting connections. This indicates the port is not
being blocked by either a firewall or your ISP and is currently operational.
Goodluck!
Ted
Original comment by ted.cho...@gmail.com
on 14 Apr 2011 at 4:02
Oh, btw, I had a look at your image, and saw it's INET and username thing, that
is not correct, I think you are not even connected to the right machine, that's
probably router, so please do try connecting locallly via your local 192... ip
address. If you can't even connect that way, there's no way you can ever get
remote dyndns to work at all.
Attached is how it should look like. nas is your machine host name
Original comment by ted.cho...@gmail.com
on 14 Apr 2011 at 6:37
Attachments:
Guys, I discovered that unfortunately the firewall of my company is blocking
the connection ... I tried using ssh online, which works only with the passage
of time it is locked.
Do you have a web how to install ssh on the NAS? Using his own webserver?
I'm trying but I can not! LOL
I'm reading about Anyterm (http://anyterm.org/1.0/install.html), we'll see.
Thank you to everyone who responded!
Ps.: To run ssh, I had to create a rule to forward port 9001 to 22.
Ex 189.174.34.17:9001 to 192.168.1.100:22
Original comment by neuronio...@gmail.com
on 27 Apr 2011 at 12:17
Original issue reported on code.google.com by
neuronio...@gmail.com
on 23 Mar 2011 at 2:11Attachments: