The Server that is only Half There

[coyote]

Alright now that I got your attention, I have created a TS 2 Server(duh) and some of my users / friends cannot sign on to it. There are three people that normally access this server me ( admin ), friend one, and friend two. Now I did all the port forwarding and such because I have a D-Link DI-604. And it works great for Friend 1. He has never had a problem signing on to my external IP. I can sign on to either my internal or external IP with out a problem.

Now hear comes the big mystery, I have Friend 2, he gets on the first time no problem we all havea great time, but then 2 days later or so, he attempts to get on and he can't both me and friend 1 can still get on fine. So I do a little research, and finally decide some detail that really does not matter and he gets on fine again. But another two days go by or some unfixed amount of time longer than 5-6 hrs normally, and he cannot get on anymore.

In fact the only way he can sign on now is if I restart both the TS Server and my Router (Every once in a while I only have to reset one). I have no software firewall, I have no auto-virus protection running in the back ground. Its a dedicated Server that I have TS running on, and finally both Friend 1 & Friend 2 has approximately the same configuration. I looked everywhere using every keyword I can think of for the last month. I can no longer keep restarting the server it takes too long on my end now.

So any one know what is wrong? Thanks for any suggestions you might have. P.S.: Read the FAQs is not a suggestion I already have been there so please don't send me back.

Thanks Again,

Coyote

[guldi]

and have you tested the "boundtiIP" from the FAQ ?

I had such a problem once as well with a friend. Looked later that in a periode there were some ISP interconnection problems as some games created problems as well.
Might as well be a problem of your two routers (firmware update)

[coyote]

Sorry I not sure what you me by "BoundtiIP" I searched for it in the FAQ Forums, and nothing came up. Did you misspell it? Also, I once tried to add

BoundToIp1=128.61.59.11 but that definitely did not work. Maybe I have misread something, I am quite confused as to what I am bounding, and why does it the bounding work to begin with but then not later?

[coyote]

I am still having this problem where my friend has like a 50/50 chance of getting in. Anyone with any ideas? Sometimes he can and sometimes he cannot access the server and this is with the server being up 24/7 for the past week.

[guldi]

- tested when binding the server to it's LAN IP ?
- Does your friend get a timeout (As described in the FAQ) ? Tested the debug mode ?

[coyote]

guldi your still not making sense no he does not get a timeout that I am aware of, and now there are two ppl with the same problem, and they both have different routers with no software firewalls. All it shows is the no reply. As if the server is not up. If they reboot there computer it can connect. And exactly what timeout are you talking about in the FAQ? Please copy and paste the link because I have yet to find this mystery FAQ that solves all.

