Unable to connect to my local server using dynamic dns name

[tgp1994]

Hi everyone.

I've been having weird experiences with my 2wire 3801HGV. It seems like, with some services, it doesn't allow local computers to connect to others using an outside IP (or in this case, domain name).

I have just updated my dynamic DNS, and yet, when I try to connect to my TF2 server hosted by a Windows Server 2003 machine, my client refuses to connect. This occurs when either using my outside IP or domain name.

I can still connect using the server's internal IP, although I still want my friends to be able to connect, and I have this theory where steam friends won't recognize the outside IP unless I actually connect with it.

Does anyone know what's at fault here? Is it my residential gateway? The firewall service isn't even on in the server.

P.S. None of the residential gateway's logs show anything suspicious.

Update: After following the solution found here, I was able to get my server to show up on the master server list, and when I view the info of it, it shows my external ip (very good!) although it shows up as not responding, and I cannot use the join button.

Update 2: I realized I completely forgot to mention my forwarded ports I have ports 27000 through 27040, both on TCP and UDP forwarded.

[realchamp]

You cannot access your own server with the external IP. Unless you have loopback enabled.

[tgp1994]

(02-06-2011, 04:28 AM)realchamp Wrote:  You cannot access your own server with the external IP. Unless you have loopback enabled.

Why would that not work? It should eventually find out that the outside IP leads to that server, then connect like it normally would.

And anyways, this used to work with my old DD-WRT Linksys router.

[realchamp]

(02-06-2011, 04:40 AM)tgp1994 Wrote:  

(02-06-2011, 04:28 AM)realchamp Wrote:  You cannot access your own server with the external IP. Unless you have loopback enabled.

Why would that not work? It should eventually find out that the outside IP leads to that server, then connect like it normally would.

And anyways, this used to work with my old DD-WRT Linksys router.

You will not be able to connect with your own external ip address, unless your router supports loopback.

[tgp1994]

(02-06-2011, 04:41 AM)realchamp Wrote:  You will not be able to connect with your own external ip address, unless your router supports loopback.

I'm pretty sure it does, in one form or another. I.E. I can still connect to my TeamSpeak3 local server using my external IP. But anyhow, it seems like the issue was fixed by restarting the modem.

[RichardAPerez]

so it worked? did you do as realchamp said?

[tgp1994]

(02-06-2011, 07:42 AM)RichardAPerez Wrote:  so it worked? did you do as realchamp said?

Well, realchamp didn't really give me much to do Not that there was much to do, either the residential gateway supported loopback or it didn't. But it looks like it does, when it wants to.

So I'd say that 2wire RGs are bad, and this is partially fixed.

[a7m1]

(02-06-2011, 09:40 AM)tgp1994 Wrote:  

(02-06-2011, 07:42 AM)RichardAPerez Wrote:  so it worked? did you do as realchamp said?

Well, realchamp didn't really give me much to do Not that there was much to do, either the residential gateway supported loopback or it didn't. But it looks like it does, when it wants to.

So I'd say that 2wire RGs are bad, and this is partially fixed.

first time i listen to the loopback defenation
my linksys wag54g v2 5years old router support that
i have readed once it's not good idea to connect to ur external ip

[tgp1994]

Linksys4Lief.

(02-09-2011, 11:24 AM)a7m1 Wrote:  i have readed once it's not good idea to connect to ur external ip

Any reasona why connecting with your external ip is bad?

[realchamp]

(02-09-2011, 12:37 PM)tgp1994 Wrote:  Linksys4Lief.

(02-09-2011, 11:24 AM)a7m1 Wrote:  i have readed once it's not good idea to connect to ur external ip

Any reasona why connecting with your external ip is bad?

Higher latency. Because all your server trafic has to go out to your ISP and back, instead of just to your router and back

[tgp1994]

(02-10-2011, 12:49 AM)realchamp Wrote:  

(02-09-2011, 12:37 PM)tgp1994 Wrote:  Linksys4Lief.

(02-09-2011, 11:24 AM)a7m1 Wrote:  i have readed once it's not good idea to connect to ur external ip

Any reasona why connecting with your external ip is bad?

Higher latency. Because all your server trafic has to go out to your ISP and back, instead of just to your router and back

Really? I'm not so sure about that, I'm pretty sure the router its self should realize that I'm trying to connect to my own network (that's the idea of loopback after all, right?) I also still get blazing (like LAN speeds) when downloading maps from my own server. Ping doesn't seem any different, either. (Also, running a traceroute only seems to require going to the residential gateway (I'll try to keep that synonymous to router).)