Bug 25521

Description of problem:
This report is to a large extent a repeat of report 22011, from which nothing seems to have transpred, and from which the situation has worsened.
The difficulty lies in the ability to mount SMB shares in Draxtools, as a component of the Control Centre. Historically, this has always been a bit flaky. Particularly in the 'search for servers' which notably fails far to often to find servers which are there.
Generally one of the requirements for access to a remote SMB share, is the access username and password on the remote unit. This was once covered, but at some point the option of entering a password was removed. At the time, I believe of Mga5,a change was made that I do applaud. It had been noticed that in fstab, the username and password were in clear, and a system I shall call 'Credentials' was added. In this the password was held in an entry in /etc/samba, which was only readable by root. You did not have to use this. In which case on bootup the user would be asked for the password, which rather defeated the purpose of hiding it Oddly, too, in Mga5 the new Credentials system only applied to 32 bit machines while 64 bit machines ran only the old system. In Mga7, we seem to have reverted to the old, pre-Credentials system. After a great number of attempts, recently, on a new build the search servers function did, in fact turn up a new server, the consequent fstab entry was of the old pre-Credentials style.
A further point, which has never been addressed, is that the 'server search function, when it works, returns a server name. Which it duly enters into the fstab entry. This subsequently does not work, since the mount operation requires an IP address. The machine cannot resolve this, until an appropriate entry in /etc/hosts is made.
When I upgraded to Mga6 on some of my machines, I gave up on the 'official' process and simply typed out the whole process from scratch. A further point, is that as laid out, the fstab entry will create a viable mount to a remote server, bu the subsequent file structure  will be entirely owned by root, which meant that the user can only write to the share as root.I used various subterfuges which drew a certain amount of ire on the Mageia Forum, to run Konqueror, my File Manager of choice, as root. At Mga5, I did a lot of research into this, and consequently found, and not in any Mageia chronicles, that if I added 'uid= (user id) and gid=(group id), to the fstab command line, the mount was created with normal ownership and rw rights as any other entry. Later, I realised that since this was a boot function, it would assign the same rights when logged in as someone else. Not that that matters to me since all my machines are single owner use


Version-Release number of selected component (if applicable):
All versions to current


How reproducible:
At all times


Steps to Reproduce:
1.try to add a ahared directory within Mageia Control Centre
2.
3.