TS Server no longer works behind new router.....any clues?

[LBScout_HA]

Ok guys:

I moved this last week, which means new ISP. My new ISP is blocking port 80 so I had to redo my website...........as if that was not enough I get all my servers set up and test them all.

TS loads on the server fine. I check to make sure it has the new IPs and it does. I start my client, and enter the new IP in the conection manager. and TS connects to my server.................

Then I get the "Your connection has been terminated"........or whatever that sexy little lady says, and I see the reconnect status box come up.

I try everything.........I check the router settings, ports are forwarded correctly............I am at a loss.

Then I go to the server log and find this message:

11-17-03 01:05:20,All,Info,server, Starting server with port: 8767
11-17-03 01:05:20,Error,All,server Server startup failed with port 8767, Exception: EIdSocketError .Socket Error # 10049 Can not assign requested address.


Now this is telling me ONE of a few things:

1. the port is not forwarded (but I know it is)
2. the IP the TS is connecting to is not the correct IP of the server. This might be the problem, but I have tried the bindip option in the server ini, and it did nothing but stop the server from connecting all together.
3. the port is blocked by my ISP ( I doubt this but hey who knows) so my next question is.........Where do I change the server loading port?

and has anyone else had this issue from a Network Everywhere NR041 router before?

Thanks for any help you can give me.

Scout

[Dummer Sack]

Since it worked for you bevore, I don't know if that is the problem but it is with many routers:

1. If you connect from within the LAN many routers do not support the redirection. So from within the LAN you have to use the LAN address.
If you want to test the server let someone form outside the LAN connect to it. I would recommend to try this first before changing something.

2. If you want to check your WAN IP just visit http://www.whatismyipaddress.com/.
The BoudToIP= is for binding the server to special interfaces. So if you have multiple netwok cards installed and you want the server only to be accessible from one of them you set the BoundToIP= to the IP of that network card. Setting the BoundToIP= to your WAN IP will most likely fail, since you WAN IP is an interface of your router not your TS server.

3. If the port is blocked by your ISP you can try to set it to another port in the web interface. Read The manual on how to access it. You have to be logged in as superadmin to change the port.

[LBScout_HA]

I have had my people try to connect from outside the lan and they get the same message. They log in and then they get the termination message.

I know what the WAN IP is. This is not an issue of not knowing how to set it up. It has been working for 2 years (with one Voice program or another).

By the way I listed the error I am recieving in the thread. I was under the assumption that someone who worked on this software would be able to explain the error..........I guess not.

Also the "Superadmin" function does not seem to work. The password does not function.........that was a secondary issue I was going to tackle later on.

One more thing I have read a thousand posts in this forum and ANY THREAD that asks a question about TS itself always gets one answer "Read the manual"................why is that?

If you can not help someone.......why even bother opening your mouth?

Some people may not be able to read the manual, some people may be Old, Young, technically disadvantaged, trying to help their child, maybe they do not read english, using a translator............for any number of reasons they may not be able to access the manual. Why when a person asks for help; can't someone just do that............give them help.

Scout

[Dummer Sack]

Here is an explanation for the socket error you get:

WSAEADDRNOTAVAIL (10049) Cannot assign requested address.

Berkeley description: Normally results from an attempt to create a socket with an address not on this machine.

WinSock description: Partly the same as Berkeley. The "address" it refers to is the remote socket name (protocol, port and address). This error occurs when the sin_port value is zero in a sockaddr_in structure for connect() or sendto().

In Berkeley, this error also occurs when you are trying to name the local socket (assign local address and port number) with bind(), but Windows Sockets doesn't ascribe this error to bind(), for some unknown reason.

Developer suggestions: Assume bind() will fail with this error. Let the network system assign the default local IP address by referencing INADDR_ANY in the sin_addr field of a sockaddr_in structure input to bind(). Alternately, you can get the local IP address by calling gethostname() followed by gethostbyname().

WinSock functions: connect(), sendto(), FD_CONNECT

Additional functions: It seems odd that the v1.1 specification doesn't ascribe this error to the function bind().


As I explained in 2. that means that you have set the BoundToIP= in the server ini to an invalid IP. Leave it open so that the server can start correctly.

Since you did not post your server version I can only guess what your problem with the superadmin is.
In the older versions there was a checkbox that you have to ckeck for superadmin login. In the newer version there is a link on the login page that brings you to a seperate login for superadmin.

[LBScout_HA]

I am still confused as to why it JUST started to do this?

The Server has been running with THIS version of TS for several months the only thing I changed was my geographical location. And I had to switch my router.

I updated the IP addresses to reflect this change.......and the router was almost exactly the same kind as the old one.....this is a real head scratcher.

I figured out what was wrong with the superadmin issue and I fixed that. I changed the UDP port, and I still get the same termination message...........

Well I installed it on another machine outside the LAN, and it fired right up......so I guess I need to dig a little deeper into the settings of this new router.

Thanks

Scout

[vsteel]

I also have the NR041 switch/router and I have the same problems. Here is my situation.

I have the latest teamspeak server software 2.0.19.40
I am running windows XP Home edition.
For the testing I have all firewalls turned off. ( never run XP and I have zone alarm ver. 4.5.530.000 shut off)
I forwarded port 8767 and used UDP not TCP.
Per the router instructions I turned off DHCP (you have to turn that off to get the port forwarding to work)

I have even setup my server computer up in the DMZ with still no luck. I can see and get on the server inside my LAN, just not outside of it. People log in and then get the "timed out" message. I have tried and tried to get this to work. I just can't seem to get a server going. I do have the latest greatest firmware in the router also.

I have no problem getting on other people's servers, I just can't host a server.

I am just thinking that the NR041 is not compatable with teamspeak server or I have totally missed something.

[Dummer Sack]

The timeout message does mean that they con connect to your server but get a timeout afterwards. The message they should get if they cannot reach your server is the following: "No reply from server
Maybe the server is offline or maybe teamspeak is not running on it"

Please ask a friend to set his client to debug mode (in the options) and sent his TSClient.log to you (after he tried to connect). Then post the log here.

EDIT: Also post a server.log for a connection try.

Possible causes of the problem:
I have heard reports that ZA sometimes even blocks ports when it is shut down. Somtimes it even blocks after the deinstallation if that is not going correctly (Only solution was to install and deinstall it again).
Another problem can be your router. Make sure that you have the latest firmware installed on it.

Read more about the timeout problem here (http://www.teamspeak.org/forums/showthread.php?s=&threadid=9114) and also search the forum for it a bit.

[vsteel]

I will try and get the requested logs posted here.

I have searched the forums before I posted but nothing helped.

I do have the latest firmware for the router.

If zone alarm was blocking the ports would someone trying to log in still see the server before they timed out or would they not see the server at all?

[Dummer Sack]

Originally posted by vsteel
If zone alarm was blocking the ports would someone trying to log in still see the server before they timed out or would they not see the server at all?

Yes it is true. But I personaly do not trust ZA with what it is doing in the TCP/IP network stack (Since I have seen the thing with the deinstall). So maybe it is just messing around with the packets.

[LOAM]

have a look here, someone with problems that maybe be relevant

http://www.broadbandreports.com/forum/remark,8348955~root=equip,16~mode=flat

[Dummer Sack]

Yes right.

Broadband Reports is a great site for ppl with router troubles.
Maybe we should redirect all people with router problems to this site.