Boot any of the Live-CD/DVD on a LAN that contains a confirmed working NFS server. On my test system the HD is turned off. Default setting: MCC -> Security -> Set up your personal firewall -> defaults to "Everything" checked Then do: MCC -> Network Sharing -> Access NFS shared drives and diretories -> Search servers nfs-utils is preinstalled and running on the live media. Launching a "Search servers" will result in an endless wait for the NFS server on the LAN being listed as available. Simply executing the following proces: MCC -> Security -> Set up your personal firewall -> uncheck then recheck "Everything" Then rerun: MCC -> Network Sharing -> Access NFS shared drives and diretories -> Search servers The available NFS servers on the LAN will be listed and setting up the share can proceed. If you install from the Live-CD/DVD this condition will be transferred to the install. If you install from the Classical DVD this is not a problem. Reproducible: Steps to Reproduce:
*** Bug 9365 has been marked as a duplicate of this bug. ***
first is always shorewall stopped ? we seems to have a bug in drakfirewall https://bugs.mageia.org/show_bug.cgi?id=9329 maybe the workaround fix this too ?
How can I stop shorewall?
systemctl status shorewal.service give you the status stop for stopping it (or with service )
Created attachment 3610 [details] results of shorewall service test - status, stop Turning off shorewall did not help.
Instead of stopping shorewall, try just using the command (as root), shorewall clear
CC: (none) => davidwhodgins
(In reply to Dave Hodgins from comment #6) > Instead of stopping shorewall, try just using the command (as root), > shorewall clear That indeed worked. Once "shorewall clear" was executed the MCC found the NFS share and continued to install the necessary code to set up the NFS dirtectory. Testing was done with Live-CD 32-bit installed on a USB thumb drive on real hardware. I'll assume it'll work on all the other Live media.
but if you have some shorewall rules, and if it stopped it works no ? seems really a dup of above bug
Old
Status: NEW => RESOLVEDResolution: (none) => OLD