Closed GoogleCodeExporter closed 9 years ago
I need more details, did you check with telnet or similar that the host/port
are correct? did you check admin/password authentication?
Original comment by tokland
on 25 Dec 2010 at 3:47
Authentication is correct(I can log into the Advanced Web interface using a
browser), and the service answers to telnet on port 12323
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 4:39
You can try connecting yourself on nazir258.dyndns.org:12323
username: chronkey
pass: tokland
Thanks!
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 4:43
With this info it will be easier to debug, but I cannot connect. The name
resolves to 92.98.178.116, but no connection to port 12323. and nmap shows it
as closed. Can you check your firewall/port redirections?
thanks
Original comment by tokland
on 25 Dec 2010 at 4:52
I can access it from the internet.. Can you try telnet?
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 5:07
The ipaddress it resolves to is correct.. I had issues with chrome and IE, it
only connects with firefox
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 5:08
I tried with firefox and chrome, none worked. nc connected but no respone. With
lynx:
$ lynx nazir258.dyndns.org:12323
Looking up nazir258.dyndns.org first
Looking up nazir258.dyndns.org:12323
Making HTTP connection to nazir258.dyndns.org:12323
Sending HTTP request.
HTTP request sent; waiting for response.
Retrying as HTTP0 request.
Looking up nazir258.dyndns.org:12323
Making HTTP connection to nazir258.dyndns.org:12323
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://nazir258.dyndns.org:12323/'
Alert!: Unable to access document.
All of this connection problems may be the reason the extension does not work.
I can connect to my mldonkey using any browsers (even lynx)
Original comment by tokland
on 25 Dec 2010 at 5:20
does there need to be some configuration to the firewall.. can I disable it for
a while?? Im using the Turnkey vmware appliance..
any suggestions?
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 5:25
The configuration depends on your DSL router, they have usually a "ports and
redirections" tab. To test, you should be able to connect using a proxy (in
case you don't have an external server). For example, I can connect my mldonkey:
http://87.235.142.119:4680/
using this web proxy:
http://kproxy.com/
Original comment by tokland
on 25 Dec 2010 at 5:39
I have a linksys and the ports 12320 thru 12324 are forwarded to my appliance..
I can connect to it over the web using a browser.. not sure what the issue is..
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 5:57
Did you tried to connect through kproxy? I can access my mldonkey but not
yours, so there must some problem (not sure which exactly).
Original comment by tokland
on 25 Dec 2010 at 6:05
kproxy is blocked by my ISP :-(
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 6:07
> kproxy is blocked by my ISP
your ISP blocks webpages? are you from china or something? (just kidding; or
not). You really need an external server/proxy so you can check that port is
open from the outside. Sometimes there are two levels of filtering of incoming
connections, one at the ISP and other at the router.
BTW, nmap reported as open ports only these: 21, 1111, 1112, 2222, 5900, 6881
Original comment by tokland
on 25 Dec 2010 at 6:29
Im from Dubai in the Middle EAst :-)
Sorry.. I think I didn't explain correctly. I use my mobile phone browser,
which is on 3G so outside my NAT and I can connect to the Mldonkey interface.
can you try https://nazir.dyndns.org:1111
Port 1111 maps to 80 on my internal network.
Sorry for the bother..
Original comment by nisark...@gmail.com
on 25 Dec 2010 at 6:43
> can you try https://nazir.dyndns.org:1111
does not connect either:
$ nc -vv nazir.dyndns.org 1111
cannot connect to 222.164.122.4:1111 (cm4.epsilon122.maxonline.com.sg)
Original comment by tokland
on 25 Dec 2010 at 6:49
Original comment by tokland
on 15 Jan 2011 at 12:41
Original issue reported on code.google.com by
nisark...@gmail.com
on 25 Dec 2010 at 10:35