Forum

Results 1 to 9 of 9
  1. #1
    Join Date
    April 2014
    Posts
    3

    can connect from LAN, cannot from Internet

    Hi all- Since EA just took voice chat out of Battlelog, I decided to set up my own TeamSpeak 3 server. Everything is great, but I cannot connect from the Internet. However, I can connect from within my LAN. I'm using AT&T U-Verse DSL.

    1) all my ports are configured on the router. I even added TCP 9987 for grins. See pic below:

    http://i1311.photobucket.com/albums/...psa069d876.jpg

    2) I can connect to the TeamSpeak server from the Internet via Telnet. odd, huh?

    3) here are the netstat -a results if it helps...

    Code:
    C:\Users\Mike>netstat -a
    
    Active Connections
    
      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:80             TheRock:0              LISTENING
      TCP    0.0.0.0:135            TheRock:0              LISTENING
      TCP    0.0.0.0:443            TheRock:0              LISTENING
      TCP    0.0.0.0:445            TheRock:0              LISTENING
      TCP    0.0.0.0:2869           TheRock:0              LISTENING
      TCP    0.0.0.0:3306           TheRock:0              LISTENING
      TCP    0.0.0.0:5357           TheRock:0              LISTENING
      TCP    0.0.0.0:10011          TheRock:0              LISTENING
      TCP    0.0.0.0:18501          TheRock:0              LISTENING
      TCP    0.0.0.0:30033          TheRock:0              LISTENING
      TCP    0.0.0.0:49152          TheRock:0              LISTENING
      TCP    0.0.0.0:49153          TheRock:0              LISTENING
      TCP    0.0.0.0:49154          TheRock:0              LISTENING
      TCP    0.0.0.0:49155          TheRock:0              LISTENING
      TCP    0.0.0.0:49170          TheRock:0              LISTENING
      TCP    0.0.0.0:49171          TheRock:0              LISTENING
      TCP    0.0.0.0:57621          TheRock:0              LISTENING
      TCP    127.0.0.1:4370         TheRock:0              LISTENING
      TCP    127.0.0.1:4380         TheRock:0              LISTENING
      TCP    127.0.0.1:5354         TheRock:0              LISTENING
      TCP    127.0.0.1:5354         smtp:49156             ESTABLISHED
      TCP    127.0.0.1:5354         smtp:49158             ESTABLISHED
      TCP    127.0.0.1:8099         TheRock:0              LISTENING
      TCP    127.0.0.1:9990         TheRock:0              LISTENING
      TCP    127.0.0.1:23401        TheRock:0              LISTENING
      TCP    127.0.0.1:25639        TheRock:0              LISTENING
      TCP    127.0.0.1:27015        TheRock:0              LISTENING
      TCP    127.0.0.1:27015        smtp:49207             ESTABLISHED
      TCP    127.0.0.1:49156        smtp:5354              ESTABLISHED
      TCP    127.0.0.1:49158        smtp:5354              ESTABLISHED
      TCP    127.0.0.1:49200        TheRock:0              LISTENING
      TCP    127.0.0.1:49207        smtp:27015             ESTABLISHED
      TCP    127.0.0.1:60970        smtp:60971             ESTABLISHED
      TCP    127.0.0.1:60971        smtp:60970             ESTABLISHED
      TCP    127.0.0.1:62514        TheRock:0              LISTENING
      TCP    192.168.1.74:139       TheRock:0              LISTENING
      TCP    192.168.1.74:51906     sjc1-accesspoint-a30:4070  ESTABLISHED
      TCP    192.168.1.74:51908     terastacker:microsoft-ds  ESTABLISHED
      TCP    192.168.1.74:51913     17.149.36.172:5223     ESTABLISHED
      TCP    192.168.1.74:51915     74.125.129.125:5222    ESTABLISHED
      TCP    192.168.1.74:53100     214:43357              ESTABLISHED
      TCP    192.168.1.74:53777     200.126.64.8:53303     ESTABLISHED
      TCP    192.168.1.74:57438     nuq05s01-in-f22:https  ESTABLISHED
      TCP    192.168.1.74:57484     cpe-24-28-27-12:37069  ESTABLISHED
      TCP    192.168.1.74:57486     118-167-27-137:31196   ESTABLISHED
      TCP    192.168.1.74:57492     c-50-135-121-111:50638  ESTABLISHED
      TCP    192.168.1.74:57613     175.143.210.168:13856  ESTABLISHED
      TCP    192.168.1.74:57646     nuq05s02-in-f20:https  ESTABLISHED
      TCP    192.168.1.74:57648     nuq05s01-in-f14:https  ESTABLISHED
      TCP    192.168.1.74:57659     nuq05s02-in-f8:https   ESTABLISHED
      TCP    192.168.1.74:57660     homeportal:http        ESTABLISHED
      TCP    [::]:80                TheRock:0              LISTENING
      TCP    [::]:135               TheRock:0              LISTENING
      TCP    [::]:443               TheRock:0              LISTENING
      TCP    [::]:445               TheRock:0              LISTENING
      TCP    [::]:2869              TheRock:0              LISTENING
      TCP    [::]:3306              TheRock:0              LISTENING
      TCP    [::]:3587              TheRock:0              LISTENING
      TCP    [::]:5357              TheRock:0              LISTENING
      TCP    [::]:49152             TheRock:0              LISTENING
      TCP    [::]:49153             TheRock:0              LISTENING
      TCP    [::]:49154             TheRock:0              LISTENING
      TCP    [::]:49155             TheRock:0              LISTENING
      TCP    [::]:49170             TheRock:0              LISTENING
      TCP    [::]:49171             TheRock:0              LISTENING
      TCP    [fe80::5549:19b:806d:bc1c%10]:51919  [fe80::1029:6771:c696:5460%10]:microsoft-ds  ESTAB
      UDP    0.0.0.0:500            *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:4500           *:*
      UDP    0.0.0.0:5355           *:*
      UDP    0.0.0.0:9987           *:*
      UDP    0.0.0.0:50130          *:*
      UDP    0.0.0.0:55288          *:*
      UDP    0.0.0.0:55290          *:*
      UDP    0.0.0.0:56082          *:*
      UDP    0.0.0.0:57326          *:*
      UDP    0.0.0.0:57621          *:*
      UDP    0.0.0.0:62484          *:*
      UDP    0.0.0.0:64394          *:*
      UDP    127.0.0.1:1900         *:*
      UDP    127.0.0.1:44301        *:*
      UDP    127.0.0.1:48200        *:*
      UDP    127.0.0.1:48201        *:*
      UDP    127.0.0.1:48202        *:*
      UDP    127.0.0.1:53375        *:*
      UDP    127.0.0.1:53376        *:*
      UDP    127.0.0.1:53772        *:*
      UDP    127.0.0.1:53773        *:*
      UDP    127.0.0.1:53799        *:*
      UDP    127.0.0.1:53800        *:*
      UDP    127.0.0.1:55063        *:*
      UDP    127.0.0.1:62087        *:*
      UDP    127.0.0.1:62514        *:*
      UDP    127.0.0.1:64392        *:*
      UDP    127.0.0.1:64393        *:*
      UDP    127.0.0.1:64807        *:*
      UDP    192.168.1.74:137       *:*
      UDP    192.168.1.74:138       *:*
      UDP    192.168.1.74:1900      *:*
      UDP    192.168.1.74:1900      *:*
      UDP    192.168.1.74:5353      *:*
      UDP    192.168.1.74:5353      *:*
      UDP    192.168.1.74:21328     *:*
      UDP    [::]:500               *:*
      UDP    [::]:3540              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:4500              *:*
      UDP    [::]:5355              *:*
      UDP    [::]:55289             *:*
      UDP    [::]:55291             *:*
      UDP    [::]:57327             *:*
      UDP    [::]:62485             *:*
      UDP    [::]:64395             *:*
      UDP    [::1]:1900             *:*
      UDP    [::1]:5353             *:*
      UDP    [::1]:5353             *:*
      UDP    [::1]:64806            *:*
      UDP    [fe80::5549:19b:806d:bc1c%10]:1900  *:*
    4) I disabled the Windows firewall on the machine running the TeamSpeak server, but that didn't help.

    5) I have not tried doing a DMZ on the router yet since my wife is using our connection for work right now.

    6) yougetsignal.com says that ports 10011 and 30033 are open.

    7) even more strange... yougetsignal.com says that port 9987 is not open. that would make sense if I only had it open as a UDP port, but I also set it as an open TCP port. From what I can find, AT&T does not block this port.

    That's about all I can think of. Can you all think of something I missed? Is anyone else running a TS server from behind an AT&T U-verse router?

    thanks in advance. -Mike

  2. #2
    Join Date
    December 2009
    Location
    UK
    Posts
    768
    2) Are you saying you can't connect to the Teamspeak internet IP from inside your LAN? If that's the case, it's not unusual, some routers don't allow connections to that IP from inside the LAN

    7) Any port checker will only report ports open if they've had a reply from some software listening on that port, Teamspeak doesn't listen on port 9987 TCP

  3. #3
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,350
    5) Do not disable NAT. That's risky.

    Quote Originally Posted by Air SeaTac View Post
    2) Are you saying you can't connect to the Teamspeak internet IP from inside your LAN? If that's the case, it's not unusual, some routers don't allow connections to that IP from inside the LAN
    Is it router or ISP?

  4. #4
    Join Date
    December 2009
    Location
    UK
    Posts
    768
    Quote Originally Posted by numma_cway View Post
    Is it router or ISP?
    I meant he might not be able to connect to Teamspeak from inside the LAN through his WAN IP if that's what you're getting at

  5. #5
    Join Date
    April 2014
    Posts
    3
    Interesting. I can connect to it with the server itself using both my LAN and WAN IP. So, I tried that same test with another computer on my network. It would only connect with the LAN IP. So, I assumed it wasn't working for external Internet connections. I'll take my laptop out and see if I can get on some other network and try it again. I'll keep you posted. Thanks for the info.

  6. #6
    Join Date
    December 2009
    Location
    UK
    Posts
    768
    If you wanted to post your server's address there's plenty of people here who could test it

  7. #7
    Join Date
    April 2014
    Posts
    3
    [SOVLED] Apparently, the router won't let you connect to your own server from inside your own network if you use the external address or IP. I did not know that, and it was working all along. Thanks for everyone's help.

  8. #8
    Join Date
    November 2014
    Posts
    1

    Cannot connect through internet.

    So I tested the server. I didn't change any settings. I can connect it through localhost, I can connect it through lan but I cannot connect via the internet. Yet if I use my client, I can join public servers outsides.

    I have checked ips and port forwards so there aren't any mistype. Any suggestion what would go wrong?

    Thank you.
    Last edited by dante696; November 7th, 2014 at 03:47 PM. Reason: merged

  9. #9
    Join Date
    June 2008
    Posts
    18,151
    Ask a friend to connect. Not all routers allow, that you can connect to the external ip.

    This has been answered many times!
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. TS3 can't connect to the internet
    By knoxcorner in forum Windows
    Replies: 0
    Last Post: June 24th, 2013, 04:10 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •