NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

OmegaStrife's avatar
OmegaStrife
Aspirant
Nov 11, 2024
Solved

RAXE300 Not Port Forwarding Correctly?

So I used to have a RAX80 which would forward ports completely fine, but I upgraded to the RAXE300 (Netgear Nighthawk) and it does not appear to be forwarding ports as I am intending. I tried as many things as possible to get it to work, but maybe y’all will have some advice. I have an AT&T Modem which is set to passthrough mode and the Nighthawk router with all of the correct ports forwarded to my computer’s local IP. The PLEX server on 32400 works fine and the port is open per canyouseeme.org, but I can’t get the ports to appear open for my local TeamSpeak 3 server which is what I’ve been using for years now. Any suggestions? I tried turning off uPnP, turning off NAT on the Netgear, using that IP address under DMZ, but nothing seems to be able to open it.

 

  • Yes, apologies. It turned out it was a very confusing issue with Windows Firewall. I had allowed permissions for the program, for ports, and various other settings but it never resolved until I just turned it into accepting all ports. I believe the router was working as intended the whole time. However, the issue occurred when I replaced the Nighthawk router that I had, so I have no idea why Windows Firewall started interrupting the process when I hadn't changed any settings. Mystery solved, I guess. I tore my hair out over this for about 4-5 days.

4 Replies

  • DarrenM's avatar
    DarrenM
    Sr. NETGEAR Moderator

    I would first try removing all the port forwarding but the 9987 and 30033 are the 2 ports that are required for Teamspeak and see if that works. You may also want to run the server as Admin when you boot it up on whatever device you use it.

     

    Thanks

    Darren

    • OmegaStrife's avatar
      OmegaStrife
      Aspirant

      Yes, apologies. It turned out it was a very confusing issue with Windows Firewall. I had allowed permissions for the program, for ports, and various other settings but it never resolved until I just turned it into accepting all ports. I believe the router was working as intended the whole time. However, the issue occurred when I replaced the Nighthawk router that I had, so I have no idea why Windows Firewall started interrupting the process when I hadn't changed any settings. Mystery solved, I guess. I tore my hair out over this for about 4-5 days.