I haven't seen this problem (and I have LOOKED)

[Degas]

I have searched for 2 days, since I don't want to waste anyone's time here. However, I can't find this problem in any post, or in any FAQ (although the FAQ is kind of useless since the server revamp).

We have been running our Clan TS on a commercial TS server for about a year now. It is running on port 8855.

I leased some beefy (20GB storage, 120GB throughput) shared server space and had SSH enabled. I installed the latest Linux TS Server software (Version: v2.0.r20.b1 Linux). Didn't have a problem with the install, thanks to the tutorials found here :).

We are all running Client vsn. 2.0.32.60. Everyone is still able to log into the TS server running on port 8855 at the commercial site. However, here is the problem:

When I create a server on the new webspace with UDP port 8855 as the address, only certain people can log in. So far, we have an Australian user and a Norwegian user who can log into the server. Everyone else is getting the message:

"No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it"

We have tried a large range of port settings, still with the same results.

I've seen a LOT of posts and such about people not being able to log into their TS server, and in those cases it all boils down to the firewall/router settings. However, those of us not able to log into the 8855 server at the new site CAN log into the 8855 server at the old site. That is definitive proof that firewall/router settings are not the issue. And, since we have some users who can log into the port 8855 server at the new site, while others cannot, it has me totally stumped, along with 2 full-time IT support guys who are in our clan.

Incidentally, so far all the people unable to log in are in the US. The new server is hosted by Canaca.com in Toronto.

This one has us pulling our hair out! If you can help, the beer's on me!

EDIT: Running the client with debug logging turned on, here is the error message those unable to connect are generating:

"11-09-04 10:30:48,1776,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait"

Also, checking admin on the commercial TS Server we are leasing, I see that their server version is 2.0.19.51 . Not sure if this is relevant, but it IS one thing that differs between the two.

[Degas]

Hello? TS gurus! Anyone home on this one? You guys are our only hope :)

[m&m's]

the new hoster have it's port fowarded for ya ? on there router ? and are your users placing the port # after your ip , if not it sends info on default port 8767

[Degas]

Thanks for the reply.

I can't answer the question about the new host having the port forwarded for us. All I can tell you is that at least 2 users have no problem logging into the TS server on that host. That leads me to believe there is no problem getting into that port at my host.

Yes, we are entering the port numbers correctly. We have even tried many other ports with exactly the same results. The Aussie and Norwegian users can log in and talk on every one of the servers, and our other users get the error message that the server doesn't exist or doesn't appear to have teamspeak running.

We have double- and triple-checked that we are all trying to log in EXACTLY the same way. I have even created admin accounts on the servers and tried to log in that way with no success. I can't log into the servers as superadmin either. I don't get an unsuccessful login message, my client doesn't even think there is a server running.

It's a communications problem, but it's a very strange one. The US people that can't log in are from the Seattle area, the New York area, the Dallas area, the Mobile, Ala. area, etc. We are using separate ISP's, connection methods, and even internet backbones. On the same domain, we can visit the web pages just fine, including posting on our forums, uploading to the FTP site, etc.

We really need some help on this one. One reason I leased this server space was because it saved me money with the ability to run a TS server, rather than paying to rent space for it.

I'm going to try some telnet stuff, just to see what kind of message I get when trying to connect to the ports where the server is running. When I get more info, I'll post it.

[Degas]

OK, one of our IT guys finally figured it out.

We installed the TS software on a shared server. The host has several different IP's assigned to that server. What we had to do was edit the [Main Config] section of the server.ini file inside the tss2_rc2 folder on our server, and bind the server operation to our specific IP address.

Old version:

[Main Config]
BoundToIp1=
ExternalIPDectection=1
HTTPServer Port=14534
HTTPServer Enabled=1
DateTimeFormat=dd-mm-yyyy hh:nn:ss
TCPQueryPort=51234
AllowedClientNameChars=
DisAllowedClientNameChars=()[]{}

New version:

[Main Config]
BoundToIp1=XX.XX.XXX.XXX
ExternalIPDectection=1
HTTPServer Port=14534
HTTPServer Enabled=1
DateTimeFormat=dd-mm-yyyy hh:nn:ss
TCPQueryPort=51234
AllowedClientNameChars=
DisAllowedClientNameChars=()[]{}

You'll notice there is now an IP plugged into the "BoundToIP1=" line. This is what fixed our problem. We just made sure we plugged in the static IP of our server and we are now up and running with no problems.

Thanks, M&M's, for the effort :)