Upvote Upvoted 2 Downvote Downvoted
Problem with own TF2 Server
posted in Q/A Help
1
#1
0 Frags +

Hi, there fellas I wanted to create my own TF2 server... I got it running so far and I can connect to it without a problem. But others cant seem to be able to do so. I forwarded port 27000 - 27040 on my Router and in my Firewall.
Now the thing is that I have the Server running on VirtualBox VM running CentOS. I also forwarded the ports there. But like I said... only I can connect. What am I missing the Public IP of the VM and the one of my Desktop is the same, that seems weird afaik.
Would appreciate help.

Hi, there fellas I wanted to create my own TF2 server... I got it running so far and I can connect to it without a problem. But others cant seem to be able to do so. I forwarded port 27000 - 27040 on my Router and in my Firewall.
Now the thing is that I have the Server running on VirtualBox VM running CentOS. I also forwarded the ports there. But like I said... only I can connect. What am I missing the Public IP of the VM and the one of my Desktop is the same, that seems weird afaik.
Would appreciate help.
2
#2
0 Frags +

What do you mean when you say "I forwarded the ports [on VirtualBox]"? What did you change to your VM's network configuration?

The public IP should be your router's IP.

Alternatively, you could just run the server directly on Windows, it should be easier to setup and you won't lose performance due to virtualization.

What do you mean when you say "I forwarded the ports [on VirtualBox]"? What did you change to your VM's network configuration?

The public IP should be your router's IP.

Alternatively, you could just run the server directly on Windows, it should be easier to setup and you won't lose performance due to virtualization.
3
#3
0 Frags +

First of all i changed the Network Adapter from my VM from NAT to Bridged. Then I forwarded the ports in CentOs with "firewall-cmd --zone=public --add-port=27015/udp ---permanent" did the same for tcp and the same for 27005.

Yeah its my routers public IP. But what are you supposed to enter into the "connect x.x.x.x:27015" command?

edit: So do other also enter the IP starting with 192.168 into the connect I thought it would the the local IP only. Or are the last 2 octets the public IP?

First of all i changed the Network Adapter from my VM from NAT to Bridged. Then I forwarded the ports in CentOs with "firewall-cmd --zone=public --add-port=27015/udp ---permanent" did the same for tcp and the same for 27005.

Yeah its my routers public IP. But what are you supposed to enter into the "connect x.x.x.x:27015" command?


edit: So do other also enter the IP starting with 192.168 into the connect I thought it would the the local IP only. Or are the last 2 octets the public IP?
4
#4
0 Frags +

You and they should connect to your 77.x.x.x IP (http://ip4.me/)
192.168.x.x is your local network

You and they should connect to your 77.x.x.x IP (http://ip4.me/)
192.168.x.x is your local network
5
#5
0 Frags +

Ok, I cant connect to the routers IP either. Only to my local... Whats the problem there.

Ok, I cant connect to the routers IP either. Only to my local... Whats the problem there.
6
#6
0 Frags +

Ok, the servers works without any problems on my Windows Desktop I just had the problem that there was no hltv ip port allocated. But I fixed that by putting +tv_port 27020 in to parameters...
Why is the server not working on my VM?

Ok, the servers works without any problems on my Windows Desktop I just had the problem that there was no hltv ip port allocated. But I fixed that by putting +tv_port 27020 in to parameters...
Why is the server not working on my VM?
7
#7
0 Frags +

It says
Socket connection failed (WSAEADDRNOTAVAIL)
Unable to connect to remote server (0.0.0.0:0)
when I rcon status in the Server-Console. If I rcon on server itself it says the same just with the Server IP instead of 0.0.0:0
Is there a fix for that?

It says
Socket connection failed (WSAEADDRNOTAVAIL)
Unable to connect to remote server (0.0.0.0:0)
when I rcon status in the Server-Console. If I rcon on server itself it says the same just with the Server IP instead of 0.0.0:0
Is there a fix for that?
Please sign in through STEAM to post a comment.