Teamspeak 3 Wont Allow Connections
-
The virtual server is on .13 the physical server it sits on it .2 so should I just forward to one?
Huh? You need to forward the port to the IP address expecting the connections.
-
The virtual server is on .13 the physical server it sits on it .2 so should I just forward to one?
Huh? You need to forward the port to the IP address expecting the connections.Thanks
-
Nope changed nothing. Still cannot connect.
-
To clarify, right now you're forwarding JUST to .13, right?
-
Yes port forwarding to .13 to the virtual server where the teamspeak 3 Ubuntu server sits.
-
Have you tried rebooting? I had a firewall issue with TS where it wouldn't forward connections through correct (It would block them –- I pulled it out of the firewall log). I rebooted and then it worked fine after that.
-
Yes port forwarding to .13 to the virtual server where the teamspeak 3 Ubuntu server sits.
Could you also post a picture of the Firewall -> Rules -> WAN tab?
-
Tried rebooting still wont allow anyone in. Now it doesn't even show incoming connections on the system log->firewall. It does keep showing LAN connections every time anyone tries to connect.
-
Did you nuke the 30033 forward? I don't see a corrisponding rule for it in that pic, but I do see two separate ones for 10011
-
Changed it. Check these photos out. Still nothing
EDIT I changed the 10011 on the port forward one
-
That WAN thing is still wrong. You did NOT change the NAT ports, only the destination port.
-
Please see the edit. I changed the wan 10011 to 30033
-
No. You only changed it in one place. Look at the NAT Ports field!
-
Yes I did. Here
-
Wonderful. Now, either reset the states or reboot the box.
-
Rebooted still cant get clients =\
-
Sucks to be you. Produce some packet captures.
-
I'm trying to understand your setup. Modem–--> Into NIC #1 into a virtual machine that uses that port dedicated *no bridge the connections go out of it through ----> NIC# 2 the lan port which is bridged ----> into a switch
do you mean that pfsense is virtualized or is it on bare metal, and when you say it uses a dedicated port no bridge do you mean it's a virtual nic?Secondly is your modem a full modem, not one of the generic modem/router combo devices isp's like to give out? If it is one of those combo devices then you'll have to configure it to port forward to the pfsense box.
-
In this post:
https://forum.pfsense.org/index.php?topic=94117.msg523417#msg523417
You do not have a rule on WAN for 30033.
I don't know if you are using the linked rules from your port forwards or not.
This stuff really does "just work."
-
And the most current settings.
