Ports Forwarded/Firewall Gone, Outsiders still can't connect
Ports Forwarded/Firewall Gone, Outsiders still can't connect
The thread title is pretty self-explanatory. I've done what the FAQ said and configured my router to forward all ports from 6667 to 8067 to the approriate box. I even completely removed my firewall, and I'm still the only one who can connect.
Any answers for this one? (Server is nightscape.dyndns.org:6667, if it helps any.)
Any answers for this one? (Server is nightscape.dyndns.org:6667, if it helps any.)
Bricker, I fixed my dyndns yesterday. Let me clairfy what exactly the problem is:
I have removed my firewall and forwarded port 6667 to the correct box as it insructed in the FAQ, and I can only connect internally through the address 10.117.11.69. No connection can be made to the external address, 65.255.130.101 (which nightscape.dyndns.org points to).
So, with firewalls not being an issue, and he ports properly forwarded, can anyone tell me why it still won't take an external connection?
I have removed my firewall and forwarded port 6667 to the correct box as it insructed in the FAQ, and I can only connect internally through the address 10.117.11.69. No connection can be made to the external address, 65.255.130.101 (which nightscape.dyndns.org points to).
So, with firewalls not being an issue, and he ports properly forwarded, can anyone tell me why it still won't take an external connection?
Contact your ISP.
Something's terribly wrong with the route to your IP.
There appears to be some sort of loop (test it with a traceroute: http://www.dnsstuff.com/tools/tracert.c ... 55.130.101 )
Something like:
16 65_255_159_2.class_c.mna.cvalley.net [65.255.159.2]
17 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
18 huntsville1.charitonvalley.com [208.218.32.105]
19 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
20 huntsville1.charitonvalley.com [208.218.32.105]
21 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
22 huntsville1.charitonvalley.com [208.218.32.105]
23 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
24 huntsville1.charitonvalley.com [208.218.32.105]
25 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
26 huntsville1.charitonvalley.com [208.218.32.105]
27 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
28 huntsville1.charitonvalley.com [208.218.32.105]
and on and on... you get the idea...
Something's terribly wrong with the route to your IP.
There appears to be some sort of loop (test it with a traceroute: http://www.dnsstuff.com/tools/tracert.c ... 55.130.101 )
Something like:
16 65_255_159_2.class_c.mna.cvalley.net [65.255.159.2]
17 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
18 huntsville1.charitonvalley.com [208.218.32.105]
19 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
20 huntsville1.charitonvalley.com [208.218.32.105]
21 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
22 huntsville1.charitonvalley.com [208.218.32.105]
23 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
24 huntsville1.charitonvalley.com [208.218.32.105]
25 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
26 huntsville1.charitonvalley.com [208.218.32.105]
27 208_218_32_114.class_c.uunet.cvalley.net [208.218.32.114]
28 huntsville1.charitonvalley.com [208.218.32.105]
and on and on... you get the idea...
If you don't make mistakes, you aren't really trying.
- Coleman Hawkins
- Coleman Hawkins