Another "No Reply" error

[bhawes]

Ok before I began with my issue, yes I have read all the FAQ's and have searched the Forum for this problem, but have turned up nothing. If this is a repeat, then I'm truely sorry.

I downloaded the TeamSpeak Server Version 2.0.20.1 WIN32 it is running on Windows XP Pro (5.1 Build 2600) I also downloaded the service binary version 2.0.20.1 (BETA) for the same computer. I have everything installed and working, I have forwarded the correct ports and everything is working ( Tested this by someone out-of-state connecting to the server ) It was working great for about 6 months, then I get a call, telling me that this person is getting the "No Reply from server, Maybe the server is offline or maybe teamspeak is not running on it"

So I check on my server and TeamSpeak is up and running and I checked the Server Logs and there is no errors in there. So I tell him to try again and he did, same response, then I try to connect to it. (I have a DYNDNS account and that is what I use for the name of the server) so I start getting the same error. So I kept trying to connect using the dyndns name and no the IP and I got the same error. So I switched to the IP address and still same error. Switched back to the name and it worked. I'm connected

This is the problem that I'm having, sometimes it will connect and sometimes it won't, There isn't any error message from the server, and the only one that the client side gets is the "No reply from server" message. Before this problem started I didn't install or update any software or hardware. Just really strange that out of the blue it started doing this, so I unintalled it and deleted that folder, went into the regedit and made sure everything was out of there. Redownloaded and fresh copy of Server and Service, and did a fresh install. I'm still getting the same error message sometimes.

Any help or suggestions in this manner would be greatly appreciated !!


I found one post that had about the same problem that I'm having, but it doesn't offer me a solution, since I have DYNDNS already. Sorry for the re-post but the other post didn't offer any solution.

[WolfStar76]

A few things come to mind.

The first and foremost would be to simlpy reboot your router and/or modem if you haven't done so recently. Like any other computer, these devices can act wonky sometimes, but a good reboot can clear them tight up.

Secondly, and it *sounds* like you tested this to a degree, would be to verify that your dynamic DNS is going to your WAN IP. It's not completely unheard of for those services to get hung up sometimes. If you're using your router for DynamicDNS, however, rebooting the router might be all the fix you need.

Give those a go and let us know the results.

[bhawes]

I tried rebooting my router the first time I noticed the problem, I unplugged it and left it unplugged for about 30 mins. and it was still doing it (Sorry should have said that in the first post)

I can't explain it, but ever since I posted the first message, I haven't had a problem with it, so you might have been right when you said "verify that your dynamic DNS is going to your WAN IP" It might have been getting hung up on their end and wouldn't let it connect. Not really sure what's going on, but as of now it is working correctly.

Thank you very much for your advice.

[FlyNavy]

Does your router provide automatic updates to the DYNDNS site? Sometimes, when your WAN IP address changes it takes a little while for the router or the PC client to realize the change and forward the info to DYNDNS.