Results 1 to 14 of 14
Thread: [Solved] Forwarded port ...
-
01-04-2010, 04:36 #1
-= TeamSpeak User =-
- Join Date
- Jan 2009
- Location
- somewhere
- Posts
- 18
[Solved] Forwarded port ...
Alright guys, quick question for ya.
I got the port 9987 (UDP) forwarded on the IP address 192.168.1.6
Now how do I make sure that TS3 is looking for the IP address 192.168.1.6?
I've looked around, but can't seem to find any information.
Thanks!
-
01-04-2010, 06:47 #2
-= TeamSpeak Fanatic =-
- Join Date
- Feb 2006
- Location
- Texas, USA
- Posts
- 4,187
I assume you are talking about the server. Look in the server logs. The server shouldn't be looking for that IP specifically, it should be looking for ANY IP.
-
01-04-2010, 11:52 #3
-= TeamSpeak User =-
- Join Date
- Jan 2009
- Location
- somewhere
- Posts
- 18
Thanks for the reply.
I gues I don't know what to say then. I can connect with the local host, but whenever I try to connect from the "outside" I'm not able to.
Here are screenshots of what I've done so far.
http://screencast.com/t/ZThlYWY3Y
Guess I'm not sure what else you guys want me to show you. I didn't forward the other two ports b/c I know I won't need those funtions.
Also, here are the latest server logs.
2010-04-01 10:43:10.139300|INFO |ServerLibPriv | | Server Version: 3.0.0-beta21 [Build: 10608], Windows
2010-04-01 10:43:10.194300|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, (c)TeamSpeak Systems GmbH
2010-04-01 10:43:10.194300|INFO |DatabaseQuery | | dbPlugin version: 3.6.21
2010-04-01 10:43:10.224300|INFO |DatabaseQuery | | checking database integrity (may take a while)
2010-04-01 10:43:10.261300|INFO |SQL | | pruning old database log entries where timestamp is older than 90 days
2010-04-01 10:43:10.501300|WARNING |Accounting | | Unable to find valid license key, falling back to limited functionality
2010-04-01 10:43:10.621300|INFO |FileManager | | listening on 0.0.0.0:30033
2010-04-01 10:43:10.829300|INFO |VirtualServer | 1| listening on 0.0.0.0:9987
2010-04-01 10:43:10.834300|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1, 24.179.244.77,
2010-04-01 10:43:10.838300|INFO |Query | | listening on 0.0.0.0:10011
-
01-04-2010, 12:03 #4
-= TeamSpeak Fanatic =-
- Join Date
- Feb 2006
- Location
- Texas, USA
- Posts
- 4,187
While on your LAN you need to use either the LAN IP (if server is on a different computer) or localhost/127.0.0.0 (if the server is on same computer)
When you forwarded the ports did you do it in both your router and any software firewalls you have? Outside of your LAN you will need the external IP address which you can get from places like http://www.whatismyip.com/
**EDIT**
Sorry if I stated something you have in your screenshot. I'm at work and can't view that web address.
-
01-04-2010, 12:10 #5
-= TeamSpeak User =-
- Join Date
- Jan 2009
- Location
- somewhere
- Posts
- 18
All I showed in that screenshot was that I forwarded the UDP port 9987 to 192.168.1.6
I did get my external IP address which I try to put back into Address bar in the client, but it still says failed to connect. I went into Windows Firewall and allowed both UDP ports 9987. Kind of frustrating ... thanks for the fast reply.
-
01-04-2010, 12:16 #6
-= TeamSpeak Fanatic =-
- Join Date
- Feb 2006
- Location
- Texas, USA
- Posts
- 4,187
If you are on the LAN you will not be able to connect using the external IP. Double check that you have the correct LAN IP for the computer with the TS server on it. I would recommend setting a static IP or an IP reservation in your router for the computer running the server. If you don't there is a possibility that when this computer connects to the router it may be assigned a different IP than what you have in your port forward settings.
I would forward them to start and get the server working. After it works you can remove them if you do not use them but get the server working firstI didn't forward the other two ports b/c I know I won't need those funtions.
Some firewalls require you do a range of ports to cover a port i.e. 9986-9988 for port 9987 to be open.
-
01-04-2010, 12:18 #7
-= TeamSpeak Fanatic =-
- Join Date
- Feb 2006
- Location
- Texas, USA
- Posts
- 4,187
If you would like, PM me your server IP/port & password (if it has one) and when I get home from work in a few hours I'll try and connect.
-
01-04-2010, 12:24 #8
-= TeamSpeak User =-
- Join Date
- Jan 2009
- Location
- somewhere
- Posts
- 18
The computer I'm on right now is the one that I'm hosting the server with. My LAN IP should be 192.168.1.1
I just set my static DNS IP TO 192.168.1.1
I have all of those ports forwarded.
EDIT: PM sent -- I forgot to say that the port is 9987.
-
01-04-2010, 13:43 #9
-= TeamSpeak Fanatic =-
- Join Date
- Feb 2006
- Location
- Texas, USA
- Posts
- 4,187
I got home early and just tried to connect but got a failure. Go to START->RUN and type CMD. In this window type ipconfig and press ENTER. Look for the IPv4 address (this is your LAN IP) and verify that this is the address you forwarded your ports to.
-
01-04-2010, 14:06 #10
-= TeamSpeak User =-
- Join Date
- Jan 2009
- Location
- somewhere
- Posts
- 18
I just got out of a class and am at work now ... I go to a 2nd job after this one so I won't be home until about 3 PM Central. I emailed someone at my home to see if they can get the IPv4 information.
Thanks for the help!
-
01-04-2010, 14:08 #11
-= TeamSpeak Fanatic =-
- Join Date
- Feb 2006
- Location
- Texas, USA
- Posts
- 4,187
Oh ok, I should be around. 3pm central is 10pm here but I have off tomorrow so I'll probably be gaming or something. We'll get this figured out
-
02-04-2010, 02:59 #12
-
02-04-2010, 09:40 #13
-= TeamSpeak Fanatic =-
- Join Date
- Feb 2006
- Location
- Texas, USA
- Posts
- 4,187
@pillbox1234567
He figured it out. He just had the ports forwarded to the wrong IP. Once he fixed that it worked like a charm
-
12-04-2010, 06:33 #14
-= TeamSpeak Lover =-
- Join Date
- Jun 2003
- Location
- GERMANY
- Posts
- 35
Nevertheless a feature either on TS website or in the client to test the EXTERNAL connectivity of ones private at home TS Server would be of great
help. 99% of home users these days are on LAN cuz they use ROUTERS.
If you always need a 3rd party to check if your connectable from the outside
that is mildly said SUB OPTIMAL. I ran into the problem myself and it was annoying no to be able to test properly on my own. A simple portchecker
on TS support page would suffice for the most basic needs (at least to know if port is reachable).
Of course one could try use other websites that offer such a portscan (some security sites do) but why shouldnt TS improve on this
subject...see no real reason for that (setting up a limit eg of 10 portscans to same IP within a certain period of time will nullify abuse
attempts.)
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
[Solved] Since beta 19 : unable to bind network port
By Swagger in forum Server SupportReplies: 2Last Post: 11-03-2010, 15:40 -
Jdawgg's Guid to Starting a TeamSpeak 2 SERVER
By JD in forum [TeamSpeak 2] Server SupportReplies: 21Last Post: 14-08-2008, 14:54 -
Can't enter admistration or my server.
By TheSavior in forum [TeamSpeak 2] Server SupportReplies: 12Last Post: 10-06-2006, 22:48 -
Forwarded the Port But still doesnt work
By Xabition in forum [TeamSpeak 2] Server SupportReplies: 5Last Post: 20-01-2005, 06:22


Reply With Quote
