Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Not all routers do auto-loopback (throw the connection back to the internal network using fowarding rules)
What game is?
I use the SonicWall appliance, it routes automatically, and I've already created firewall rules to free all ports used by steam.
But appears to be a port forwarding problem
What do you mean by LAN and WAN connection settings?
Does your server have 2 interfaces/ip addresses configured?
AFAIK the game server process can only be bound to one ip address and in your case it seems to be bound to your private lan ip address which means it'll never respond on the wan interface.
Binding the server to your wan ip address however might cause trouble for you being able to join via lan then (depends on your setup).
I'd recommend to use the usual setup by having only one lan ip configured on the server and then forward udp 27015 to this lan ip address.
My l4d2 servers shows up both internal and external ip (on status) and both works fine on local network.
Yes. I have a DNS server that works with domain zones. I have an IP lan and another WAN IP. The server responds internally over the LAN IP and externally over the WAN. Externally, I can access the server and make settings on it through IP WAN, but I can not connect in the game over IP WAN.
Exactly like you said, should work that way. Apparently it seems to be a firewall problem, but I've already made all the necessary settings to access the server, and I no longer have any ideas whatsoever. When I set up the server two weeks ago, I was able to connect only once externally over the IP WAN, and then the error mentioned by me always occurs. I also use ebot, and it works only via LAN.