Client connection problems

[Civilian]

Ok, I'm having trouble getting a client to connect to my server.

-I'm behind a Netgear router

-I have Norton Firewall but I've disabled it

-I can connect using a client on my external IP and my static router IP

-I have Microsoft Anti-Spyware but I've shut it off

-I have turned off IE pop-up blocker. I don't have any anti-spyware, software firewalls, or pop-up blockers running.

-I've assigned a static IP to the server computer

-I've forwarded the proper ports using the proper protocols on my router/firewall

-I've even gone into webadmin and assigned an account for the client

-The client is attempting to connect on my external IP on port 8767. I've also tried port 8768

-The client is getting the error message "Got a bad response from the server"

-The client is using RC2. The server is RC2. They were both just downloaded.



Is there anything else I can try? Help is greatly appreciated.

[guldi]

1) inside your LAN you should only use the LAN IP (as statet in the FAQ "no reply")

2) Since you can use your external IP to connect to you server, one should assume the port forwarding is working correct.
so what error message does your friend gets ? Coudl it be that it is described in the "no reply" thread ?

[Civilian]

I connected using my external IP to test it out, but, now I'm just using my 192.168 internal IP.

I went through the "No Reply" thread but there wasn't anything new there.

I have 8767 and 8768 on both UDP and TCP and the other 2 ports are on TCP.

The client still gets this message:

[23:53:09] Connecting to xx.xxx.xxx.xxx:8768
[23:53:09] Got a bad response from the server

I've also tried port 8767 with the client.

[Civilian]

Ok, I was able to have another person connect, which leads me to believe that the problem is on the client computer. Is there anything that a client could be doing wrong that might prevent connection to a server? Everything I've read so far says ports do not need to be opened on the client computer. Is this true? The client is running Windows Firewall and has already gone in and configured it for Teamspeak. No port forwarding has been done yet, though.

[guldi]

In the past, incompatible client - server version had been the main root for this error msg. But since the latest ver are out quite a while, I guess this is not the problem in your case (if you use the latest ver. you're fine) ?

- Not correct configured firewalls have been a reported cause for this error (so I'd try without the firewall for testing)
- Just a guess: there's a FAQ thread dealing with "not all can connect". May this one be helpful ? Pls, post back would be interesting to get the reason for this error !

[Civilian]

Is this the thread you mean?

http://forum.goteamspeak.com/showthread.php?t=19166&highlight=clients+connect

I just happened to upgrade all my Norton Software and while I had Internet Security uninstalled I decided to try again, with no success.

I haven't gotten around to trying anything else yet, but, I thought I'd add that the client computer is behind a wireless router. No ports have been forwarded on the router's firewall either. It's on uPnP I believe. The client computer is not configured to have a static IP with the router; it's having everything autodetected.


So, things I have yet to try are:

Debug mode in TS client

Static router IP and DNS IPs for the client computer

Disabling Windows Firewall and setting the router to DMZ on the client computer



What does debug mode do, anyway?

[guldi]

no, actualy I meant this thread (http://forum.goteamspeak.com/showthread.php?t=6418)

Debug Mode:
increases the log verbosity and it seems as if the timeout would (slightly) increase. Several timeout issues could be solved by using the client in the debug mode.

[Civilian]

I tried this as mentioned in that thread:

1:
In server.ini in the section [Main Config] there is an option BoundToIp=
Set that to your server ip. For example: BoundToIp=213.202.254.115
You don't need to specify a port.


It didn't work. Not only that but I was also unable to connect to the server. I tried using my internal router IP. That loopback IP, and my external IP.

[guldi]

you do not need to specific a port (this is a matter of the IP). BUT: you don't want to bind it to your external IP ! Bind it to the LAN IP (not loopback) of the PC hosting the TS Server.
213.202.254.115 is a WAN IP and since you're behind a router (with NAT I expect) this is most surely NOT the IP your TS server is running on.

If your buddy still gets "bad response..." I can only assuem a firewall / router problem on his end. Can he connect to other TS servers ? Is he the only player login in from WAN and having this problem ?

[Civilian]

Ok, This is what I've tried:

I entered in BountToIP=192.168.xx.xx in the server.ini file, with no port.

I also tried disconnecting my router and shutting down my firewall at the same time that the client disconnected her router and shut down her firewall. I tried this with "Warning" mode and "Debug" mode. The client got the exact same error. The client tried downloading the software again. No change.

The client tried pinging the server without firewall, with firewall, with firewall and router and all packets went through.

I also tried pinging the client while all firewalls and routers were removed BUT, I could not get a single ping through. 100% Loss. I find this odd since I can have a voice/video/text conversation over MSN.

Strange...

[Brain]

I entered in BountToIP=192.168.xx.xx in the server.ini file, with no port.
That would be "BoundToIP"...

[Civilian]

I didn't really type it in. I just entered the IP into the field.

But... it's a moot point.

I figured out the problem. There was a copy of Norton Internet Security running on the client computer which wasn't showing up in the system tray from startup and the person on the client side didn't know it was installed and set to block Teamspeak, outright...

I will go off and shoot myself now.

After I am done you may shoot me too.