problem with voice server and IIS6 Win2003 web edition

I have been putiing my hair out in clumps..
Purchased a dedicated server, Windows 2003 web edition with IIS6
installed.
I installed a team speak server for my boys, all 60 of us.
The Teamspeak server runs fine, no problems with that, but there is a
webadmin function that wont work with the ip of the server. need that
for my more dedicated members to handle everyday issues...

To connect the teamspeak client (a seperate progam) to my TSserver you
use http://my.ip.add:8767 and this works great, so at least i know
8767 is open.

Now the TS server has httpdocs that are all .html
My ip alone will load the default web on port 80, no problem
The address http://localhost:14534/ loads the webadmin fot
TS(httpdocs)when
im using remote desktop on the server.

If I use the IP inplace of localhost from my home desktop no joy.

I have tried,
1) Using local security policy, self managed firewall, making sure
that ports 14534 and 51234 are not being blocked.

2) I have reset security settings for the folder and subfolders that
the Teamspeak program resides in and gave the account IUSER_blabla

3) I have even tried creating a web and directing it to the httpdocs
folder, enabling anonomous access (the script handles auth) and also
allowed server side includes. when I open the side I get ,
%%INCLUDE%header.html%
bla bla
%%INCLUDE%footer.html%

To be honest, im prety shure Im not supposed to have to do this,
The TeamspeakServer for windows is a server in it self.

Does any one know how I can get my two servers to get along ?


Thanks,
Glenn H

David
Fri Jan 23 05:45:58 CST 2004

Woah, hold on a minute -- what evidence is compelling you to even change any
security settings ??? First, stop speculating and get rid of all those
changes that you've made. When you randomly make such changes without a
justfied reason, you run the risk of screwing up server-side configuration
beyond what you can repair, possibly needing to reinstall the entire server.
So, be less trigger-happy and pay more attention to diagnostics.

You're saying that port 8767 on your server is used by the TeamSpeak client.
You're also saying that port 14534 on your server is used for Web-based
administration of the TeamSpeak Server.

Now, what is/isn't working? I think you're saying that
http://localhost:14534 from the server itself works (which shows that all
the application settings are correct on the server and do not need to be
changed -- so I do not understand why you went about making security
changes). What isn't working is if you try to connect to port 14534 from
another computer. This seems like a network configuration/routing problem
and NOT with IIS6 at all.

Questions you must answer:
1. Which IP is that the website on 14534 bound to?
2. Is the IP an Internet routable IP or Intranet IP.
3. What ports are actually open on the IP interface that the website is
bound to
4. Are the client browsers going through some Proxy or not

I think some layer in between the client and server is botching things up,
and you need to start pointing out what those layers are in your particular
setup and verifying its functionality.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Glenn" <GHboom1@yahoo.com> wrote in message
news:1ab0deb8.0401212017.48476102@posting.google.com...
I have been putiing my hair out in clumps..
Purchased a dedicated server, Windows 2003 web edition with IIS6
installed.
I installed a team speak server for my boys, all 60 of us.
The Teamspeak server runs fine, no problems with that, but there is a
webadmin function that wont work with the ip of the server. need that
for my more dedicated members to handle everyday issues...

To connect the teamspeak client (a seperate progam) to my TSserver you
use http://my.ip.add:8767 and this works great, so at least i know
8767 is open.

Now the TS server has httpdocs that are all .html
My ip alone will load the default web on port 80, no problem
The address http://localhost:14534/ loads the webadmin fot
TS(httpdocs)when
im using remote desktop on the server.

If I use the IP inplace of localhost from my home desktop no joy.

I have tried,
1) Using local security policy, self managed firewall, making sure
that ports 14534 and 51234 are not being blocked.

2) I have reset security settings for the folder and subfolders that
the Teamspeak program resides in and gave the account IUSER_blabla

3) I have even tried creating a web and directing it to the httpdocs
folder, enabling anonomous access (the script handles auth) and also
allowed server side includes. when I open the side I get ,
%%INCLUDE%header.html%
bla bla
%%INCLUDE%footer.html%

To be honest, im prety shure Im not supposed to have to do this,
The TeamspeakServer for windows is a server in it self.

Does any one know how I can get my two servers to get along ?


Thanks,
Glenn H

David
Fri Jan 23 20:02:13 CST 2004

Woah, hold on a minute -- what evidence is compelling you to even change any
security settings ??? First, stop speculating and get rid of all those
changes that you've made. When you randomly make such changes without a
justfied reason, you run the risk of screwing up server-side configuration
beyond what you can repair, possibly needing to reinstall the entire server.
So, be less trigger-happy and pay more attention to diagnostics.

You're saying that port 8767 on your server is used by the TeamSpeak client.
You're also saying that port 14534 on your server is used for Web-based
administration of the TeamSpeak Server.

Now, what is/isn't working? I think you're saying that
http://localhost:14534 from the server itself works (which shows that all
the application settings are correct on the server and do not need to be
changed -- so I do not understand why you went about making security
changes). What isn't working is if you try to connect to port 14534 from
another computer. This seems like a network configuration/routing problem
and NOT with IIS6 at all.

Questions you must answer:
1. Which IP is that the website on 14534 bound to?
2. Is the IP an Internet routable IP or Intranet IP.
3. What ports are actually open on the IP interface that the website is
bound to
4. Are the client browsers going through some Proxy or not

I think some layer in between the client and server is botching things up,
and you need to start pointing out what those layers are in your particular
setup and verifying its functionality.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Glenn" <GHboom1@yahoo.com> wrote in message
news:1ab0deb8.0401212017.48476102@posting.google.com...
I have been putiing my hair out in clumps..
Purchased a dedicated server, Windows 2003 web edition with IIS6
installed.
I installed a team speak server for my boys, all 60 of us.
The Teamspeak server runs fine, no problems with that, but there is a
webadmin function that wont work with the ip of the server. need that
for my more dedicated members to handle everyday issues...

To connect the teamspeak client (a seperate progam) to my TSserver you
use http://my.ip.add:8767 and this works great, so at least i know
8767 is open.

Now the TS server has httpdocs that are all .html
My ip alone will load the default web on port 80, no problem
The address http://localhost:14534/ loads the webadmin fot
TS(httpdocs)when
im using remote desktop on the server.

If I use the IP inplace of localhost from my home desktop no joy.

I have tried,
1) Using local security policy, self managed firewall, making sure
that ports 14534 and 51234 are not being blocked.

2) I have reset security settings for the folder and subfolders that
the Teamspeak program resides in and gave the account IUSER_blabla

3) I have even tried creating a web and directing it to the httpdocs
folder, enabling anonomous access (the script handles auth) and also
allowed server side includes. when I open the side I get ,
%%INCLUDE%header.html%
bla bla
%%INCLUDE%footer.html%

To be honest, im prety shure Im not supposed to have to do this,
The TeamspeakServer for windows is a server in it self.

Does any one know how I can get my two servers to get along ?


Thanks,
Glenn H