Troubles with Setting up server

[Yvarb]

hello, i recently tried to set up a Teamspeak 2 Server, but it's not really working.
my connection looks like this:

Modem -> Router -> Pc1 + 2 -> hub -> pc3 -> Hub ->Pc4+5

i already forwarded the ports to the internal ip adres of the pc its running on (PC5 in this case), but the problem is, i cant even connect internally. when i try to connect to pc5 (192.168.1.120) with teamspeak 2, it doesn't recognize a server running, while i really have the application running.

I am using Teamspeak 2 (2.0.32.60) to connect, and the server version is uknown to me, but it's the newest one to date (14/12/06). i can connect to the administration panel, but that's about it.

What am i doing wrong? if you require any additional information, ill add them.

this is my server.ini:

[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=4445
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

[Reedy Boy]

Its a bit of a strange setup, as that is routed through different pc's

Or thats how it looks, or is it like

Modem -> Router -> hub -> Hub
| | |
Pc1 + 2 pc3 Pc4+5

?

[Yvarb]

it's not that, it's a bit of a weird setup, but it works with my ftp server aswell.
i just found something which might be the problem tho,
if i try to connect to 192.168.1.120, my internal ip, it says no server running.
but when i connect to localhost, it connects to 127.0.0.1:8767, and voila, there's my server. but that's not my ip at all, doesnt show up when i run ipconfig command either. did i configure something wrong somewhere? the server gives the ip
62.x.x.x, which is my outdoor ip, and it shows 192.1.168.120, which is my LAN ip, it doesnt show 127.0.0.1 anywhere.

edit:
i used bindtoip1 192.168.1.120, and i can connect now, using both WAN and LAN ips, but others still say they cant.

So in short, the problem atm is that no one except myself can connect.

[WolfStar76]

127.0.0.1 is a reserved address called "localhost." Put simply, 127.0.0.1 says "connect to yourself" - which is why you won't find it listed in ipconfig.

You mention your connection is modem -> Router. Would that be a DSL modem by chance? If so, it probably has a rotuer built into IT as well.

If I'm right you'd need to configur port forwarding on the modem to direct traffic to the router. Then tell the router to forward to the machine running TeamSpeak Server.

Just a thought.

[Yvarb]

its just a cable modem with no router functionalitys, and the routing is not the problem i think. because, i cant connect using 192.168.1.120 either, and that's my internal ip, so it should be running there. only localhost works, or when i use BoundToIP1=192.168.1.120, but then it only works for myself.

[WolfStar76]

I have to confess, I'm not overly familiar with the use of the BindToIP command, having never needed it myself.

It's my understanding, however, that that's really only needed in a system with more than one NIC (and therefore more than one potential IP address). It's purpose being to tell TeamSpeak Server which of the IP addresses to listen on. Again, having not used it myself, this is largely conjuncture from what I've read here and there.

The binding allows you to connect to the LAN address, so I'd say that's the least of our worries at the moment. This isn't related to routing, however, since the router doesn't handle traffic on your LAN - just traffic passing to and from the LAN to the WAN.

The fact that you have several hubs on the network *shouldn't* be an issue either, since a hub is just an unintelligent repeater, so there shouldn't be any configuration to worry about there.

The 3 things to check are the following (and I'm stealing them from my generic checklist posted elsewhere).

1) Are you sure your users are connecting to your correct WAN address? You can verify this by checking your WAN IP at www.whatismyip.com. Even if you've checked before, check again. A "standard" cable connection has a dynamic IP which is subject to change at your ISP's whim.

2) Double-check your routing configuration. I'm sure you've checked it time and again, and are probably sick of checking it, but it can't hurt to look again. The most common mistake I see here is people accidently forwarding traffic to their router instead of the correct LAN PC. For added difficulty, if you don't have a static IP on your PC, the address chould change internally sometimes, thereby invalidating your port forwarding. Give your PC a Static IP, or a DHCP reservation.

www.portforward.com is a great resource for making sure you've configure your router correctly. It couldn't hurt to double-check your settings against what's posted there for your model of router.

