Topic: running server mode only

[input]

I am running SME Server in Server mode only because my second pcicard does not support it.
But can I acces SME Server from  another windowsclient with https ?
I want to play with it in Server mode only for now.
I found the servermanager to play with.
But I can not acces from my windowclient https://loek/server-manager/
I am running SME Server on virtualbox and when I type ifconfig I get this Address 192.168.166.1 when I ping this Adress on a terminal on my Windowsclient I get a Time-out.
Have sombody an idea how to connect with https://loek/server-manager.

Thanks

[janet]

input

You need to configure a DNS server correctly to get name resolution on your network, and point your workstations at that DNS server. The SME server can be the name server if you choose it to be, but you will need to specify that in your router or gateway machine. Alternatively just access it using
https://192.168.166.1/server-manager

I assume all your machines are on the same IP range ie 192.168.166.xx ?

[input]

input

You need to configure a DNS server correctly to get name resolution on your network, and point your workstations at that DNS server. The SME server can be the name server if you choose it to be, but you will need to specify that in your router or gateway machine. Alternatively just access it using
https://192.168.166.1/server-manager

I assume all your machines are on the same IP range ie 192.168.166.xx ?

I am running Fedora 14 with Virtualbox and SME Server Server only.
The ip from Fedora is 192.168.1.2  eth0
The ip from SME is 192.168.166.1 eth0
The ip from other Windowsclient is 192.168.1.179 eth0
I set the DNS on 192.168.168.1 but no luck. I can not acces https://192168.166.1/server-manager

[cactus]

I am running Fedora 14 with Virtualbox and SME Server Server only.
The ip from Fedora is 192.168.1.2  eth0
The ip from SME is 192.168.166.1 eth0
The ip from other Windowsclient is 192.168.1.179 eth0
I set the DNS on 192.168.168.1 but no luck. I can not acces https://192168.166.1/server-manager

SME Server and it's client need to be in the same subnet to have default access to the server manager. Guessing you have used a default C-class subnet (255.255.255.0) your Fedora client nor the windows client is in the SME Server subnet and most likely therefore not able to access it.

[janet]

input

You should have all computers on the same IP range ie
SME 192.168.1.xxx
Fedora 192.168.1.2
Windowsclient 192.168.1.179

Your DNS server should also be on the same IP range as the other computers eg
192.168.1.yyy
and then configure your Windows client to use that IP as the DNS server

What machine or device is acting as your DNS server ?
It may be simplest to nominate the SME server as your LAN's DNS server.

[input]

SME Server and it's client need to be in the same subnet to have default access to the server manager. Guessing you have used a default C-class subnet (255.255.255.0) your Fedora client nor the windows client is in the SME Server subnet and most likely therefore not able to access it.

Thanks for the reply.
But how can I solving it. Is there some documentation that I can read.

[cactus]

Thanks for the reply.
But how can I solving it. Is there some documentation that I can read.

You should configure this properly in the console, which is detailed in the manuals in the wiki (http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter6), it should be available when you login in SME Server as admin and choose the option to reconfigure your server.

[input]

input

You should have all computers on the same IP range ie
SME 192.168.1.xxx
Fedora 192.168.1.2
Windowsclient 192.168.1.179

Your DNS server should also be on the same IP range as the other computers eg
192.168.1.yyy
and then configure your Windows client to use that IP as the DNS server

What machine or device is acting as your DNS server ?
It may be simplest to nominate the SME server as your LAN's DNS server.

I used admin to login and I use as DNS 192.168.1.255 and I put it also by DNS from Windowsclient but no nothing happend.

[johnp]

.255 is a broadcast value for a /24 subnet i.e. usable ip addresses are from .1 thru .254

[cactus]

I used admin to login and I use as DNS 192.168.1.255 and I put it also by DNS from Windowsclient but no nothing happend.

I think your fundamental concept of basic network terminology and architecture is not up to par.

DNS is only for name resolution, you can see it as the address book of your network (and the internet), when using IP numbers it is not used as DNS is meant to translate human readable domain names to IP numbers, that can be handled by computers.

Networks consist of multiple PC's each having it's own unique address (IP number). This IP number is devided into for quads each ranging from 0 to 255. The groups are meant to limit the numbers of PC's that can be seen, this is called a subnet. Usually small networks consist of small numbers of PCs and a so called, C-class subnet (255.255.255.0) is used in which roughly 250 PCs can be placed. These PC's all have the first three quads of the IP address is common, only the last quad is unique. You can see a subnet more or less like a street, all houses are in the same street but they all have a different number.

