Server Restart, UDP problem

[stringseagle]

I run a TS2 server on my pc... for my friends and I. It runs great... rarely a problem. However, EVERY time i reboot my computer and the server starts up... i cant connect. UDP fails the TS2 test. If I go into server administration, and change the port from 8767 to 8766... it connects fine.... then next time i reboot.. i have to change it back to 8767 for it to work..... what gives?

[ANR Daemon]

Check if you have more than one server instance running at times.

[stringseagle]

ok new discovery with this problem, btw.. no 1 server running at any point in time.


My friends will be connected to it and talking to eachother when i reboot my pc.. (server is on laptop) when i come back to connect.. i cant get in...

[14:22:25] No reply from server
Maybe the server is offline
or maybe TeamSpeak is not running on it

lies... im lookin at it running..8767 port... im talkin to my friends through xfire who are on it... or other times ill restart the server with 8766 and ill log on.. they get back on ... knowing i have to change the port sometimes. i dont understand it at all.. when i do the server test from http://ts2test.planetteamspeak.com/?page=step1 it shows the server doesnt exist in any way shape or form.. but they are on it... and i cant connect until i change the server port.

[ANR Daemon]

Then fix your networking and firewall configuration.

[BHKai]

Does it work if you change it from 8767 to 8766, save, then change it back to 8767 without rebooting?

[stringseagle]

Daemon, if retarded answers like that are all you have to contribute, please do not post in my thread. if you want to help, help. saying fix your stuff... doesnt help in the slightest. and to the BHKai... yea it does work when i do that. but anytime i reboot my pc, i have to alter the server again to be able to connect to it. and for further clarification, since the original post i have put the server is on my laptop and i dont use it for anything but ts2. my pc that i connect to it with is a separate machine, though on the same network. The same exact problem still exists.


BTW: my computer is in the DMZ of my router and there is no other firewall active on my pc.

[BHKai]

Are you using wireless?

How does the server startup? Do you have it as a scheduled task, service, or do you just open it up when you log on?

[Tomas]

stringseagle,
1. what is examctly version of your teamspeak server you had installed(from installer and check that by looking in files maybe readme will have mention about version.
2. then what version is the server running?
3. you said daemon. do you have it installed as service?

if the trouble is what I think then you already know what is the cause after checking above.

yea it can be network issue or something thro.
4. as who are you starting teamspeak server? {username permissions to the teamspeak folders? administrators?}
5. did you ever set any limits to mem, or anything for that user or pc??
6. did you folled with some restrictions on pc?
7. what exactly is urs setup? Windows, what kind? does pc firewall have a name and version??
8. server log check(and post here few sections).
9. ...... propably remote includessssssssss. btw, what exactly do you mean by server restart? PC/HW one or just a soft/Program one? cuz that can make a hell difference if you missuse the term.

[stringseagle]

No, not using wireless. The server is on my laptop and I start it manually.

1. both are current... updated executables.
2. ""
3. I said Daemon, because I was replying to the user named Daemon....
4. Admin on both.
5. No.
6. No
7. Windows XP Home, nofirewall.
8. Be more specific on what "sections" you want posted, posting random things from the server log doesn't seem to make sense.
9. When referring to my PC, I mean reboot. When referring to the server I mean restart(software) as the terms imply. Again, my ts2 server is on a separate machine(laptop) that I use ONLY for the TS2 server.

[Tomas]

stringseagle,
....
8. server log check(and post here few sections).
....

I guess there is nothing in logs which could give some light to the problems during times and around the times when you experience them.

did you used boundToIp in server.ini ??