I have been trying for several weeks to install and configurate a Suse 11.3 Distro so it would work as a server.
Having some basic experience with the graphical Suse, I thought it would be possible, but it would take time.
This is what I’m trying to do:
The server is connected to the internet on one side and on the other side, connected to the internal network.
The server needs to broadcast the internet like a router would, so it also needs to have its firewall enabled. It needs to act as a Samba server.
And appearently, if I’m not mistaken, you also need a DNS-server for the internet, I think. It also needs a DCHP-server for the IP-adresses inside the internal network.
I have been able to make a server redirect the internet to the computers in the internal network. I don’t know how I did it and I’m unable to get Samba working on it.
On my second server I fixed the Samba issue, but I could not get the internet woring. Again, I don’t know how I managed to get in this situation.
I’ve been looking into multiple forums/fora, tutorials and explinations how to do stuff, including adding users to Samba (one of the problems I had).
Furthermore I don’t seem to figure out how exactly both the DNS-server and the DCHP-server fit in the picture. Has it something to do with LAMP, which currently I have not searched any information about.
If someone knows a good tutorial, maybe I haven’t spotted one of those on the World Wide Web, could you please reply?
Here’s the view of my network:
- Internet - // WWW ---- HUB --- // "niet een Router" "not a Router" || ||- Server1 -| // Server1 = main |- Server2 -|| // Server2 = backup || --- switch --- |||| ||||- "printer" |||-- PC1 ||--- PC2 |---- "Draadloos" "Wireless" - || PC3 -|| PC4 --|
As you can see, the internet signal goes to a HUB. There it gets multiplied and transmitted to one of the running servers. I have two servers just incase one breaks.
The internet signal goes through one of the servers and then goes to the SWITCH (and then you’re in the internal network).
The server needs to act as a router, because the IPs are not static.
About the computers in the internal network, variating from desktop to laptop and OS from Linux to Windows and MacIntosh. They all should be able to print and get connected to the internet, even if some of them are not inside the internal workgroup of Samba.
About filesharing of Samba: Every user would get his/her private map and there would be one public map shared for all users, including temporary guests.
I hope someone can help me. Thanks for reading.