Hello, everyone.
I am the developer for SMBUp. I see some comments that it doesn't work in this specific scenario and want to help make it at least able to mimic the current set-up.
Some background:
SMBUp exists because a lot of my friends were affected Lion retiring Samba for their own solution. The reasons behind this change are varied and justifiable on Apple's part, but the effect on users are undeniable. Old devices are incapable to connect to SMB shared from Lion. These old devices use an obsolete and old version of Samba (since it's the only free and available implementation, just as Apple did in OS X until 10.7) and the client in this version is incapable of connecting to SMB folder shared in modern versions of the protocol (Lion supports SMB2, non GNU/GPL V3 Samba versions only support the old, 1997, slow and obsolete version of SMB implemented in Windows 3.1 for Workgroups).
For these devices there's usually no way to use different versions of the SMB protocol, so even though Apple's actions may be justified the problem exists and needs fixing.
Enter Samba through MacPorts. From the very first day Lion was launched tutorials were made to install Samba through MacPorts. These meant a lot of steps and a certain degree of expertise and time, as Xcode had to be downloaded and packages installed (several hours in total).
I created SMBUp because I'd been arguing someone would come up with a front-end for Samba from the day Lion was released and after almost a full year couldn't believe nothing had come up. This also meant creating a Samba installer to free users of the need to do Xcode and Macports if all they wanted was samba.
So, to be clear: SMBUp is a front-end for Samba 3.2.15 and is fully compatible with MacPorts' installation (if you allow SMBUp to install itself you'll end up with the exact same set-up ad MacPorts).
This means there's no difference in running Samba from a macports installation and using SMBup for it. There might be differences in the configuration of Samba itself, though.
SMBUp provides a front-end for most functionality in SMB.CONF but doesn't preclude knowing about it for more advanced uses. It doesn't include either HOMES or PRINTERS shares yet, so these are ignored.
When loading shares in SMBUp is uses default values for them (namely: guest access enabled, read-only shared folders). These can be overriden and advances settings accessed. For example, if your shared folder requires "create mask" to be "0765" and "printable" to be set to "no" this can be done through the advanced settings.
Currently SMBUp doesn't store paths with spaces enclosed in double quotes. This shouldn't be a problem since Samba doesn't require it. You may see this difference if you compare both.
Also, if you install SMBUp and had Macports installed before, you can allow the program to read your existing config file or to create one from scratch. In either case we recommend keeping a copy of the one you know already works (normal location for smb.conf is "/opt/local/etc/samba/smb.conf". If you close SMBUp once installed and copy the old file in the new location, upon start SMBUp should parse it properly.
Let me know if you want specific help with SMBUp.