Topic: running server mode only

[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.