Hi all, Loving the easy NT4 upgrade process- DNS with my existing BIND works great except a hint to make the domain name a subdomain so it doesn't collide with existing DNS zone. However, now when I try to connect to (for example) \\pegasus\crees I get "The network name cannot be found". A new share, "homes" has appeared, but of course it maps to nothing and I get the same error! Does the homes share lose its magic, or have I missed some obscure group policy setting? smb4.conf header: # Global parameters [global] workgroup = BAYOFRUM realm = ad.bayofrum.net <http://ad.bayofrum.net> netbios name = PEGASUS server role = active directory domain controller server services = rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate, smb dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupke y, dnsserver, winreg, srvsvc idmap_ldb:use rfc2307 = yes posix:eadb = /var/db/samba4/private/eadb.tdb [netlogon] path = /var/db/samba4/sysvol/ad.bayofrum.net/scripts <http://ad.bayofrum.net/scripts> read only = No [sysvol] path = /var/db/samba4/sysvol read only = No [homes] comment = Home Directories read only = No browseable = No Thanks for any help! Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Hello Chris, Am 22.12.2016 um 22:54 schrieb Chris Rees via samba:> However, now when I try to connect to (for example) \\pegasus\crees I > get "The network name cannot be found". A new share, "homes" has > appeared, but of course it maps to nothing and I get the same error! > > Does the homes share lose its magic,...On a Samba DC, yes. :-) The Samba dynamically-created per-user home shares feature is not working on a Samba AD DC. However, this is not a real limitation. Don't call the share [homes], share the folder containing the home directories instead, set the correct permissions, and Windows is happy, too. Because Windows doesn't know the dynamically-created per-user homes, this way additionally prevents you from discovering some problems when using folder redirections, etc. Here's a guide: https://wiki.samba.org/index.php/User_home_drives Regards, Marc
On Thu, 22 Dec 2016 21:54:58 +0000 Chris Rees via samba <samba at lists.samba.org> wrote:> Hi all, > > Loving the easy NT4 upgrade process- DNS with my existing BIND works > great except a hint to make the domain name a subdomain so it doesn't > collide with existing DNS zone.I take you have carried out a 'classicupgrade' from an NT4-style PDC to an AD DC. How is your Bind server set up ? is it using flat files ? If so I would suggest you take the hint and run bind on the DC using dlz as a subdomain of your original dns domain.> > However, now when I try to connect to (for example) \\pegasus\crees I > get "The network name cannot be found". A new share, "homes" has > appeared, but of course it maps to nothing and I get the same error!I think the first may be an effect of your bind setup at the moment. The second, the [homes] share, is because [homes] doesn't work on a DC, you will need to use something like [home] and add a 'path' line, you can also remove the 'browseable' line, this is because there is no browsing with a Samba AD DC. You are also going to have several other problems, this is because you seem to be using the deprecated 'ntvfs' database Rowland
Marc Muehlfeld wrote:> Hello Chris, > > Am 22.12.2016 um 22:54 schrieb Chris Rees via samba: >> However, now when I try to connect to (for example) \\pegasus\crees I >> get "The network name cannot be found". A new share, "homes" has >> appeared, but of course it maps to nothing and I get the same error! >> >> Does the homes share lose its magic,... > On a Samba DC, yes. :-) > > The Samba dynamically-created per-user home shares feature is not > working on a Samba AD DC. However, this is not a real limitation. Don't > call the share [homes], share the folder containing the home directories > instead, set the correct permissions, and Windows is happy, too. Because > Windows doesn't know the dynamically-created per-user homes, this way > additionally prevents you from discovering some problems when using > folder redirections, etc. > > Here's a guide: > https://wiki.samba.org/index.php/User_home_drives > > Regards, > Marc > >Thanks Marc! Please would you consider adding a line at the top of that wiki page saying that it doesn't work? I found that page, and was hoping I would still be able to have it as a legacy option. It's not a problem, but being explicit would be good-- even better would be a mention under [homes] in the smb.conf manpage. Would you accept such a manpage patch if you'd like me to do it? Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.