[m&m's]

http://forum.goteamspeak.com/showthread.php?t=19293
i beleave this is the FAQ he's posting about

[coyote]

Okay thats one I been looking at I am trying the whole DEBUG one and we will see how long that lasts as a fix.

[coyote]

Well DEBUG mode still finds the problem here is the client log:

---------------------------------------------------------------
-------------- log started at 09-07-05 10:31 -------------
---------------------------------------------------------------
09-07-05 10:31:33,936,DEBUG,All,Startup,Client version 2.0.32.60
09-07-05 10:31:33,936,DEBUG,ProcedureInfo,Client Open,Creating and starting threads
09-07-05 10:31:33,936,DEBUG,All,TDSoundIn.Open,opend direct Capture 8bit=0 , 11khz=1
09-07-05 10:31:38,936,DEBUG,ProcedureInfo,Client Open,host ???.??.??.??resolved to ???.??.??.??
09-07-05 10:31:38,936,DEBUG,ProcedureInfo,Client Open,Send LoginStep1
09-07-05 10:31:38,936,DEBUG,ProcedureInfo,Client Open,Waiting for LoginStep2
09-07-05 10:31:41,936,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait
09-07-05 10:31:41,532,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
09-07-05 10:31:41,936,DEBUG,All,TMainForm.FormDestroy,FCall backSynchronizer.Free done
09-07-05 10:31:41,936,DEBUG,All,TMainForm.FormDestroy,FSoun d.Free; done
09-07-05 10:31:41,936,DEBUG,All,TMainForm.FormDestroy,FSoun dNotifications.Free done
09-07-05 10:31:41,936,DEBUG,All,TMainForm.FormDestroy,FWave Saver.Free done
09-07-05 10:31:41,936,DEBUG,All,TClient.Destroy,active FClientReadThread.waitfor
09-07-05 10:31:41,1192,DEBUG,All,TClientReadThread.Execute, leaving
09-07-05 10:31:41,936,DEBUG,All,TClient.Destroy,active FClientReadThread.freeing
09-07-05 10:31:41,936,DEBUG,All,TClient.Destroy,active FClientReadThread.Freed
09-07-05 10:31:41,1940,DEBUG,All,TClientEventThread.Execute ,Close confirmed
09-07-05 10:31:41,1892,DEBUG,All,TClientWriteThread.Execute ,Close confirmed
09-07-05 10:31:41,936,DEBUG,All,TClient.Destroy,active closed buffer
09-07-05 10:31:41,936,DEBUG,All,TClient.Destroy,active FClientWriteThread.Freed;
09-07-05 10:31:41,936,DEBUG,All,TClient.Destroy,active FClientEventThread.Freed
09-07-05 10:31:41,936,DEBUG,All,TClient.Destroy,active destroyed buffer
---------------------------------------------------------------
--------------- log ended at 09-07-05 10:31 --------------
---------------------------------------------------------------

The IP is in there I just did not want to send it out. Any rate the IP address is not the problem because multiple others can connect without a problem.

[m&m's]

do a fourm search on TDICallBack.execute

[coyote]

Sorry for the multiple posts in a row but I keep learning more and more prior to any help. Basically I tried to switch my server to Static DHCP instead of Dynamic. But the problem still happens, and seeing as its only a few clients I really dont think its a refresh problem with the router versus TS Server. I think the problem lies in what the client is doing, but nothing makes sense why would a client not see a server at one place and another person at the same time connects just fine?

[m&m's]

as dns updates around the world , each ISP updates at diferant times ISP 1 may get the info 10 mins after it gets refreshed ISP 2 may have gotens its new list 1 min befor the last change and may take it longer to get the next update ISP may update on the top of the hour etc......

[guldi]

just a guess, can your friend connect after he deletes the hidden teamspeak.conf file ?
Can he connect to other TS servers ?
Did you tested with binding the server to it's LAN IP ?


To me this sounds like an ISP / router problem maybe combined with the (high) timeout sesitivity of the current TS client

Some people reported that older clients aren't that timeout sensitive. You might want to test an older clinet from the FTP server. A feedback here would be very welcome

[Funeral]

I am experiencing the same problem.

I set up a TS server for my clan members @ my office on a static IP server. This server is a "honeypot" and as such has no firewall. There is no configurable router in front of it.

LAN users can stay connected indefinitely.
Some WAN users can stay connected indefinitely.
Other WAN users get disconnected at random... and cannot reconnect for anywhere from 5 minutes to 2 hours. Deleting teamspeak.conf allows them to reconnect immediately.

Still... having users delete teamspeak.conf every couple hours when they get disconnected... doesn't seem like a solution.

[mage150]

Hi I am having this same exact issue as listed in this thread. My log even gives the same error.

I am running a dedicated TS box, it works for a while and than all of a sudden 50% of ppl can connect and 50% cannot connect to my TS server.

I have been speaking with pwk on the IRC channel and we could get a connection on time and than the next morning it was back to the same thing, left untouched certain people can no longer connect while I am a few others can.

Currently I cannot get my UDP test on my server port (Which I set to 9999) to work on the TS2 connection test.

I tried bound2ip and it does not help.

I turned off IP Recognition, does not help.

I also have a DI-604 router, which which may making me think it may be router related, however it does the SAME thing with my linksys BEFWS11 router, so I think not.

Any insight would me nice as to a solution.