I am replacing an aged and terrible samba server with a new shiny one, where the directory structure actually makes sense, and access to files is controlled, but there's one problem with the new one:
The old samba server can be mapped by windows machines as a drive, so you can map " \server\" as a drive and it shows you all the shares. Neat, also useful.
The new one... does not. Mapping it directly like that gives an error: "The network name cannot be found". Mapping "\sever\sharename" works fine.
I would rather not need to map each of the dozen shares each as its own network drive, and there were problems involved in sharing the parent folder (each share is it's own volume).
So the question is: does anyone happen to know the secret sauce involved in that? Or am I being a dumbass and not seeing some simple setup thing that would fix it?
Here's the old smb.conf global section, but it looks uninteresting (share defines omitted because there's around 60 of them...)
[global] workgroup = stuff realm = stuff.site.com interfaces = eth0, 130.208.84.0/255.255.252.0, 10.170.0.0/16, 10.0.0.0/255.0.0.0 security = ADS passdb backend = tdbsam log level = 4 syslog = 0 log file = /var/log/samba/%m.log smb ports = 139 unix extensions = No machine password timeout = 0 preferred master = No domain master = No idmap domains = ALL idmap uid = 1001 - 900000000 idmap gid = 1001 - 900000000 idmap config ALL:readonly = yes idmap config ALL:default = yes idmap config ALL:backend = lwicompat_v4 read only = No cups options = raw wide links = Yes dos filetime resolution = Yes [link][1 comment]