"Needs to be requested"

[ARCHI]

Actually I think that the main problem is dynamic IP. It shouldn't be dynamic, so I don't know what VPS provider you have but probably that's the reason.

When you start TeamSpeak it's running fine because users can join through IP, but after some time IP changes and it's not working anymore.

That's just my solution, I'm not sure if it's right but it looks like that's the problem.

Check your server IP f.e. at http://whatsmyip.org - it must be public IP, not private one. After TS3 server stops "working" re-check if it's the same. If it is then problem is somewhere else. If it's not - that's the reason.

[pillbox1234567]

In any event, the problem seems to be with the host service and not with teamspeak. Also, if you are only using the VPS for teamspeak you may consider just renting a teamspeak server.

[ARCHI]

Teamspeak runs fine on any VPS which contains at least 128 mb of ram and ~1 ghz processor. Bandwidth depends on users but f.e. mine server uses 1-2 megabits / second with 70-90 users online. But hey... if you're using windows environment then it's not enough... I don't even know why anybody needs GUI on server at all o_O

[SilentStorm]

Some (cheap) providers delay server rebooting to up several minutes. As part of an "premium" (and therefore more expensive) service, this delay disappears.

Oh yeah thats true, almost forgot about this... but this Delay (which many of them actually advertise as Feature since hey if you decide you didn't really want to reboot (after confirming you are sure about 5 times) you can still abort the reboot. -.-) is only present when using their web interfaces... you can always just shutdown -r -t 0 / shutdown -r now on shell without the delay.

I don't even know why anybody needs GUI on server at all o_O

You know how it is... You can just click something, no need to remember 50 different commands and about 20 parameters for each of them... you can just click it.. sooo much easier and faster u know
[/sarcasm]
PS: no I dont use GUIs on Servers...

[PhilWhite]

Unless your provider (as has been suggested) is delaying the boot process, it shouldn't take more than a minute or two on a Windows Server 2003 VPS. How much memory does it have and are there any errors in the event viewer after a reboot?

Also, if memory is limited, Window will shut down services to stop the system dying altogether.

The startup isn't a problem, and it's not closing any of my processes.

I'll try to explain... It's a bit of a confusion.
Keep in mind the OS is Windows Server 2003

Let's say I just started up the VPS and started the TS server. Most of the time, it works. People are able to connect, chat, and do the normal actions. After about an hour or two, everyone is disconnected. After this happens, I log into the VPS and start checking logs and the normal things. I right-click on the TS3 icon and scoll over WAN IP and it shows no IP. Instead it says "Needs to be requested". I click the request button and the TS3 doesn't respond anymore; I don't think this is important. What I find to be interesting is when I scan the default ports for Teamspeak3, they're all closed... But when I restart the VPS, the ports are open and things run perfectly.

A summary: After an hour or two of use, the VPS no longer accepts any connections whatsoever. nMap scan shows that absolutely no ports are open after TS3 disconnects, but right after I restart the VPS and scan, several ports are open.

I think it's a security issue... But I've no idea how to fix it.

If I had it my way, I'd have CentOS instead of Windows, but I didn't pay for the VPS...

[Air SeaTac]

I think you may be misinterpreting what nMap is telling you, when TS3 is running the ports will show as being open because TS3 is able to respond. When TS3 shuts down there's nothing to respond on those ports so they're shown as closed.

Out of curiosity, how are you running TS3 on the server? I also run a Windows Server 2003 VPS & set the TS3 server up as a service using srvany & instsrv, it's probably because of this I don't see the icon you mention.

[ARCHI]

I mentioned already possible solution. Check if you have static or dynamic IP on your server...

[Air SeaTac]

I mentioned already possible solution. Check if you have static or dynamic IP on your server...

If a VPS provider is issuing dynamic IP's I'd find another provider, dynamic IP's should never be issued on these sort of services

[ARCHI]

Yeah, but I can't find any other possible solution of being unable to connect to the teamspeak if machine and server run fine and this thing happens after some sort of time. It's definitely network problem.

[Air SeaTac]

The logs don't show anything interesting

Just taken another look at those screenshots & IMO they show something very interesting. Seems to me that Teamspeak can't connect to the accounting server to verify your license (what sort of license do you have?). Since it can't connect to the accounting server and verify your license it shuts your Teamspeak server down.

Not sure of the hostname / IP address of the accounting server, you can probably find that information on these forums. If it is a hostname it's looking for do you have DNS available to the VPS so it can resolve that hostname?

Edit: Not awake yet, I think normal behaviour when a license can't be verified is to fall back on the non-licensed 32 slot mode

[Air SeaTac]

Take a look at this thread for accounting server / shutdown issues, might answer your problem

[PhilWhite]

I'm using NPO License, Static IP (Obviously. I don't think I've ever seen a VPS with a dynamic ip D, nMap scans normally show any ports that are open on the VPS (Whether or not it's running anything). nMap is a security scanner in my opinion, but it's normally used to exploit open ports and gain access to remote PC's without permission. I normally get very accurate results from nMap. I've scanned before and after I've launched the TS server. I'd rather not do it again, because when I scan with nMap, all of the ports close up again.

I'm checking out the thread that someone linked me to. I really appreciate the responses. My VPS provider wouldn't help me.

I think you may be misinterpreting what nMap is telling you, when TS3 is running the ports will show as being open because TS3 is able to respond. When TS3 shuts down there's nothing to respond on those ports so they're shown as closed.

Out of curiosity, how are you running TS3 on the server? I also run a Windows Server 2003 VPS & set the TS3 server up as a service using srvany & instsrv, it's probably because of this I don't see the icon you mention.

How exactly do you go about doing that? I was looking in that area, but this is the first time I've had a Windows VPS.


~~EDIT~~

Did the suggestion on this thread:
I had this result: http://vvcap.net/db/GRP0-cGhI-NCn4kQEcea.htp
The console on the left is the server, the console on the right is my personal PC.

So the issue seems to be the connection to the accounting servers.

[Air SeaTac]

I'll repeat my question about DNS, does your VPS have DNS services available, either self hosted or provided by your host? Seems to me from your last screenshot that your VPS just can't resolve accounting.teamspeak.com, try doing a ping or tracert to any other hosts & see if the results are the same

[SilentStorm]

Check the DNS Settings on your Server and change the DNS Server to some proper Server like 8.8.8.8 for example, since obviously the one you are currently using on the server sucks.

[PhilWhite]

The only DNS that's ever been used is ts3dns.com

Screenshots in my post above show results from ping attempts.