SME Server only allows PCs in it's own subnet to access the server, in real life for instance the address of the server is set to 10.0.0.1 with a subnet of 255.255.255.0 means that only PCs with a IP address in the range 10.0.0.1 to 10.0.0.255 are able to interact with your server.

In order for your Fedora and Windows system your SME Server should be in the same subnet as them, which seems not to be the case.

You have two ways of solving that:
1. Connect your server to the network with a IP that is in the same subnet as your Fedora and Windows system
2. Add additional local networks for the networks you would like to have interaction to and from with SME Server, this can be done through the server-manager. (Since you can not access your server-manager directly you will have to access it through the admin console).

[input]

I think your fundamental concept of basic network terminology and architecture is not up to par.

DNS is only for name resolution, you can see it as the address book of your network (and the internet), when using IP numbers it is not used as DNS is meant to translate human readable domain names to IP numbers, that can be handled by computers.

Networks consist of multiple PC's each having it's own unique address (IP number). This IP number is devided into for quads each ranging from 0 to 255. The groups are meant to limit the numbers of PC's that can be seen, this is called a subnet. Usually small networks consist of small numbers of PCs and a so called, C-class subnet (255.255.255.0) is used in which roughly 250 PCs can be placed. These PC's all have the first three quads of the IP address is common, only the last quad is unique. You can see a subnet more or less like a street, all houses are in the same street but they all have a different number.

SME Server only allows PCs in it's own subnet to access the server, in real life for instance the address of the server is set to 10.0.0.1 with a subnet of 255.255.255.0 means that only PCs with a IP address in the range 10.0.0.1 to 10.0.0.255 are able to interact with your server.

In order for your Fedora and Windows system your SME Server should be in the same subnet as them, which seems not to be the case.

You have two ways of solving that:
1. Connect your server to the network with a IP that is in the same subnet as your Fedora and Windows system
2. Add additional local networks for the networks you would like to have interaction to and from with SME Server, this can be done through the server-manager. (Since you can not access your server-manager directly you will have to access it through the admin console).

Thank you for this expalnation.But may it also get through iptables that I cannot have acces.
And what DNS address should I use in the option admin console. For the client Fedora I have in resolf.conf 192.168.1.1

[cactus]

Thank you for this expalnation.But may it also get through iptables that I cannot have acces.

Not if you did not temper with them, they should be default based on your serves configuration and OK. Please start by amending your IP ranges/subnets, that is most likely the clue.

[input]

Not if you did not temper with them, they should be default based on your serves configuration and OK. Please start by amending your IP ranges/subnets, that is most likely the clue.

My Fedora client as also my Windowsclient are using DHCP.
And I tried using DNS in admin mode set to the same range as in etc/resolf.con 192.168.1.1.
But still no luck.

[johnp]

Did you not understand what cactus was telling you? You need to get an understaning of networks and subnet masking. Elsewise, your likely in for trouble.

[input]

Did you not understand what cactus was telling you? You need to get an understaning of networks and subnet masking. Elsewise, your likely in for trouble.

I am still a newbie for Linux.

[johnp]

Guess not, what he was telling you is not operating system dependant. For what you are doing, I'm thinking you are over your head. Please do some research regarding the suggestions.

[cactus]

I am still a newbie for Linux.

As I already explained, this has nothing todo with Linux, it is plain basic network knowledge.

Please take our advice and put all PC's in the same subnet. Stop mucking around with DNS and DHCP settings, simply configure your PCs to be in the same subnet, so the first three quads of their IP addresses are the same, e.g.:

Fedora: 192.168.1.2
Windows: 192.168.1.179
SME Server: 192.168.1.x

with x being a number that is still available in your 192.168.1 scope.

[input]

As I already explained, this has nothing todo with Linux, it is plain basic network knowledge.

Please take our advice and put all PC's in the same subnet. Stop mucking around with DNS and DHCP settings, simply configure your PCs to be in the same subnet, so the first three quads of their IP addresses are the same, e.g.:

Fedora: 192.168.1.2
Windows: 192.168.1.179
SME Server: 192.168.1.x

with x being a number that is still available in your 192.168.1 scope.

I give the SME Server 192.168.1.3 but when I tried to ping from my Windowsclient ping 192.168.1.3 I get a Time-out.
It also not work when I open my browser with https://192.168.1.3/server-manager.