3) Software Firewalls. By default, these block inbound traffic to your PC - especially if that traffic isn't on the same subnet as your PC (IE - Internet traffic). This includes the Windows XP firewall, that was turned ON by default in SP2.

For testing you can disable any software firewalls you're running - just to see if the connection works that way. I don't recommend leaving it off in the long-term, however, for security reasons. Instead, poke around your firewalls settings, and make an Exception for traffic inbound on UDP port 8767.

With all of THAT in place, it *should* work. If it isn't there's another kink in the system somewhere that we'd have to locate. Give all of that a try and report back. :)

[FlyNavy]

This is a strange setup. From what I read, PC2 and PC3 have 2 NICs? Although the hubs are dumb repeaters, the dual NICs are not. If they are not bridged or have packet forwarding turned on, no info will go between the other segments. Do you have internet access on all segments? Is something like Internet Connection Sharing (ICS) running on PC2 or PC3?

[Reedy Boy]

Yeah, Its a very strange setup if it is routed/bridged via the different pc's...

[Yvarb]

late reply since i havent really had much time lately and didnt bother about ts too much, but with the holidays around i decided to give it another day.

1) Are you sure your users are connecting to your correct WAN address? You can verify this by checking your WAN IP at www.whatismyip.com. Even if you've checked before, check again. A "standard" cable connection has a dynamic IP which is subject to change at your ISP's whim.
im completely sure, my ip is semi dynamic, it only changes when i reset the modem.

2) Double-check your routing configuration. I'm sure you've checked it time and again, and are probably sick of checking it, but it can't hurt to look again. The most common mistake I see here is people accidently forwarding traffic to their router instead of the correct LAN PC. For added difficulty, if you don't have a static IP on your PC, the address chould change internally sometimes, thereby invalidating your port forwarding. Give your PC a Static IP, or a DHCP reservation.

www.portforward.com is a great resource for making sure you've configure your router correctly. It couldn't hurt to double-check your settings against what's posted there for your model of router.

im 100% sure i did it right here, my pc has a static IP adress, and for example i forwarded the FTP port (21) aswell, and that works as it should.

3) Software Firewalls. By default, these block inbound traffic to your PC - especially if that traffic isn't on the same subnet as your PC (IE - Internet traffic). This includes the Windows XP firewall, that was turned ON by default in SP2.
i disabled those.


as for the routing, ill try to explain it again.

Simple cable modem, not functioning as a router, just to receive the cable and give internet to a single point, which is
\/
The Router.
\/
PC1+2 are connected directly to the router, and a wire goes from the router
\/
Hub. this one receives internet, and is mostly used to extend the wires/give it to another pc aswell. Pc3 is connected to this hub, aswell as a wire that goes to
\/
Hub2. this is where PC4 + 5 + an xbox360 are connected to.

network works fine, and all have internet.

[WolfStar76]

Indeed, if those are simple non-intelligent hubs, I'll confess to being at a loss for where your connection is dying.

With no firewall on the PC, it should be as simple as getting the request to your router (via the WAN IP, which you've checked).

From there, we tell the router to give that request to the PC hosting the server (via the port forwarding - as you've done).

If there's no firewall on the PC to block that port request (and you say it's off) TeamSpeak should answer the request (as long as its running, which you've also tested).

Questions I have:

You have a working FTP server on your network - does that run as the same machine that's running TS Server? Just curious.

Have you made sure you can connect to TS across the LAN with your other PCs? That could help us pinpoint where the problem lies.

You've probably already answered these questions, but rather than re-read and further confuse myself, I'd appreciate it if you could answer them here. :)

[Reedy Boy]

You have a working FTP server on your network - does that run as the same machine that's running TS Server? Just curious.

I was just wondering that

Cause if it is the same PC, there is something strange with TS it would seem




(400th Post :))

[lharr2]

I'm new to all of this..(don't hold this against me:D ) I 'm trying to log into the csm server, but I get a "socket error" what am I doing wrong?..thanks for any advice for a beginner