Getting a virtual machine to play nice is one thing but having to configure 5 via Windows XP Remote Desktop is another especially if the virtual environment is a little new to me like Fedora Core 2. It wouldn’t have been such a challenge if the requirements were easy too. Being a Windows only environment I am basically solo in my knowledge of things Linux. Of course the fella in IT knows a bunch but we have a schedule to stick to. It seems IT people are the same everywhere you go. They know how to make machines run but making machines run well is another story. That isn’t a slam at all. It’s a realization that everyone has their own specialty area and no one can be expected to know it all.
Getting Apache running is no problem. Starting the service was easy too. The challenge came when running Samba. Using the GUI was a trick because it makes things seem too easy when really the power of the smb.conf file needs to be addressed.
The point of this post is to complain that after a day of restarting the SMB & NMB services, tweaking the conf file, checking the logs, and attempting to match kernel libraries to get VM to run smoothly; the problem with Samba was a small and unimaginable issue regarding SELinux.
I could ping to the virtual machines. I could see them in the list of machines in our workgroup. After I opened the appropriate ports I could even connect to the machine using the IP address. I kept getting a “The network path was not found” message. I also was able to get a random Guest logon prompt.
Now SELinux is new to me. It affiliation to the NSA startled me but I needed to learn how to configure it. I disabled it completely for Samba services but then I came back to it to configure it. There is a manual here. I found a very helpful thread at the same site here. Of course, I could just write a tutorial but maybe later.
After all this I am able to copy files to and from the Fedora virtual machines no problem. It was an interesting problem indeed.