Problems with TS servers and Win XP

[Napalm]

none of my clan can get TS server working on XP (client works fine), including myself. I used to run it on Win2k no problems.

When i install the server on XP, i can open it once, then close it, and the the server prog will not open again, ever.

This is the error i get in the log report.

22/06/2002 21:39:59 | ----Entering server init----
22/06/2002 21:39:59 | Created Threadlists
22/06/2002 21:39:59 | Done reading ini file
22/06/2002 21:39:59 | UDP+TCP created
22/06/2002 21:39:59 | Creating ping thread
22/06/2002 21:39:59 | Created ping thread
22/06/2002 21:39:59 | Creating UDPsender thread
22/06/2002 21:39:59 | Created UDPsender thread
22/06/2002 21:39:59 | FATAL ERROR: Unable to initialize communication

_______________________

I really would like to be able to run it on XP, and i know people who do, but they cant help me.

Help would be much appreciated. IF you need specs etc, then let me know

Thanks
Napalm

[R. Ludwig]

hi,

change the port in the ini file...

regards,
ralf

[Napalm]

Its set to the default 8765 already. Isn't that the correct one? Ive tried 8766 also, but with no success. I've tried reinstalling again too. And still same problem.

Thanks

[FatBoy666]

Try it with a higher port number. Like 25000, e.g.
But if XP blocks a bigger port range I can't help you with it, because I use Win2k or Linux. Maybe somebody knows how to unlock the standard voice port in XP...

[T. Boonstra]

Its odd that it won't open the port again, try disabling the Windows XP firewall and see if that helps..

[Napalm]

Im not using XP firewall, using a Sygate one, and it doesnt flash up saying that TS is trying to access the Net. Even with the firewall off the program wont boot. :/

Thanks

[T. Boonstra]

And you say that everyone in your clan has the same problem when they try to use TS Server?

Try download the latest TS Server from our website then, and delete/uninstall the old version you have installed..

[Napalm]

Ive tried both versions already of TS server, and tried reinstalling several times. Ive even reformatted since trying it for the first time, and still no joy. Each time I resinstall it will open once, and then once i close it, it wont open again, and thats without touching ANY settings.

Thanks

[LuCiFeR]

I have XP and im encountering the same problems. Ive already tried setting the port to 25000 or something lower like 10000. When i try to connect to the server it gives me an error. I think it was error 1100

[LuCiFeR]

Correction: Error -1000
Socket Error # 11004

[Solitaire]

the user you are logged on as, does it have admin rights? power user or user or something you setup yourself?

[LuCiFeR]

Im not sure what you mean. Do I have to set something up on my user to make a server? All I did was download the client and then the server and configured it.

[AceMan]

I am having the same trouble also. No firewall, multiple ports, even a twist of lime doesnt help I am running as administrator. I really would hope that there is more support out there than this! I would imagine that at least most of are smart enough too in that we dont need all the dumb posts in responce. This isnt an issue that any end user will solve, its a problem from within the server. Please help us to fix it.

[LuCiFeR]

I dont get it. Whenever I try to connect to my server by its name, it gives me that socket error. BUT i was reading the help documentation and now I'm able to connect to it by putting in the IP address and port number. When one of my friends gets on I'll ask him if he can connect to it as well.

[ScratchMonkey]

Sounds like a DNS problem. Look up the DNS for the name you were using. Sam Spade for Windows is good for this.

http://www.samspade.org/

If you use a non-standard port in the server ini file, you need to specify that port in the client, like this:

servername:12345

[LuCiFeR]

DNS Query at sam spade is disabled it says. I tried reverse DNS but it said OrderofDestruction:8765 doesnt exist. Oh well, I dont want to get into it, as long as I can get a server.

[LuCiFeR]

Ok I let my friend try to connect to the server but it gave him an error saying that there weren't any other computers on the other side...I also tried connecting to my server using my other computer and was successful. Btw I'm on a DSL line and these computers are connected using a LINKSYS Router.

[LuCiFeR]

TeamSpeak Staff, apparently my LINKSYS Router works like a firewall, and that is probably why no one can connect to my server outside of my LAN. Is DMZ the only way to disable this?

[Unregistered]

Unless you own a domain or have a domain name issued to you by your ISP, you must use the IP address of your server to communicate with it if you're trying to do this over the Internet.

If you are using a Linksys router, to the best of my knowledge you can configure it to pass all TEAMSPEAK traffic through to a specific internal IP address. I will post more details for this later.

[Unregistered]

Originally posted by LuCiFeR
TeamSpeak Staff, apparently my LINKSYS Router works like a firewall, and that is probably why no one can connect to my server outside of my LAN. Is DMZ the only way to disable this?

It appears DMZ is the only way to do this with the consumer-quality Linksys routers.

[Unregistered]

Originally posted by LuCiFeR
DNS Query at sam spade is disabled it says. I tried reverse DNS but it said OrderofDestruction:8765 doesnt exist. Oh well, I dont want to get into it, as long as I can get a server.

OrderofDestruction is your computer's NetBIOS name, not its DNS Hostname. Your ISP probably assigned a DNS Hostname to your IP address. The way to find it out is to go to either

http://www.network-tools.com

or

http://www.traceroute.org

and type your ISP-assigned IP address in and have it resolved for you from an external source.

[Unregistered]

Originally posted by LuCiFeR
TeamSpeak Staff, apparently my LINKSYS Router works like a firewall, and that is probably why no one can connect to my server outside of my LAN. Is DMZ the only way to disable this?

