PDA

View Full Version : administration ?? cannot find page


[007]_Bond
15-04-2003, 15:32
Hi all,

I have a problem with setting up a server.
Installing was no problem.
But when i'm trying to acces "administation" it cannot find the page.
I've read thru some post concerning this topic but non of them worked for me.

Some info: i do not have a router, use outpost as firewall,
running XP pro with all servicepack's and updates.

I've set outpost to allow anything concerning TS

What to do??

Judas
15-04-2003, 15:39
try going to your webbrowser and entering "localhost:14534" on the computer on which the server is running.

[007]_Bond
15-04-2003, 15:57
That is where i get the error message.
When it tries to connect to local hoast:14534
i get the message: connection refused

Thanks

Judas
15-04-2003, 17:04
hmm ok... i think i remember something about browser security settings. Do you allow cookies? I think the webadmin requires them. You might also try a different webbrowser if you have one available.

I assume that you dont have a fiewall rule which blocks any traffic other than on port 80?

[007]_Bond
15-04-2003, 18:43
Yes cookies are allowed, and firewall set to allow anything relating to TS.

The TS client works!

Judas
15-04-2003, 19:58
Have you tried to use the webinterface on another computer in your lan (LAN IP : 1453).

Did you by any chance change the port on which the webadmin is running?

[007]_Bond
15-04-2003, 23:35
no i did not try on another pc and did not chage the port.

I have no other pc at hand here.

i did make a chanel in publick server, sound was not good at all.
could hardly understand wat was said.

will this improve when i have own server or does this not matter?

Thanks.

Judas
16-04-2003, 09:09
Sound quality depends on a lot of things.

1) selected codec
2) quality of connection and distance to the host
3) quality of hardware used by the people (doesnt make all that big a difference though)
4) client-settings


You can select whatever codec you like on your own server.. so quality might improve. The connection should be better as well on your server as people you are hosting for usually live in the same country or a bordering one. Client settings might be the most important thingts to get right if you encounter problems. Shouldnt be all that hard to fix that in a few loopback tests though.


Aber the webinterface... i am a little bit at lost there. If you havent already tried id suggest that you completely uninstall the server and then try a new install.

[007]_Bond
16-04-2003, 09:39
Yes I tried a new install, tried it to another directory, tried it on another partition (C:/), even tried it in the same dir. as the client.
Non of this helps.
I still get the connection error when trieing to acces the administration.
What does work is the ip adresses, the show up fine, but i can not update ip,s
Then i also get an error message.

I'm getting a little bit lost here........... I do not no what else to do to fix problem.

Can't be unfixeble i guess.

Thanks.

Judas
16-04-2003, 11:20
Hmm.. error while updating the IP...

You should give the latest developer realease a try then. You can find that in the corresponding section of this board.

http://www.teamspeak.org/forums/showthread.php?s=&threadid=3854

This is at least supposed to fix certain errors with updating the ip.. maybe it fixes your problem as well.

[007]_Bond
16-04-2003, 11:37
Okay i did that, fixed the ip udate but still no administration..

you said something about using an other browser, i am using IE, maybe netscape works...

Will try that next.

Thanks

Judas
16-04-2003, 13:04
IE is actually supposed to be the browser with which it works for sure... but giving netscape/Mozialla a try cant hurt.

Are you running any webservers on the same computer where the TS client is running? That shouldnt cause any trouble but i remember having read about certain people having problems running a TS server next to a IIS.


If possible, a portscan might show you if the Webadmin port is open at all. If it isnt it might be conflicting with another application. Hence you could try to change the port (dont have a TS server at hands here so i cant tell you exactly how to do it, but i assume that it can be done in the server.ini while the server is shut down)

[007]_Bond
16-04-2003, 14:09
Hi,

I tried Opera for browser and it works!!!!!

I want to keep IE for browser so some detective work has to be done.

I will keep u informed about the result if ever to find it!!
Thanks for the help..

NormaN

Judas
16-04-2003, 14:39
Nice ;)

At least you have access now.

About IE. It generally does work with IE as the board would be flooded with thousands of post complainging if it wouldnt.

Yet it doesnt work on your system which makes me think that IE might either confuse something or your settings are not on default (which isnt actually a bad thing, since you might not be happy with default settings)

Try the following though. There is an option to add pages to your "trusted page list" or "trusted location list" or something along that line. If that for should work the source of the problem is located.

IE uses a few different security levels. Each applying to a specific environment (LAN, Trusted Sites, Secure Sites, Web, Sites you dont trust(?)). Since each of them Levels has different settings for security either I assume that either of the following happens on your comptuer:

1) IE doesnt trust the page
2) The settings for LAN (local) confilict with the TS Webadmin

u can also try connecting to 127.0.0.1:14534 (it could be that IE reacts different on "localhost" and "127.0.0.1")

Anyways.. let us know when you'll find a solution.

[007]_Bond
16-04-2003, 15:40
Party time....

I used the alternative "localhost" you sugested.

It works, can do anything now!!

Thanks for the tip.
I do not have enough IE experiance to now what the problem was.

Thanks for your help.

Norman

Judas
17-04-2003, 09:21
I could try to explain why it works with 127.0.0.1 but i'd very soon get lost in some networkstuff which i dont understand either.

localhost is actually supposed to be the same as 127.0.0.1 where 127.0.0.1 is the loopback address. Somehow your localhost either doesnt get resolved to 127.0.0.1 or does point to a wrong address. Anyways.. i'd say that you just leave it like it is cause messing with the network can get you in serious trouble ;)