PDA

View Full Version : server on localhost -> no reply


Pidsa
23-07-2003, 19:18
Hi. I am hosting a TS2 Server on my own PC. I am behind a router.
Everyone from the Internet can connect (because I forwarded port 8767).I can also connect but only by using my internet IP. As the server is running on localhost I tried to enter the following IPs to connect to the server (so I would not have to re-enter my own internet IP [which is not static] everytime I connect with a new one) :
127.0.0.1
localhost
192.168.123.104
127.0.0.1:8767
localhost:8767
192.168.123.104:8767

All of them result the following error message (client) :
No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it

23-07-03 20:11:24,368,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait

I used the search function and found several topics regarding my problem, in most of them is recommended to try things like localhost and 127.0.0.1 but as you see I tried those and they do not work for me. Its interesting to see that the connection to localhost in one moment works and then suddenly does not anymore ( = I was able to connect once and tried to reconnect , without success ). However most of the time it does not work.

And yes there is a server running and no there is no firewall.

Teamspeak Version :
- Server 2.0.19.40
- Client 2.0.29.47

OS:
- Windows XP Service Pack 1

Soundcard Driver:
- Creative AudioPCI (ES1371,ES1373)(WDM)

Router:
- SMC Barricade

DirectX Version:
- 9.0a



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
BoundToIp=
[WebPost]
AdminEmail=na
ISPLinkURL=na
ISPName=Private
ISPCountryNumber=4428
Enabled=1
PostURL=
ListPublic=0
[log]
access=0

Kim Ethan
24-07-2003, 04:15
I had the EXACT same problem and uninstalling the client then reinstalling it worked for me.

Hopefully this will work for you.

Kim Ethan
24-07-2003, 05:02
damn, it still does the same thing, even after reinstalling the client. It's probably a bug because i tried EVERYTHING, and other user can connect fine to my server except myself.

i'm not behind a router or a firewall by the way.

guldi
24-07-2003, 06:45
strange ?? I never had probs in LAN connections...

- just to make sure, you can ping the LAN IP's fro mthe same PC ?
- you could play with the bindtoIP (server.ini) and bind the server on to your LAN IP of the TS server PC.
- 192.168.123.104 Is the IP of your PC where TS is running on it (not the IP of the router) ?
- can you connet to the webadmin ?

Pidsa
24-07-2003, 15:08
damn, it still does the same thing, even after reinstalling the client


Same here.


- just to make sure, you can ping the LAN IP's fro mthe same PC ?
- you could play with the bindtoIP (server.ini) and bind the server on to your LAN IP of the TS server PC.
- 192.168.123.104 Is the IP of your PC where TS is running on it (not the IP of the router) ?
- can you connet to the webadmin ?


- Yes, I can ping the LAN IPs cause they are all mine and I can also ping the router and other users in LAN.
- I already tried to bind it to localhost and it did not help against the problem but only caused that Internet users could not connect either.
- 192.168.123.104 is my LAN IP , the router's IP would be 192.168.123.254
- Yes I can connect to the webadmin


A few minutes ago I was able to connect to localhost from here 2 times , and again another reconnect ended up at the same error. Apparently the error depends on the server's mood as I can not see a system in that behaviour.

BATMAN66
24-07-2003, 17:33
I get the same error "No reply from server Maybe the server is offline or maybe teamspeak is not running on it " i have tryed evrything dunno whats up with that but it sucks,but if i dont use it for aday it will work its wierd,i tried uninstalling updateing ip add,first time i had problem with TS by the way its great so if theres any new ideas on how to fix would be greatly appreciated.

Kim Ethan
25-07-2003, 17:27
yeah it worked the next day for me, and today i tried again. I logged in once, then diconnected, then tried to reconnect and it failed 2 times, then i tried again and it worked. Strange.