This should work - let me know!

In order to setup a public IP server for TeamSpeak, you must first do the following:

Assign a static IP Address to the computer that is going to be the designated server. If the LAN IP and DHCP Settings were not modified in any way from default, an address of 192.168.1.3 will work. Don't forget the Subnet Mask, Default Gateway, or the DNS Information. For more on setting up a static IP Address, refer to "How to set up a static IP address" in this Knowledgebase.

Access the Router's Setup page and select the Advanced tab. Click on the Forwarding tab and make the following modifications: [using an IP Address of 192.168.1.3]

Service Port Range Protocol IP Address
8765 TCP 192.168.1.3
8766 UDP 192.168.1.3

Once this is done, the server address for clients outside of the LAN will be your WAN IP Address* from the Router's Status page.

* If your service provider has provided you a dynamic IP Address or you are running a PPPOE DSL service, clients may drop unexpectedly due to changes in the IP Address. The use of a dynamic dns hosting service is recommended if hosting a server with one of these connections.

[LuCiFeR]

damn, thank you very much.

[Unregistered]

Us Californians gotta stick together! ;)

[LuCiFeR]

Hey Unregistered, one question about forwarding. When i go to my router's setup and go to forwarding, it has under Ext. Port [blank] to [blank] then to the side protocol "TCP or UDP" and then IP Address. I was wondering what to put in the first blank under Ext. Port. I know for one of em I put 8765, and then in a next one i put 8766 and enable those.

[ScratchMonkey]

TCP ports and UDP ports are completely separated, just like zip codes and phone numbers aren't the same thing but have a crude similarity.

So you need to forward UDP ports 8765 to 8765, and TCP ports 8766 to 8766. (ie. one port of each kind.)

[Hellraider]

Originally posted by AceMan
I am having the same trouble also. No firewall, multiple ports, even a twist of lime doesnt help I am running as administrator. I really would hope that there is more support out there than this! I would imagine that at least most of are smart enough too in that we dont need all the dumb posts in responce. This isnt an issue that any end user will solve, its a problem from within the server. Please help us to fix it.

:o It works prima on XP

SERVERINI:XP

[Version]
ServerVersion=v1.2.2
[Passwords]
ServerPassword=YOURS
AdminPassword=admin
[General]
Servername=YOURS clan
MaxClients=14
[Networking]
TCPPort=8766
IP=YOURS
[Ping]
MaxPingTries=3
PingWaitTime=15000
IdleTimeBeforePing=5000
[WebStatus]
Active=1
TeamSpeakSite_Active=1
TeamSpeakSite_DisplayInWebList=1
WebPostURL=
WebPostLinkUrl=http://www.teamspeak.net

[LuCiFeR]

Originally posted by ScratchMonkey
TCP ports and UDP ports are completely separated, just like zip codes and phone numbers aren't the same thing but have a crude similarity.

So you need to forward UDP ports 8765 to 8765, and TCP ports 8766 to 8766. (ie. one port of each kind.)

I thought UDP ports were 8766, not TCP.

[ScratchMonkey]

You're right, I got 'em backwards. (Just checked my running server to be sure.)

[Napalm]

ok after much messing about i finally got it working.

I tried a load of various IP's and finally got the right one, and the only way my server will boot is by not putting the IP in the config file. I can then connect to my server using the client, and so can the rest of my clan.

Well done me

Napalm

[Jens L.]

;)

sry

best help is self-help

[PsYcHo_FiSh]

I'm having the same problem with the dreaded "11004". I never had this problem with ventrilo (or any) but I'm using TS because my brother's clan now is.

This has to be a problem with TS itself, not just my ISP or my set up. Otherwise, ventrilo would have been giving me all this.

From what I can surmise on these forums, the only way around 11004 is through consulting with your ISP or replacing the host server name with its actual ip. This is something I cannot do right now! So you see: I am frustrated beyond belief.

I'm running XP pro with the built in firewall off. I don't think that would make a difference either way because I've turned my personal firewall off and it still gives me the 11004 error.

[Reval]

I am have ing the same problem most of you speak of. I am running on win xp I have a server up but no one can go in it tried numerous things. has any found a fix?

[WalkaboutTigger]

How To Fix The "Error getting network address for ".....". Cause: host not found (11001)"
How To Fix The "Error getting network address for ".....". Cause: requested entry not found (11004)"

An 11001 error means that the name you provided for a server in the client connection cannot be resolved to an IP address because DNS entries for that host name cannot be found. Try using the appropriate (internal or external) IP address for the server in the client connection string instead of the name.

An 11004 error means that the name you provided for a server in the client connection cannot be resolved to an IP address because DNS entries for that host name cannot be found or connection cannot be resolved to an IP address because DNS entries for that host name are misconfigured (for example a CNAME record without an appropriate A record). Try using the appropriate (internal or external) IP address for the server in the client connection string instead of the name.

If you need help determining your external IP address, from the TS server, bring up a browser and go to http://www.myipaddressis.com/ which will, after a moment, tell you your external IP address.

If you need help determining your internal IP address, from the TS server, go to a command interpreter prompt (on WinNT/XP/2k3, select Start, Run and type CMD and select OK) and type in IPCONFIG (if running WinNT/XP/2k3) and press ENTER. You should see something similar to the following:

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : example.com
IP Address. . . . . . . . . . . . : 192.168.1.60
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254

which displays the IP address of this machine as being 192.168.1.60 which is the internal IP address.

Walkabout