Help! TS Server no showin ip

[Gbcbsfnst]

umm my windows Teamspeak server is now only showin local ips and now only i can connect... any one know why and how to fix it... please?

[Dummer Sack]

The display of the external IP is just a feature that has no effect on the functionality of the server. Sometimes this feature does not work.

If only you can connect then maybe you are using a router or microsoft ICS. Do a search for port forwarding here in the froum. Also if you have a firewall you have to open the ports for TS. The ports are in the server manual and the FAQ.

[Gbcbsfnst]

umm when i said only i can connect i didnt mean.. i think i can only connect b/c it isnt showin the globe ip i mean other people tried and coudlnt connect. and FYI this has been only been happening recently my TS Server was up and running fine before and other people were coming...

[Gbcbsfnst]

And also i let my firewall let the server use/connect too/through all ports..

[guldi]

again, that the global IP is not displayed has NOTHING to do with the functionallity of TS (by the way, the feature seems to work again as it shows both my LAN and WAN IP CURRENTLY).

If people fro mthe WAN can not join, then you changed something in your settings (firewall, port forwarding). Maybe you use DHCP (which is a very bad idea when running server) and the IP has changed ?

with the given info, we can only guess and assume, something not very comfortable to help you further :(

[saintchuck]

Browse to www.myip.com.

This will show your global IP, give this to your friends and you should be in business.

[Gbcbsfnst]

---------------------------------------------------------------
-------------- log started at 05-12-03 12:46 -------------
---------------------------------------------------------------
05-12-03 12:46:54,ALL,Info,server, Server init initialized
05-12-03 12:46:54,ALL,Info,server, Server version: 2.0.19.40 Win32
05-12-03 12:46:54,ALL,Info,server, Starting server with port: 8767
05-12-03 12:46:54,ALL,Info,server, Starting server with port: 8766
05-12-03 12:46:55,ALL,Info,server, Server init finished
05-12-03 12:47:00,ERROR,All,frmMain, unable to detect external ip


Arg, you told me it was just a feature...

[guldi]

Yes, it IS JUST a feature absolutly not necessary to run a server.
the error is showing you that at the moment the feature is not running.

Do you get it now ?????????

[<CK>Degan]

Hmm...everything's been runing fine untill I restarted my PC. Note: *Nothing* changed with my router, I'm NOT runing a firewall. You say that finding the external IP is just a feature but when you look at the log I pasted here it seems that TS isn't doing something.

I'm at a loss...any ideas?


-------------- log started at 05-12-03 13:40 -------------
---------------------------------------------------------------
05-12-03 13:40:17,ALL,Info,server, Server init initialized
05-12-03 13:40:17,ALL,Info,server, Server version: 2.0.19.40 Win32
05-12-03 13:40:17,ALL,Info,server, Starting server with port: 8767
05-12-03 13:40:18,ALL,Info,server, Server init finished
05-12-03 13:40:21,ERROR,All,frmMain, unable to detect external ip
05-12-03 13:40:42,ERROR,All,frmMain, unable to detect external ip
05-12-03 13:41:17,ERROR,All,frmMain, unable to detect external ip
05-12-03 13:42:02,ERROR,All,frmMain, unable to detect external ip
05-12-03 14:57:49,ERROR,All,frmMain, unable to detect external ip
05-12-03 16:41:50,ERROR,All,frmMain, unable to detect external ip
05-12-03 16:41:54,ALL,Info,server, Server shutdown initialized
05-12-03 16:42:01,ALL,Info,server, Server shutdown finished
---------------------------------------------------------------
--------------- log ended at 05-12-03 16:42 --------------
---------------------------------------------------------------
---------------------------------------------------------------
-------------- log started at 05-12-03 19:25 -------------
---------------------------------------------------------------
05-12-03 19:25:00,ALL,Info,server, Server init initialized
05-12-03 19:25:00,ALL,Info,server, Server version: 2.0.19.40 Win32
05-12-03 19:25:00,ALL,Info,server, Starting server with port: 8767
05-12-03 19:25:01,ALL,Info,server, Server init finished
05-12-03 19:25:06,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:25:12,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:29:14,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:32:05,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:38:00,ALL,Info,server, Server shutdown initialized
05-12-03 19:38:02,ALL,Info,server, Server shutdown finished
---------------------------------------------------------------
--------------- log ended at 05-12-03 19:38 --------------
---------------------------------------------------------------
---------------------------------------------------------------
-------------- log started at 05-12-03 19:38 -------------
---------------------------------------------------------------
05-12-03 19:38:29,ALL,Info,server, Server init initialized
05-12-03 19:38:29,ALL,Info,server, Server version: 2.0.19.40 Win32
05-12-03 19:38:29,ALL,Info,server, Starting server with port: 8767
05-12-03 19:38:29,ALL,Info,server, Server init finished
05-12-03 19:38:36,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:38:47,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:40:46,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:40:56,ERROR,All,frmMain, unable to detect external ip
05-12-03 19:45:52,ALL,Info,server, Server shutdown initialized
05-12-03 19:45:55,ALL,Info,server, Server shutdown finished
---------------------------------------------------------------
--------------- log ended at 05-12-03 19:45 --------------
---------------------------------------------------------------
---------------------------------------------------------------
-------------- log started at 05-12-03 19:55 -------------
---------------------------------------------------------------
05-12-03 19:55:21,ALL,Info,server, Server init initialized
05-12-03 19:55:21,ALL,Info,server, Server version: 2.0.19.40 Win32
05-12-03 19:55:21,ALL,Info,server, Starting server with port: 8767
05-12-03 19:55:21,ALL,Info,server, Server init finished
05-12-03 19:55:25,ERROR,All,frmMain, unable to detect external ip
05-12-03 20:09:41,ERROR,All,frmMain, unable to detect external ip

[Dummer Sack]

Do you configure the computer on which the TS server is running via DHCP?

If so, make sure thet the LAN IP did not change and still matches the IP you entered in the Port Forwarding.
I recommend that you do not let the computer obtain its IP automatically but configure it manually to avoid such problems.

In this thread (http://www.teamspeak.org/forums/showthread.php?s=&threadid=8979) are some tips on how to do that.

[guldi]

Dear <CK>Degan

Look, this is my last server.log from today:

-------------- log started at 06-12-03 11:59 -------------
---------------------------------------------------------------
06-12-03 11:59:13,ALL,Info,server, Server init initialized
06-12-03 11:59:13,ALL,Info,server, Server version: 2.0.19.46 Win32
06-12-03 11:59:15,ALL,Info,server, Starting VirtualServer id:1 with port:8767
06-12-03 11:59:16,ALL,Info,server, Server init finished
06-12-03 11:59:19,ERROR,All,frmMain, unable to detect external ip

In the last line you can see that I get this error too (at the moment). You can trust me, I did not edited my log to cheat you. The external IP detection is a feature presented by the TS "Master server". Your server is sending a packet to this server and gets in replay an answer containing your WAN IP. This IP is then shown on your Desktop.

It has happended "many times" that this service is not working. There is nothing YOU can do about it apart from having patience and wait till it is back !

If you can't live without the WAN IP:

- check www.myip.com
or have loot at
- www.dyndns.org (and check their docu)

[<CK>Degan]

Thanks Guldi. Now...the big question is: Why, after restarting my PC and running TSServer are my clients not able to join? I've checked my LANIP and everything is still good. Checked my router settings and nothing has changed there and, no I'm not running any kind of firewall (except Zonealarm *not pro* and everything there seems to be in order).

I'm sure theres something fishy up with my system (or service provider) but I've yet to figure it out, apparently others are having this problem recently also. If anyone else comes up with this problem *and* a solution I'd be most grateful. Thankyou

[Dummer Sack]

Yes, sounds strange.

But since it is better to have the IP of the TS server configured manually, try to change that and look if the problem goes away.
Just to remove one possible error source.

[<CK>Degan]

okay, server is runing and I cant figure out why but periodicly my router keeps switching back to DHCP. Why? I've NO clue..it must be possessed like the rest of my computer crap.

[Dummer Sack]

I don't understand.
The router is only hosting the DHCP server.
If a couputer uses this DHCP server to configure its IP address is configured at this computer not the router (in the way I described in this (http://www.teamspeak.org/forums/showthread.php?s=&threadid=1521) and this (http://www.teamspeak.org/forums/showthread.php?s=&threadid=8979) thread).

So do you mean the computer that is hosting the TS server is changing from manual to automatic configuration by itself?
I never heard of such a thing.

[<CK>Degan]

Everyone I've talked to has said the same thing, Sack, but trust me, its happening (last night as an example). If I can ever get through to Netgear support (LOL ya right) I'll get some answers and post them here for the rest of the TS community.

[Dummer Sack]

Its not that I don't beleve you. Its that I don't understand you.
You still did not tell what you mean with:
Originally posted by <CK>Degan
my router keeps switching back to DHCP.
Do you mean that on the computer that is hosting the TS server you did set it to "Use the Following IP Address" and on the next reboot it is back to "Obtain IP Address Automaticaly"?
If so then you do not have a problem with your router but a very strange problem with your computer / operating system and you should contact microsoft support not netgear support.

[<CK>Degan]

Yes, yes, exactly DS. That seems to be the issue. Funny though, it hasn't happened in a few days now and its got me worried (real problems are persistant, which I can fix). If it happens again, I'll be sure to let you all know AND what I'm doing to correct the situation (short of a 3# hammer, hehe).

So far, Microshaft hasn't been able to help me (partly could be the language barrier...I dont speak Indian), neither could Dell (big suprise?). I actually got through to Netgear and they are about as clueless as a prom queen at a gun show. At least you guys here know what you're talking about and at times are very helpful.

More later as the saga continues.