Thank you all for your replies.

I am sorry I took a while to get back to you.

Here is a reminder of my situation:

I have Fedora 16 x64 installed on virtual machine (using VirtualBox).

I have installed some services (httpd, php, subversion)

I have installed FMS 4.5 but its not working properly.

At first, I didn't know how to modify the "server" and "adminserver" files... however, I found a post here by r.cira which helped me modify these files. After modification, I can restart FMS and FMS Admin without any warnings. However, my modifications were a bit different than his... this is what I did:

Inside "server", I searched for the term "RHEL5", and I got to the following line:

cd_check "Red Hat Enterprise Linux Client release 5" /etc/redhat-release redhat-RHEL5-i686

under which I added the following line

cd_check "Fedora release 16 (Verne)" /etc/redhat-release redhat-RHEL6-i686

Restarting FMS again gave me another warning (I forgot what it was... something like "unspported version"... anyways, I modified "server" again to override that warning... here is what I did:

I searched again for the term "RHEL5" and got to the following case statement:

case $DISTRO in

    redhat-RHEL5-i686)

                    ;;

Inside which I added the following:

    redhat-RHEL6-i686)

                    ;;

I did the same thing to "adminserver"... restarting both gave me no warnings.

Now, however, I am still at the same problem as before... that is... not sure why but it seems my FMS IS NOT running... but the FMS Admin IS running...

This is what I notice... when using the nmap command to see the ports that are bound to services... I can see:

1111/tcp open  lmsocialserver

but I cannot see the 1935 port at all... (Note: during installation, I have bound my FMS to the port 1935 alone... because the HTTP server is using port 80).

now... there is another thing that I noticed... and this is new. As I stated earlier, I have an older server that has FMS 3.5 on it... using nmap shows all ports bound successfully (1111 and 1935)... however, I recently found about the FMS upgrades from Adobe... so whenever I upgrade my server to any other version (other than the 3.5.1 that is already installed), I get the same symptom... FMS doesn't bind to port 1935, only FMS Admin connects to port 1111.

Not sure if thsoe are related... but I started to think maybe Adobe has changed something in terms of binding FMS to its ports (1935 in this example)...

Any ideas..?? thanks in advance... and sorry for the long post.

Thank you Nikhil for your reply.

After further investigations, it seems that Fedora is not a good platform to run FMS on. That is the problem here!!

Fedora was working fine for me when I used FMS 3.5.1, but any other later versions don't work (as explained above).

Even Fedora runs FMS 4.0, but not any of its updates.

Lastly Fedora x64 doesn't run FMS 4.5 at all (as explained above).

When I switched to CentOS 5.7, everything worked like charm, from the first time, without any troubles what so ever.

I am not a Linux expert... but I thought Fedora was based on Redhat... and I thought that all these different flavours of Linux are all built on the same infrastructure (almost)... so it sounded strange to me why it wouldn't work on Fedora but would on CentOs... It even sounded stranged why FMS 3.5.1 would work on Fedora but not FMS 3.5.7.