Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    TS3 Server cannot be reached

    Scheduled Pinned Locked Moved NAT
    3 Posts 3 Posters 1.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      Winzier09
      last edited by

      I am running a teamspeak 3 server that cannot seem to forward the 9987 port on pfsense. TS3 Server is on a virtual Ubuntu server through Hyper-V that located on a physical box that shares a VM with pfsense. Everything in the home works fine internet wifi etc.

      Before Pfsense clients could connect to the teamspeak server, but after no one can reach in. I have the basic 9987 port and I have tried forwarding it on pfsense. (I heard something about Split DNS, but I am not sure what my host name or domain name would be for the ubuntu server.) I included a photo as well. I've tried everything possible on the port forwarding side.

      The ubuntu can ping google and reach out to everything and has the ports all forwarded on it

      Here is my 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
      The switch has a wireless router connected used as an access point *No dhcp that is located on pfsense *other users are using the switch as well

      What are your thoughts on why external users cannot connect? I can connect to it on my own network and console into through putty.
      Ports.jpg
      Ports.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • nodauN
        nodau
        last edited by

        first thoughts,

        1. try telnet from inside and check port connectivity
        2. try online telnet and check if ports are reachable from outside
        3. check, if rules are set on appropriate interface (i know it's a linked rule ;-) )
        4. the server 13 will never be reached since you are on the same wan interface. so all packets will be delivered to the first match in your nat list and that is server 2

        i have a ts3 server running on a dmz interface and having no trouble (neither inside nor outside) nat reflection needs be enabled in the advanced setting to reach the public ts3 from inside.

        Norman

        virtualized pfSense 2.7.2 HA-Cluster on vsphere 8

        1 Reply Last reply Reply Quote 0
        • D
          dvserg
          last edited by

          Multipost here https://forum.pfsense.org/index.php?topic=94117.0

          SquidGuardDoc EN  RU Tutorial
          Localization ru_PFSense

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.