1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Open Ports question

Discussion in 'Networking' started by ven15_ss, Mar 20, 2010.

Thread Status:
Not open for further replies.
Advertisement
  1. ven15_ss

    ven15_ss Thread Starter

    Joined:
    May 22, 2007
    Messages:
    57
    I have Windows 7 - 64 bit Home Premium on Asus P7P55D LE motherboard and GT240 card.

    For Internet I hase ADSL2 and use a Netgear DGN2000 moden/router. And use Trend Micro Internet Securtity 2009.

    I have a dyndns account and have been trying to set up a Teamspeak 3 server. I can connect to sever os localhost. When I try Portforwards open port tool it says port 9987 is not open.

    Result from port check
    Error: I could not see your service on xxx.xxx.xxx.xxx on port (9987)
    Reason: Connection refused

    I have setup port forwarding on router and have allowed server program in Trend. I think it is set right. The IPS has advised they do not block 9987.

    The other 2 ports (TCP 10011 & 30033) have not been set up as I understand they are not needed.

    Below is result from netstat -a

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Kathy>netstat -a

    Active Connections

    Proto Local Address Foreign Address State
    TCP 0.0.0.0:135 New-PC:0 LISTENING
    TCP 0.0.0.0:445 New-PC:0 LISTENING
    TCP 0.0.0.0:554 New-PC:0 LISTENING
    TCP 0.0.0.0:2869 New-PC:0 LISTENING
    TCP 0.0.0.0:5357 New-PC:0 LISTENING
    TCP 0.0.0.0:10011 New-PC:0 LISTENING
    TCP 0.0.0.0:10243 New-PC:0 LISTENING
    TCP 0.0.0.0:30033 New-PC:0 LISTENING
    TCP 0.0.0.0:49152 New-PC:0 LISTENING
    TCP 0.0.0.0:49153 New-PC:0 LISTENING
    TCP 0.0.0.0:49154 New-PC:0 LISTENING
    TCP 0.0.0.0:49155 New-PC:0 LISTENING
    TCP 0.0.0.0:49156 New-PC:0 LISTENING
    TCP 0.0.0.0:49158 New-PC:0 LISTENING
    TCP 0.0.0.0:49159 New-PC:0 LISTENING
    TCP 0.0.0.0:49177 New-PC:0 LISTENING
    TCP 127.0.0.1:6999 New-PC:0 LISTENING
    TCP 127.0.0.1:37848 New-PC:0 LISTENING
    TCP 127.0.0.1:40000 New-PC:0 LISTENING
    TCP 127.0.0.1:40000 New-PC:49173 ESTABLISHED
    TCP 127.0.0.1:40000 New-PC:49174 ESTABLISHED
    TCP 127.0.0.1:40000 New-PC:49175 ESTABLISHED
    TCP 127.0.0.1:40000 New-PC:49176 ESTABLISHED
    TCP 127.0.0.1:40000 New-PC:49178 ESTABLISHED
    TCP 127.0.0.1:49173 New-PC:40000 ESTABLISHED
    TCP 127.0.0.1:49174 New-PC:40000 ESTABLISHED
    TCP 127.0.0.1:49175 New-PC:40000 ESTABLISHED
    TCP 127.0.0.1:49176 New-PC:40000 ESTABLISHED
    TCP 127.0.0.1:49178 New-PC:40000 ESTABLISHED
    TCP 192.168.0.2:139 New-PC:0 LISTENING
    TCP [::]:135 New-PC:0 LISTENING
    TCP [::]:445 New-PC:0 LISTENING
    TCP [::]:554 New-PC:0 LISTENING
    TCP [::]:2869 New-PC:0 LISTENING
    TCP [::]:3587 New-PC:0 LISTENING
    TCP [::]:5357 New-PC:0 LISTENING
    TCP [::]:10243 New-PC:0 LISTENING
    TCP [::]:49152 New-PC:0 LISTENING
    TCP [::]:49153 New-PC:0 LISTENING
    TCP [::]:49154 New-PC:0 LISTENING
    TCP [::]:49155 New-PC:0 LISTENING
    TCP [::]:49156 New-PC:0 LISTENING
    TCP [::]:49158 New-PC:0 LISTENING
    TCP [::]:49159 New-PC:0 LISTENING
    TCP [::]:49179 New-PC:0 LISTENING
    TCP [::1]:6999 New-PC:0 LISTENING
    UDP 0.0.0.0:500 *:*
    UDP 0.0.0.0:3544 *:*
    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:5004 *:*
    UDP 0.0.0.0:5005 *:*
    UDP 0.0.0.0:5355 *:*
    UDP 0.0.0.0:9987 *:*
    UDP 0.0.0.0:40116 *:*
    UDP 0.0.0.0:56350 *:*
    UDP 0.0.0.0:56352 *:*
    UDP 0.0.0.0:56354 *:*
    UDP 0.0.0.0:63095 *:*
    UDP 127.0.0.1:1900 *:*
    UDP 127.0.0.1:54249 *:*
    UDP 127.0.0.1:54472 *:*
    UDP 127.0.0.1:56356 *:*
    UDP 127.0.0.1:56504 *:*
    UDP 127.0.0.1:60645 *:*
    UDP 127.0.0.1:64445 *:*
    UDP 127.0.0.1:65120 *:*
    UDP 192.168.0.2:137 *:*
    UDP 192.168.0.2:138 *:*
    UDP 192.168.0.2:1900 *:*
    UDP 192.168.0.2:51565 *:*
    UDP 192.168.0.2:54248 *:*
    UDP [::]:500 *:*
    UDP [::]:3540 *:*
    UDP [::]:3702 *:*
    UDP [::]:3702 *:*
    UDP [::]:3702 *:*
    UDP [::]:3702 *:*
    UDP [::]:4500 *:*
    UDP [::]:5004 *:*
    UDP [::]:5005 *:*
    UDP [::]:5355 *:*
    UDP [::]:40116 *:*
    UDP [::]:56351 *:*
    UDP [::]:56353 *:*
    UDP [::]:56355 *:*
    UDP [::1]:1900 *:*
    UDP [::1]:54247 *:*
    UDP [fe80::85c:f571:6095:daf4%11]:546 *:*
    UDP [fe80::85c:f571:6095:daf4%11]:1900 *:*
    UDP [fe80::85c:f571:6095:daf4%11]:54246 *:*

    C:\Users\User>

    I do not know a lot about this but thought above info may help?

    Does this mean that 9987 is up and running?
    Is there a way to tell if it is being stopped by modem/router or Trend?

    Thanks
     
  2. makethissound

    makethissound

    Joined:
    Mar 17, 2010
    Messages:
    48
    1. Get another computer on your network. We'll call this test client1.
    2. Turn off all firewall software on the client PC (temporarily)
    3. Try to connect to the teamspeak server on your local network (by local IP). Success means that TrendMicro is not blocking the port.
    4. If you are able to successfully connect, get your buddy to try to try to connect from his house. If not, you need to poke the right holes in your software firewall.

    Also you may want to make sure your computer has a static DHCP lease from your router's DHCP server.
     
  3. ven15_ss

    ven15_ss Thread Starter

    Joined:
    May 22, 2007
    Messages:
    57
    I downloaded Teamspeak 3 to "client1" and decided to test without doing anything (turning off firewall) on sever PC. client1 connected.
    I then input the dyndns host name in lieu of local IP and it still got through - not sure if this is treated as external or not.
    Need to do a test with a friend from outside.
    Could a password cause the open port test to fail?
     
  4. makethissound

    makethissound

    Joined:
    Mar 17, 2010
    Messages:
    48
    A password could definitely cause it to fail. A port tester doesnt know how to authenticate, usually.

    When the computer uses DYNDNS to resolve the server name, it goes out to the internet and says, "Yo, DynDns servers, where do i go to get to this server name here?" and DynDns gives it your router's internet facing IP address. So using DynDns name will get it to go out to the internet and come back.
     
  5. ven15_ss

    ven15_ss Thread Starter

    Joined:
    May 22, 2007
    Messages:
    57
    Well definately confirmed port open and server working with a join via IP. However DYNDNS was not succesful from external.
    It has been suggested a DYNDNS link can take some time to work it's way around. So will try again fron next 2 nights to see if there is a change.

    Thanks
     
  6. JohnWill

    JohnWill Retired Moderator

    Joined:
    Oct 19, 2002
    Messages:
    106,409
    If you're waited 24 hours, I really doubt that it's a DynDNS issue.

    You can simply check if your DynDNS is working, ping your DynDNS URL and see if the IP address resolved matches your public IP address. If so, it's working properly.
     
  7. ven15_ss

    ven15_ss Thread Starter

    Joined:
    May 22, 2007
    Messages:
    57
    John

    I think this may be a NOOB question but never done any pinging before.

    How do I do it?

    Cheers
     
  8. Angriper

    Angriper

    Joined:
    Mar 18, 2010
    Messages:
    22
    Press start and then type 'CMD' into the box, and then open command prompt from the list.

    Type 'Ping <DynDNS URL>' to ping.
     
  9. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/911491