[cactus]

I give the SME Server 192.168.1.3 but when I tried to ping from my Windowsclient ping 192.168.1.3 I get a Time-out.
It also not work when I open my browser with https://192.168.1.3/server-manager.

Allright, now we are getting somewhere, finally.

I saw you are using VirtualBox. Although I do not know the product by heart I remember that VirtualBox by default does not expose the virtual network interface of your guest to the network of the host system. This is done in a lot virtualization systems. Instead a private network is created through which the virtual host (guest) van communicate with the real life PC it is running on (host).

You will have to dive into the documentation and configiration of VirualBox to find a way to remove this private network and install a bridge interface on your Fedora system. This bridge is then used to expose the virtual network card to your real network and when that is done successfully I suspect you will be able to access server-manager on your virtual SME Server as well.

I have done a quick search on the internet and found this: http://www.samlesher.com/fedora/bridge-network-interface-on-virtualbox-in-fedora

Although it is for FC 8 I think the logic might still apply.

Be aware, in step 4 of the instruction network settings are configured for your bridge interface, but is seems some line wrappings are lost, I guess it should read something like this:

Code: [Select]

DEVICE=br0
TYPE=Bridge
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.100.2 #enter the IP you use for the host machine here
NETMASK=255.255.255.0 #enter the correct subnet mask for your network
GATEWAY=192.168.100.1 #enter the correct default gateway for your network
DELAY=0 STP=off
Since I noticed you are unfamiliar with basic networking I think you might have bitten off more than you can chew at the moment. Now you are also introducing a virtualization environment to the mix, I suggest you do some serious reading up and have a good read through through the manual of VirtualBox first. Then find out how to configure your bridge and see if that works.
If that works I suggest you start reading the SME Server Documentation in the wiki, especially the Administarion Manual and the User manual, all of it and, perhaps even twice. The past has proven that it might be much to grab at first and a second reading will help you understand better as you have a better grasp of the nice product SME Server is.

[input]

Allright, now we are getting somewhere, finally.

I saw you are using VirtualBox. Although I do not know the product by heart I remember that VirtualBox by default does not expose the virtual network interface of your guest to the network of the host system. This is done in a lot virtualization systems. Instead a private network is created through which the virtual host (guest) van communicate with the real life PC it is running on (host).

You will have to dive into the documentation and configiration of VirualBox to find a way to remove this private network and install a bridge interface on your Fedora system. This bridge is then used to expose the virtual network card to your real network and when that is done successfully I suspect you will be able to access server-manager on your virtual SME Server as well.

I have done a quick search on the internet and found this: http://www.samlesher.com/fedora/bridge-network-interface-on-virtualbox-in-fedora

Although it is for FC 8 I think the logic might still apply.

Be aware, in step 4 of the instruction network settings are configured for your bridge interface, but is seems some line wrappings are lost, I guess it should read something like this:

Code: [Select]

DEVICE=br0
TYPE=Bridge
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.100.2 #enter the IP you use for the host machine here
NETMASK=255.255.255.0 #enter the correct subnet mask for your network
GATEWAY=192.168.100.1 #enter the correct default gateway for your network
DELAY=0 STP=off
Since I noticed you are unfamiliar with basic networking I think you might have bitten off more than you can chew at the moment. Now you are also introducing a virtualization environment to the mix, I suggest you do some serious reading up and have a good read through through the manual of VirtualBox first. Then find out how to configure your bridge and see if that works.
If that works I suggest you start reading the SME Server Documentation in the wiki, especially the Administarion Manual and the User manual, all of it and, perhaps even twice. The past has proven that it might be much to grab at first and a second reading will help you understand better as you have a better grasp of the nice product SME Server is.

I appreciate your explanation for this all.

[input]

I appreciate your explanation for this all.

SMEServer is working now in Virtualbox.
Thanks for the reply's

[cactus]

SMEServer is working now in Virtualbox.
Thanks for the reply's

It would be nice if you were to detail your steps here. It might proof valuable to future readers.

[input]

It would be nice if you were to detail your steps here. It might proof valuable to future readers.

Running SMEServer on virtualbox using Windowsclient:
choose Settings and then Network Bridge Adapter and then for example use for Windowsclient 192.168.1.2 and use for the virtualboxclient 192.168.1.3 and you can log in https://192.168.1.3/server-manager.