Post Installaton questions Scalix Mail Server Fedora Core 4
Posted: Thu Jan 12, 2006 1:43 am
Hello everyone,
I was able to successfully install the scalix server. Thank you Scalix for your wonderful support.
I have a couple of coments and a question or too before I start adding users and testing the server.
1. During the install, the installation program does a pre-flight check to make sure everthing is present before starting the installation process. I had a problem getting past this step initally. It would always fail with unable to find network. I could not understand why the network could not be found. I had used the network to download the scalix server and test the DNS server to make sure that was working before I started. I though this was a real strange problem. Why can it not detect the network. After some fumbleing around I hit upon an idea, that possibly the nickname of the ethernet adapter was set incorrectly.
Durring the inital install of fedora core 4, the OS instlaler did not properly detect the network card. So I installed one of my older 10/100 cards just to the server up and running. when it came time to give the card a nic name, I gave it VT86C100A, the model number of the card that was installed. I rebooted the server and as redhat came up it would say initalizing network VT86C100A.
You can do an ifconfig eth0 and get all the information about the adpater, you can do a service network restart and that would all work perfectly. I thought what a cool way to know what network was what.
While I was troubleshooting this problem it occured to me that the older redhat 8 server always seemd to say "initalizing network eth0". I thought .. No that cant be, but I gave it a try anyway. After changing the nick name of the ethernet card to eth0 and restarting the network, I re-ran the pre-flight system check, and it was successful.
I might suggest a different way of checking for network connectivity other than trying to detect the nickname of the ethernet card.
2. The installation went pretty well. I thought that the java sdk was going to be included with the installation file, it was not, so I had to download and install this module in the middle of my installation. I should have not skipped over that step in the guide (sheesh).
3. Kerberos authentication.
This was skipped over during the install, Why?
Does the community version include kerberos authentication?
Isn't that a way of encrypting the passwords with out using HTTPS?
Can the admin console be accessed through HTTPS?
Can Kerberos authentication be installed at a later date?
I do not have a Kerberos server installed.
All clients authenticate through samba which is already encrypted.
4. The admin console came up just as expected. I have not started adding users, that will be tomorrow.
Thanks everyone for all your help. So far I am pretty impressed.
I was able to successfully install the scalix server. Thank you Scalix for your wonderful support.
I have a couple of coments and a question or too before I start adding users and testing the server.
1. During the install, the installation program does a pre-flight check to make sure everthing is present before starting the installation process. I had a problem getting past this step initally. It would always fail with unable to find network. I could not understand why the network could not be found. I had used the network to download the scalix server and test the DNS server to make sure that was working before I started. I though this was a real strange problem. Why can it not detect the network. After some fumbleing around I hit upon an idea, that possibly the nickname of the ethernet adapter was set incorrectly.
Durring the inital install of fedora core 4, the OS instlaler did not properly detect the network card. So I installed one of my older 10/100 cards just to the server up and running. when it came time to give the card a nic name, I gave it VT86C100A, the model number of the card that was installed. I rebooted the server and as redhat came up it would say initalizing network VT86C100A.
You can do an ifconfig eth0 and get all the information about the adpater, you can do a service network restart and that would all work perfectly. I thought what a cool way to know what network was what.
While I was troubleshooting this problem it occured to me that the older redhat 8 server always seemd to say "initalizing network eth0". I thought .. No that cant be, but I gave it a try anyway. After changing the nick name of the ethernet card to eth0 and restarting the network, I re-ran the pre-flight system check, and it was successful.
I might suggest a different way of checking for network connectivity other than trying to detect the nickname of the ethernet card.
2. The installation went pretty well. I thought that the java sdk was going to be included with the installation file, it was not, so I had to download and install this module in the middle of my installation. I should have not skipped over that step in the guide (sheesh).
3. Kerberos authentication.
This was skipped over during the install, Why?
Does the community version include kerberos authentication?
Isn't that a way of encrypting the passwords with out using HTTPS?
Can the admin console be accessed through HTTPS?
Can Kerberos authentication be installed at a later date?
I do not have a Kerberos server installed.
All clients authenticate through samba which is already encrypted.
4. The admin console came up just as expected. I have not started adding users, that will be tomorrow.
Thanks everyone for all your help. So far I am pretty impressed.