Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: grahowler on June 21, 2003, 02:59:50 AM

Title: can't access server manager
Post by: grahowler on June 21, 2003, 02:59:50 AM
Hi Folks

I know this is probably a NU-B FAQ but I have searched around and I can't find the answer to a very simple question.

I have an e-smith machine that has been running happily on a network acting as an Internet gateway. I have it to configure APACHE and install some intranet stuff on. I have hooked it up to a machine running Win2k that is running on DHCP. I had to change the IP of the e-smith machine to a valid IP for my Win2k machine so I changed it to 192.168.0.1

The e-smtih machine has DHCP disabled and the system name is "Calamari". My understanding is that when, from my Win2k machine, I go to http://calamari/server-manager in a broswer I should be able to access the server manager, but I get a "this page cannot be displayed, check your network connection" message.

Any ideas?

thx in advance
Title: Re: can't access server manager
Post by: TrevorB on June 21, 2003, 03:47:30 AM
You can use the server-manager from any workstation 'within' the SME controlled network.

It sounds like you have tried to make the SME box a client of the W2K box (hence you will be trying to get into the SME via it's external, protected, interface).
You don't need to remove the SME box from it's role and you certainly shouln't need to change IP adddresses.

Now, if you wanted to remove it to do some playing. You can just use the keyboard and monitor on the SME box....

A little more info on exactly what you are trying to do will help. We may not be guessing then.

Trevor B

grahowler wrote:
>
> Hi Folks
>
> I know this is probably a NU-B FAQ but I have searched around
> and I can't find the answer to a very simple question.
>
> I have an e-smith machine that has been running happily on a
> network acting as an Internet gateway. I have it to configure
> APACHE and install some intranet stuff on. I have hooked it
> up to a machine running Win2k that is running on DHCP. I had
> to change the IP of the e-smith machine to a valid IP for my
> Win2k machine so I changed it to 192.168.0.1
>
> The e-smtih machine has DHCP disabled and the system name is
> "Calamari". My understanding is that when, from my Win2k
> machine, I go to http://calamari/server-manager in a broswer
> I should be able to access the server manager, but I get a
> "this page cannot be displayed, check your network
> connection" message.
>
> Any ideas?
>
> thx in advance
Title: Re: can't access server manager
Post by: Tom Haynes on June 21, 2003, 03:51:38 AM
Try https://192.168.0.1/server-manager
Title: Thanks guys.
Post by: grahowler on June 21, 2003, 05:40:45 AM
I appreciate the replies.

For trevor...

I am in a different physical location to where the machine lives normally and I have to install a large intranet on it which requires some fairly extensive Apache re-configuration. So the network's admin gave me the machine and said... "do what you need to do and I will re-install the machine on the network when you're done".

According to the network admin the IP configuration of the network it lives on would not be compatible with my win2k machine, thats why I was instructed to change the e-smith machine to 192.168.0.1 to make the changes I need to. He said that I should be able to change the IP then navigate to to HTTP://calamari/server-manager to start configuring it.

I need to acces it via a browser in order to browse the intranet that is being installed on it to check permission levels, amoungst other things. Unfortunately I can't get a hold of the network admin till Monday so I am left tinkering away for myself until then!

For Tom...

I tried your suggestion to no avail I am afraid.

Sorry if I am a bit vague but all help is appreciated.

Cheers!
Title: Got it!
Post by: grahowler on June 21, 2003, 09:32:19 AM
Thanks for the help but I got it going.

It was the subnet mask on my Win2k machine. When I ran ipconfig from the command prompt I realised that DHCP was setting the subnet mask to 255.255.0.0 on my Win2k machine. Once I set a static IP on it and set the subnet mask to 255.255.255.0 it worked like a charm.

Cheers and thanks for the assistance anyway!