Hi all,

 

Sorry if this has been covered somewhere. 

 

I have a L4D server on my LAN, which is connectable via WAN using my
external IP address, and also by using a DNS forwarded address of
this.domain.com. External clients can connect to it no problems via either
the IP or domain name, and I can connect to it ONLY via my internal IP of
192.168.1.50.


To remedy this, I set up a Static DNS of "this.domain.com" to point to
192.168.1.50 in my router. This works fine, so on my LAN I can type "connect
this.domain.com" from the console with no problems at all, but when I
"mm_dedicated_force_servers this.domain.com" it doesn't work - It just times
out. 


Does anyone know why this is? I have a Dynalink RTA1046VW router, which
afaik doesn't have loopback which I hear is the problem, but I read that
setting up the Static DNS paths is a way around this. As I have seen it is
ok for connecting to the server via console from LAN, but not for forcing
the server.

 

This is driving me insane as I'm sure there is an obvious fix to this, but I
just can't see it! I'm sure I'm not the only person with a server who likes
to be able to start a game from the lobby with friends not on the lan! 

 

Thanks all,

 

Lyndon

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to