| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 41073 | 2003-12-29 09:00:00 | Is my router blocking connections from itself? | Chilling_Silently (228) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 204001 | 2003-12-29 09:00:00 | Greetings. Ive had a no-ip.com account since long before I got ADSL. Its worked great with Windows XP forwarding all traffic on certain ports (namely 21, 22, and 80) to my PC when it dials in. People then connect fine using the No-ip.com account Ive setup. I could connect to Username.no-ip.com fine, without a worry... Now that Im on ADSL, it appears that my router is blocking connections from itself. Ergo, I cannot ssh into username.no-ip.com I can ssh into localhost, or ssh into 192.168.0.2 (My LAN IP) without a problem. This becomes rather annoying when I want to test if a service is running and available to the world, or now that I am hosting a Jabber server and want to connect to myself (I can only use an external connection type). Is there a particular setting that I should look for that could be causing this? Im not too sure of the specifics of my router, but its based on the Connexant Chipset AFAIK, and is an "epic-router", I'm looking into the specifics for a model now... I just want to be able to connect to myself, or is it something that the whole world of ADSL experience? Cheers Chill. |
Chilling_Silently (228) | ||
| 204002 | 2003-12-29 09:38:00 | Though I dont know about your set up, I had a similar problem with dyndns.org when using their dynamic dns service. It worked well on dial up and I was able to test the ftp site I set up, but with a Dynalink router I couldnt connect to myself for test purposes, but others could. So I gave up on it. | Terry Porritt (14) | ||
| 204003 | 2003-12-29 09:54:00 | Two things I'm not sure of: 1) Is the ip address for username.no-ip.com different to that of the ADSL modem? Eg. username.no-ip.com -> 203.110.243.120 adsl modem -> 202.100.66.205 2) Where are you trying to ssh from when accessing username.no-ip.com? From the internal network or on an outside computer? If its from the internal network your router/firewall's NAT readdressing will screw up connecting to dns entries pointing to your external ip address. You would have to set up an internal dns server or add a line to your hosts file that points to your internal computer for it to work correctly. Just a thought but I don't understand the problem entirely but given some more details it should be a bit clearer.... |
paintbuoy (3087) | ||
| 204004 | 2003-12-29 10:26:00 | > Two things I'm not sure of: > > 1) Is the ip address for username.no-ip.com different > to that of the ADSL modem? > Eg. username.no-ip.com - > 203.110.243.120 > adsl modem - > 202.100.66.205 Its not a problem with the no-ip.com account though. How do I know this? I ftp and ssh into my home PC from work fine, Ive had people visit my website (checked in the log files), and Ive just had two users test out my Jabber server and its fine! > 2) Where are you trying to ssh from when accessing > username.no-ip.com? > From the internal network or on an outside computer? Im trying it from an Internal network, connecting through the internet, so basically here's what should happen: Connection from my PC to router from router to isp's dns isp's dns back to my router my router to my PC Only it doesnt.. Works fine for me when the connection is not originating from my current IP Address... > If its from the internal network your > router/firewall's NAT readdressing will screw up > connecting to dns entries pointing to your external > ip address. You would have to set up an internal dns > server or add a line to your hosts file that points > to your internal computer for it to work correctly. So I need to play around with the NAT settings then on the router? It currently is setup to forward dns servers, but xtra's alien and terminator dns servers are default on all PC's... > Just a thought but I don't understand the problem > entirely but given some more details it should be a > bit clearer.... Hope that helps, and thanks for pointing me in the direction of NAT :-) Cheers Chill. |
Chilling_Silently (228) | ||
| 204005 | 2003-12-29 10:41:00 | I think that most people just put an entry in their hosts file so that blah.no-ip.com will point to 192.168.x.x or whatever you're using. | -=JM=- (16) | ||
| 204006 | 2003-12-29 10:57:00 | That's a brilliant idea JM, and its worked and Jabber has accepted it too! Jabberd was listening for connections to "username.no-ip.com" and wouldnt accept them if they were to "localhost" if it wasnt listening specifically for connections to "localhost" It works though, many thanks! Chill. |
Chilling_Silently (228) | ||
| 204007 | 2003-12-29 19:38:00 | I know my setup is completely different (direct connection to the internet, not via a network), but when I point my browser, etc to http://[myipaddress], my system loads it straight off my computer, recognising the fact that the specific IP has been assigned to my computer. I'd assume that with a No-IP account it'd have to go and do a DNS lookup first, but upon discovering the IP belongs in your network, should it not try to load it straight off the network? |
agent (30) | ||
| 204008 | 2003-12-29 20:32:00 | What you will find happening is that your router is set to accept incoming connections on port X and transfer them to machine Y, however, your router only uses this rule on the WAN (as that's the big bad net), it doesn't apply the same settings to the Lan. What happens when you try connecting is that your machine gets the IP from a dns lookup, then it goes finds the server with that IP. Your router is saying "Hey that's me!" and so your machine is sending it the packets on port X, but the router doesn't have the service available on port X so the response is the router just drops them! Is that simple or what!? |
cyberchuck (173) | ||
| 204009 | 2003-12-29 20:44:00 | Networking 101: Direct access to the Internet is a completely different ballgame than when accessing via an internal router. When directly connected to the Internet your ip will be 203.12.100.12 (for example). no-ip.com will be translating your domain name to your machines ip address (ie 203.12.100.12). Typically your computer also accepts 127.0.0.1 or Localhost as pointers to your network card also but thats a different story. Hence user.no-ip.com, 203.12.100.12, 127.0.0.1 or Localhost will send you back to your computer. When you are accessing the Internet via an internal network your computer's ip will be something like 192.168.1.3, but the routers external ip will be 203.12.100.12 (for example). A request to the outside world will go like this: 192.168.1.3 -> 192.168.1.1 (Default Gateway) -> Internet -> 203.12.100.12 (Your network's external ip address) -> (NAT Translation) -> 192.168.1.3 Now if you are trying to access your domain name from within the internal network (on the assumption you are talking to yourself) you run into a problem because in actual fact you are talking to your router/firewall at 203.12.100.12, not your personal computer which resides off it. The work around is to use a hosts file or internal DNS server to route requests to user.no-ip.com to 192.168.1.3, rather than 203.12.100.12 I hope that clears things up maybe. To start with it seems clumsy but once you get used to it its really simple. |
paintbuoy (3087) | ||
| 204010 | 2003-12-29 22:25:00 | Some routers are clever enough to have manual hosts specification in them (Mines not one) so you can set things like that up at the router as opposed to each PC! | Chilling_Silently (228) | ||
| 1 | |||||