Ashoba Jun 20, 2017 @ 9:13am
Error connecting to server via WAN
Dear, good afternoon.

I created a dedicated csgo server in the Debian operating system. Apparently I have applied LAN and WAN connection settings, but I can only play on the server if it is on LAN. I can not connect through my WAN IP assigned to the server.

When I try to connect from inside the game through the command "connect <IP WAN>" the following error appears:

Connecting to public (***. ***. ***.: 27015) ...
Server using 'public' lobbies, requiring pw no, lobby id ffffffffffffffff

After this error, it fails to enter the game.

I stress that in LAN I can connect normally with my private IP.

Thank you for your attention, and I hope you can help me.

Atte.,

NIlton.
< >
Showing 1-9 of 9 comments
Blaquicat Jun 20, 2017 @ 12:54pm 
Others players can connect to your server?
Not all routers do auto-loopback (throw the connection back to the internal network using fowarding rules)

What game is?
Ashoba Jun 21, 2017 @ 4:00am 
Hello Blaquicat, I'm talking about CS: GO. Other players also can not connect.
I use the SonicWall appliance, it routes automatically, and I've already created firewall rules to free all ports used by steam.
Blaquicat Jun 21, 2017 @ 4:32am 
Hello Blaquicat, I'm talking about CS: GO. Other players also can not connect.
I use the SonicWall appliance, it routes automatically, and I've already created firewall rules to free all ports used by steam.
Sorry o don't know sonicwall..
But appears to be a port forwarding problem
Ashoba Jun 21, 2017 @ 5:48am 
I have already created rules for forwarding, NAT, and access in SonicWall by releasing all possible ports. I do not think that's the problem. I'm already without ideas ... :(
Sepp Jun 21, 2017 @ 8:02am 
Your setup is confusing tbh.
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.
Blaquicat Jun 21, 2017 @ 8:53am 
Originally posted by Sepp:
Your setup is confusing tbh.
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.
Not exactly, srcds server will respond based on port forwarding on the internal ip (always) however, it will accept connections and recognize the wan ip address..
My l4d2 servers shows up both internal and external ip (on status) and both works fine on local network.
..::Dokyyy::..™ Jun 21, 2017 @ 9:52am 
ghdrvdf
Ashoba Jun 21, 2017 @ 11:57am 
Originally posted by Sepp:
Your setup is confusing tbh.
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.


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.
Ashoba Jun 21, 2017 @ 12:02pm 
Originally posted by Blaquicat:
Originally posted by Sepp:
Your setup is confusing tbh.
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.
Not exactly, srcds server will respond based on port forwarding on the internal ip (always) however, it will accept connections and recognize the wan ip address..
My l4d2 servers shows up both internal and external ip (on status) and both works fine on local network.


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.
< >
Showing 1-9 of 9 comments
Per page: 1530 50