Teamspeak 3 Wont Allow Connections
-
Have you packet sniffed? Make sure you see the packets coming in and going out of PFSense and if the TS server is seeing the packets but dropping them.
-
Your picture shows you forwarding each port to two different servers.
Which of the servers 10.30.150.2 or 10.30.150.13 is the right one? With those rules, it can't forward to both.
-
The virtual server is on .13 the physical server it sits on it .2 so should I just forward to one? Users connected to the teamspeak server without pfsense in the mix and connected fine. Ive tried tracing the packets and watching the log summary and watch the incoming ip's get denied. It seems that there is some LAN interaction going on as well when an incoming ip tries to connect. Regardless i added them to allow passage as a rule but still nothing??
-
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.
