I am setting up my server at home to run LAMP, DNS, DHCP, Mail, FTP. I haven’t decided if I am going to allow my windows boxes to connect to it yet or if I will just create an intranet page with file repository.
Currently the server is in a room that cannot run a wire to and I am thinking about doing all of the setup using my wireless adapter. Performance I know will take a hit until I wire it but that isn’t a big deal to me. My biggest concern is how hard will it be to setup these services and then migrate them to use the wired adapter.

Is it as simple as just disabling the wireless adapter and using the static IP Ion the wired adapter?

I didn’t plan on moving the server for about a week or maybe two since it will behind my desk and not have a monitor attached to it. I have never used the remote desktop options available and am not quite sure how they work. If they are easy to use and I can move this box sooner I will do that as well.

Does anyone have link to a guide about connecting remotely to the box from a windows machine?
If so what will I need installed on my windows computer to access the server? I am hoping to just setup the box and for the most part forget it.

Ok so I got home setup things on the floor and now I get an error when setting up the DNS server.

Error: 1m
Warning: (B mfile /etc/named.conf.include not found Skipping

Hi there,

You should have little to no issues migrating from wireless to wired NIC when the time comes, it really should not matter to you DNS, FTP or other services really.

Graphical remote connection options are pretty easy to set up - but they can be a bit odd too. If you are using Gnome, you should be able to simple activate the Vino VNC server in your menu to allow remote connections. Then use any generic VNC viewing client (Real VNC client, the No Machines Client, etc.) to connect to the Linux box.

The /etc/named.conf.include is a file which is included into /etc/named.conf - see that file which contains various notes and info on the settings you can use with named. You don’t actually need to have this .include file as all your zone file settings can be in the parent file.

I recommend using Yast however to configure your DNS zones, and not editing the file directly if you can avoid it - DNS zones are pretty intolerant of any formatting errors, etc.

I found configuring DNS in Suse using Yast to be delightfully easy. I love that you can manage your DNS using the command line version of Yast - that is extremely handy.

If you like, you may find this simple guide on setting up DNS in Yast I wrote to be helpful: Suse DNS Server Configuration - Lyceum

Good luck with your project.