IIS6 win 2003 web edition and WEBADMIN woes...

[ghboom]

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%

4) Oh, I tried BoundToIp=my ip
and no luck, actualy made it worse because I couldnt get webadmin up on the server at all, through localhost

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

[pim]

I am not sure if I understand what your problem is, what I derive from this mass of information is that you have problems logging into the webadmin of TS, is this correct?

You also state that both TS and IIS are running fine, so I dont understand your reference to "2 servers working together"

If my assumption is correct, try the following;

If you want to get into webadmin from a different machine than the one the TS server is running on, but from within the LAN, use http://server-ip:14534 (fill in the LAN-ip address of your server here)

If you want to let people from the outside world connect to your webadmin, let them connect to http://wan-ip:14534, where the external IP is the IP address on the wanside of your router, so the same IP address they use to connect to your TS, but a different port. Before you do this make sure that port TCP 14534 is forwarded on your router to the internal IP of the box running the TS server

If my assumption is wrong, try to be a wee-bit more clearer

[ghboom]

Pim, sorry, it was late and I was numb !

Problem is

http://wan-ip:14534 wont work from outside the lan.
I get page not found errors, with boundtoip=wan-ip
or
boundtoip= set to nothing.

From inside the network http://wan-ip:14534 does not work,
I see 127.0.0.1 is showing up in the bottom left of Internet explorer with boundtoip=wan-ip
or
boundtoip= set to nothing.


Inside the network http://localhost:14535 works only if boundtoip is set to nothing

after last nights post I stopped the II6 web service,
set HTTPServer Port = 80 and http://wan-ip/ loaded the
TS Server Administration Login page
I tried to login and recieved the page cannot be displayed with the url of http://wan-ip/login.tscmd now in the address bar

Today I called my host to see if the dedicated server is behind a firewall he said no, I asked him if the router/default gateway blocked ANY ports he said, the plan I purchased is totaly unmanaged, and they dont protect customers, even from themselves !

with that, I know there are no ports being blocked

Hope you or someone can help !
Glenn H

[Dummer Sack]

If BoundToIP is set to your WAN IP zou cannot connect from localhost, because the server will only anwer connections that go to WAN IP (that is what bound to IP is for).

Do you have a seperate LAN IP? If that is a dedicated host I think not, am I right?
The differentiation between LAN and WAN IP only makes sense in a NAT environment. Otherwise both are the same.
If you are in a NAT environment then you will have to forward port 14534 TCP at the nat device to your host.

The only reason I can think of why it works on port 80 and not on port 14534 that there is some kind of packet filter/firewall in place (although your host said that not). Either by your host or at the computer.

Have you tried other ports beside 14534 and 80? Maybe 8767 TCP?
Maybe ports above 10000 are blocked? I don't know.

[ghboom]

OMG, nic adapter properties, TCP/IP , Advanced,Options

TCP/IP filtering !!!

Now I have read up on window 2003 server for three days now,
searched the web and not one mention of this !!!

Oh, it works now

Glenn H

[DrDan]

TCP/IP filtering !!!

Do what with TCP/IP filtering?


Cheers
Dan

[GlennH]

What he probably found was the same thing I found,
That even though windows firewall was off that TCP filtering
was disabling any connections to or on port 80....


GlennH

[WalkaboutTigger]

TCP Filtering tells the OS to filter TCP traffic to allow or deny port-level communications.

http://support.microsoft.com/default.aspx/kb/309798

http://support.microsoft.com/kb/314067/?sd=RMVP

http://online.securityfocus.com/infocus/1559

http://itinfo.mit.edu/answer.php?id=7046

http://www.netopia.com/support/howto...leshootip.html <- Overall troubleshooting of networking and Windows

[DrDan]

Thanks for that guys, however, TCP/IP filtering is not enabled. I assumed the problem was because it wasnt on, but after reading the above links it appears that might not be the case. Any thoughts?