Strongly concur.  Samba simply won't work straight out the box. 

As for inviting Linux into the workspace cubicle, there are excellent reasons for Samba /not/ being part of the distro.  If a corporation has undertaken some initiative to integrate Linux into their IT infrastructure, their IT people will be perfectly content to install Samba themselves.  In point of fact, Linux has made enormous headway in the server room:  the Samba problem usually goes the other way, insulating the MSFT desk boxen from any Linux-y server considerations. 

Best regards,
Dan Weese

On Sat, Jul 7, 2012 at 7:25 AM, Christoph Wickert <christoph.wickert@gmail.com> wrote:
Am Samstag, den 07.07.2012, 12:41 +0100 schrieb Ron Leach:
> I'd
> always wondered why the system wouldn't see Windows shares, though.  I
> actually hadn't realised there needed to be another program installed.
>
> It would have helped us, at the start, if it had been in.

Not really. Please note that seeing the shares or browsing the network
is something different than connecting to a share. Even if you cannot
browse the LAN, you can still connect to a share or a host if you know
it's name.

Browsing requires a master browser. This usually is a Windows server and
if there is no server but only client OSes like XP, Vista or Windows 8
(not Windows 8 Server), they assign the master on a random base. This is
very unreliable, even for Windows, so you better set up Samba as the
master browser.

Long story short: Adding the package will not magically make all Windows
network functionality work, you still need to configure and start samba
to get the whole thing.

Best regards,
Christoph


_______________________________________________
xfce mailing list
xfce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xfce