Results 1 to 5 of 5
-
15-06-2005, 06:34 #1
-= TeamSpeak User =-
- Join Date
- Jun 2005
- Location
- Montreal
- Posts
- 2
Two specific users can't connect to my server
I'm using TS version: 2.0.20.1 Win32, on standard port 8767 with a Linksys Router
I can connect fine to it, so can 20+ other users
Those two users once connected to it, now they can't anymore. The two users are two brothers sharing a connection through a hub (not a router) with distinct external IP addresses.
I've checked :
-Firewalls, they don't have any
-Unmapped domain name, had them try external IP address directly, doesn't work
-Added the machine internal IP to the BoundToIp1 line in the server.ini file
-Cleared all the IP bans just in case
Now, they also tried to connect to other TS servers and they CAN connect to them.
So, from my analysis, problem is not on my end since all other users are connecting fine, and it doesn't seem to be on their end since they can connect to other servers too. So, logically, problem should be in the communication... I thought maybe the 8767 port was blocked by the ISP (which is doubtful since they are on the same ISP as I am and from my experience they only block ports for requests incoming from other ISPs)
But nevertheless I added a 2nd external port routed to the same 8767 internal port on my router and had them try to connect, still to no avail.
Oh, Also forgot to mentioned that during no try did the server log list their incoming connection request (and the setting is on, I see the others)
The error message they are getting is (don't remember the number right now) Can't connect - maybe the server is offline or Teamspeak is not running on it.
Anyone have a hint of an idea for a direction to me look into? I'm pretty out of ideas as it stands, the only thing that still bugs me to look into is as to why the two of them cannot connect if they don't share a network but only a hub to a direct internet connection, but even then, they still can connect to other servers so I don't think that path will lead me anywhere.
Thanks in advance for your help,
Sirius
-
15-06-2005, 15:38 #2
Have them copy a traceroute and post the results here. Might be interesting to see where the problem is going astray or getting lost.
-
15-06-2005, 22:11 #3
-= TeamSpeak User =-
- Join Date
- Jun 2005
- Location
- Montreal
- Posts
- 2
Traceroute gives a timout after the first hop and ping doesn't answer :/
I've had another user (who is able to connect) on the same ISP try to traceroute and ping me and his traceroute also gave a timeout after the first hop and he couldn't ping.
I can't traceroute nor ping those users myself, but I can traceroute public known servers.
-
16-06-2005, 10:46 #4
-= TeamSpeak Guru =-
- Join Date
- Aug 2002
- Location
- Switzerland
- Posts
- 8,182
1) sharing a connection through a hub, I assume you mean a modem or a re they directly conencte with their hub to the LAN of their ISP ???
2) all what you desribe sounds like an unstable connection (once they could connect, they get timeouts with ping).
- did they tested the TS client in the debug mode ?
- did you tested binding your server to it's IP (see FAQ thread not all can connect)
-
19-06-2005, 22:49 #5
-= TeamSpeak User =-
- Join Date
- Jun 2005
- Location
- OR
- Posts
- 2
not all can connect
I am currently having the same issue, I am hosting a server and many people can connect, but a select few cant.
I was able to experiment with it with the help of somone who couldnt connect, he was eventually able to connect after disabling his router.
as far as I am to understand, shouldnt this work out alright? considering its just having to connect through that single port, and its open on both ends, no firewalls of any sort when trying to connect, port forwarding on server side, everyone else can connect, but that select few can, but very rarely. the other times it just says
"No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it"
maybe its a different problem but it does look closely like the one you have, and the only way I was able to come somewhat NEAR an answer was with one person, and it could just been that persons rare chance to actually connect rather than it being his router being turned off... not to mention your friends dont have routers.... have they tried only having one comp plugged into the net instead of using hub and then see what happens?
Just a thought...
anyways, I hope somone can help with this issue, it is getting quite bothersom to deal with.
Also, I've just spent about an hour and a half looking all over this forum looking for the so called threat you speak of explaining this issue. Everywhere I look all I see is you saying there IS one, not where it is. Could you please give me a link to this thread you speak of?Last edited by Score313692; 19-06-2005 at 23:10.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
Router problems
By bigteam0385 in forum [TeamSpeak 2] Server SupportReplies: 4Last Post: 24-05-2011, 10:53 -
Administration page
By bigteam0385 in forum [TeamSpeak 2] Server SupportReplies: 5Last Post: 16-01-2006, 22:00 -
server on freeBSD 5.3
By Dulithol in forum [TeamSpeak 2] Server SupportReplies: 0Last Post: 01-02-2005, 21:36 -
Can't Connect on Internal Server
By Erdrickk in forum [TeamSpeak 2] Client SupportReplies: 0Last Post: 13-08-2004, 16:06 -
Server Crash (no specific time) 10004
By NxN_Slite in forum [TeamSpeak 2] Server SupportReplies: 2Last Post: 15-10-2003, 16:47


Reply With Quote


