Forum

Results 1 to 3 of 3
  1. #1
    Join Date
    July 2009
    Location
    Mesa arizona
    Posts
    1

    can't connect to servers localhost

    I have two computer connected to a router then modem. one computer is using a wireless network card.

    I can't seem to connect to the server (8767) form my computer. I can access the http and the tcp parts of the server.

    firewall is configured to let traffic in and out of port 8767

    Code:
    [debug]
    MessageTypes=LMTALL
    MessageDepths=LMDALL
    [Main Config]
    ExternalIPDectection=1
    HTTPServer Port=14534
    HTTPServer Enabled=1
    DateTimeFormat=dd-mm-yyyy hh:nn:ss
    TCPQueryPort=51234
    AllowedClientNameChars=
    DisAllowedClientNameChars=()[]{}
    BoundToIp1=
    [WebPost]
    AdminEmail=na
    ISPLinkURL=na
    ISPName=Private
    ISPCountryNumber=2457
    Enabled=1
    PostURL=
    ListPublic=1
    UserAgent=teamspeak
    [log]
    access_r=0
    access_u=0
    channel_registerred=0
    channel_unregisterred=0
    sa=0
    chat=0
    kick_server=0
    kick_channel=0
    [Spam]
    max_commands=10
    in_seconds=2
    
    
    
    Windows IP Configuration
    
    
    
            Host Name . . . . . . . . . . . . : mathias
    
            Primary Dns Suffix  . . . . . . . : 
    
            Node Type . . . . . . . . . . . . : Unknown
    
            IP Routing Enabled. . . . . . . . : No
    
            WINS Proxy Enabled. . . . . . . . : No
    
            DNS Suffix Search List. . . . . . : ph.cox.net
    
    
    
    Ethernet adapter Local Area Connection 3:
    
    
    
            Media State . . . . . . . . . . . : Media disconnected
    
            Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet 
    
            Physical Address. . . . . . . . . : 00-24-8C-79-5D-8D
    
    
    
    Ethernet adapter Wireless Network Connection:
    
    
    
            Connection-specific DNS Suffix  . : ph.cox.net
    
            Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter
    
            Physical Address. . . . . . . . . : 00-18-39-14-17-10
    
            Dhcp Enabled. . . . . . . . . . . : Yes
    
            Autoconfiguration Enabled . . . . : Yes
    
            IP Address. . . . . . . . . . . . : 192.168.1.100
    
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
    
            Default Gateway . . . . . . . . . : 192.168.1.1
    
            DHCP Server . . . . . . . . . . . : 192.168.1.1
    
            DNS Servers . . . . . . . . . . . : 68.105.28.11
    
                                                68.105.29.11
    
                                                68.105.28.12
    
            Lease Obtained. . . . . . . . . . : Friday, July 17, 2009 3:48:08 PM
    
            Lease Expires . . . . . . . . . . : Sunday, July 19, 2009 3:48:08 PM
    
    
    
    
    Tracing route to ts2test.planetteamspeak.com [62.75.222.133]
    
    over a maximum of 30 hops:
    
    
    
      1     1 ms    <1 ms     1 ms  192.168.1.1 
    
      2    10 ms     9 ms    23 ms  10.52.64.1 
    
      3    39 ms    11 ms    12 ms  ip68-2-2-53.ph.ph.cox.net [68.2.2.53] 
    
      4    13 ms     9 ms    22 ms  70.169.73.85 
    
      5    22 ms    30 ms    36 ms  langbbrj02-as0.r2.la.cox.net [68.1.1.231] 
    
      6    34 ms    23 ms     *     te4-2.ccr01.lax01.atlas.cogentco.com [154.54.6.229] 
    
      7    63 ms    51 ms    69 ms  te9-8.ccr01.iah01.atlas.cogentco.com [154.54.0.238] 
    
      8    69 ms    50 ms    65 ms  te7-3.ccr02.dfw01.atlas.cogentco.com [154.54.2.225] 
    
      9    66 ms    59 ms    65 ms  te9-1.ccr02.mci01.atlas.cogentco.com [154.54.25.210] 
    
     10    93 ms    73 ms    73 ms  te2-1.ccr02.ord01.atlas.cogentco.com [154.54.5.174] 
    
     11   101 ms   100 ms   102 ms  te4-7.ccr02.ymq02.atlas.cogentco.com [154.54.28.6] 
    
     12   189 ms   196 ms   195 ms  te3-1.mpd01.ymq02.atlas.cogentco.com [154.54.7.125] 
    
     13   194 ms   193 ms   179 ms  te9-3.mpd03.fra03.atlas.cogentco.com [154.54.26.142] 
    
     14   272 ms   182 ms   190 ms  te4-2.ccr02.fra03.atlas.cogentco.com [130.117.49.150] 
    
     15   181 ms   185 ms   182 ms  te7-3.mpd01.fra03.atlas.cogentco.com [130.117.3.202] 
    
     16   203 ms   235 ms   223 ms  149.6.141.58 
    
     17   195 ms   186 ms   192 ms  static-ip-85-25-225-138.inaddr.intergenia.de [85.25.225.138] 
    
     18   193 ms   188 ms   236 ms  host1.sven-paulsen.de [62.75.222.133] 
    
    
    
    Trace complete.
    
    
    
    Active Connections
    
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       1124
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:14534          0.0.0.0:0              LISTENING       1360
      TCP    0.0.0.0:31103          0.0.0.0:0              LISTENING       3308
      TCP    0.0.0.0:50001          0.0.0.0:0              LISTENING       1064
      TCP    0.0.0.0:51234          0.0.0.0:0              LISTENING       1360
      TCP    127.0.0.1:1027         0.0.0.0:0              LISTENING       1848
      TCP    127.0.0.1:4119         127.0.0.1:4120         ESTABLISHED     2232
      TCP    127.0.0.1:4120         127.0.0.1:4119         ESTABLISHED     2232
      TCP    127.0.0.1:4125         127.0.0.1:4126         ESTABLISHED     2232
      TCP    127.0.0.1:4126         127.0.0.1:4125         ESTABLISHED     2232
      TCP    192.168.1.100:139      0.0.0.0:0              LISTENING       4
      TCP    192.168.1.100:1931     192.168.1.103:445      ESTABLISHED     4
      TCP    192.168.1.100:2305     207.46.110.112:1863    ESTABLISHED     3352
      UDP    0.0.0.0:427            *:*                                    260
      UDP    0.0.0.0:445            *:*                                    4
      UDP    0.0.0.0:500            *:*                                    908
      UDP    0.0.0.0:4500           *:*                                    908
      UDP    0.0.0.0:8767           *:*                                    1360
      UDP    0.0.0.0:31103          *:*                                    3308
      UDP    127.0.0.1:123          *:*                                    1240
      UDP    127.0.0.1:1101         *:*                                    3352
      UDP    127.0.0.1:1900         *:*                                    3308
      UDP    127.0.0.1:1900         *:*                                    1548
      UDP    127.0.0.1:3722         *:*                                    3300
      UDP    192.168.1.100:123      *:*                                    1240
      UDP    192.168.1.100:137      *:*                                    4
      UDP    192.168.1.100:138      *:*                                    4
      UDP    192.168.1.100:427      *:*                                    260
      UDP    192.168.1.100:1900     *:*                                    1548
    http://i271.photobucket.com/albums/j...2/untitled.jpg

    if u need any more info just ask.

  2. #2
    Join Date
    December 2004
    Location
    RF
    Posts
    3,006
    What the meaning of your router setup if you want to connect to the server in your local network? (that aside, what you're showing us is a wrongly configured router)

  3. #3
    Join Date
    May 2006
    Location
    Europe/Czech Rep.
    Posts
    1,616
    I will explain this IT specification.(now its my turn ANR )

    server on localhost should work. did you tryed address like
    localhost
    127.0.0.1
    192.168.1.100
    the last will most likely work...
    if not then you should check firewall (maybe antivirus but that is rare)

    the following involves router configuration and allowing internet users to connect to your teamspeak:
    ummm in quoted text theres IP address *.100 and in picture of router if I skip all other stuff in it theres *.103 for ts record of port 8767 plus it can be set to (protocol)UDP only.
    as long as goes fot tmser and tmptp if its meaning for teamspeak if I skip also again wrong IP destination the protocol there have to be TCP not udp

    seriously its wonderfull example of wrongly configured router.
    example of BF2a and BF2b can be merged with protocol Both instead of BF2a for UDP and BF2b for TCP
    same goes for BF2d and BF2e

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Can't connect even to localhost
    By turtlebasic in forum Windows
    Replies: 8
    Last Post: October 24th, 2014, 01:25 PM
  2. Cannot connect to my server via localhost
    By DaLucky7 in forum Server Support
    Replies: 2
    Last Post: October 23rd, 2014, 05:16 PM
  3. can not connect to localhost or IP
    By danieltm13 in forum Server Support
    Replies: 9
    Last Post: March 22nd, 2014, 02:27 PM
  4. New, cannot connect to localhost
    By CrusaderOutland in forum Server Support
    Replies: 11
    Last Post: March 26th, 2013, 10:00 AM
  5. Can only connect through localHost
    By UndeadMyth in forum Server Support
    Replies: 5
    Last Post: June 14th, 2011, 12:34 PM

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
  •