Hello, we have two solaris file servers which export the file with nfs to the unix client and with samba to the windows clients. Both file servers are member of an active directory domain. Now we have the idea to use a new samba file server which contains the shares of both file servers and redirect the request to the correct file server with msdfs proxy. On this new fileserver I configure [global] ... encrypt passwords = Yes lanman auth = no ntlm auth = no client ntlmv2 auth = yes workgroup = xxx security = ads realm = XXX.RZ.RWTH-AACHEN.DE password server = xxx.rz.RWTH-Aachen.DE host msdfs = yes [homes] msdfs proxy = \yyy.rz.rwth-aachen.de\homes browseable = no I can connect to the homes share from a windows client which is not a member of the AD. But if I use a windows client which is member of the domain I get the error message "The drive could not be mapped because no network was found" What could be the reason? We use samba 3.0.23a without winbind. The unix and the windows site have different user administrations. The samba users have the same account name on both systems. Thanks in advance, Andrea
Gerald (Jerry) Carter
2007-Apr-17 16:21 UTC
[Samba] problems with msdfs proxy in AD environment
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrea Lorenz wrote:> I can connect to the homes share from a windows client which is not a > member of the AD. But if I use a windows client which is member of the > domain I get the error message > "The drive could not be mapped because no network was found"There have been a lot of MS-DFS fixes in 3.0.25rc1. Yo might want to test that out to see if we have already fixed this issue. cheers, jerry ====================================================================Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGJPPuIR7qMdg1EfYRAnnJAJoC0P3b18We9MMzahrciZtJHMTQuQCguF2J niTv7Eaw1A31OioV5Kju0Bg=fyPt -----END PGP SIGNATURE-----
Hello Jerry,>> I can connect to the homes share from a windows client which is not a >> member of the AD. But if I use a windows client which is member of the >> domain I get the error message >> "The drive could not be mapped because no network was found" > > There have been a lot of MS-DFS fixes in 3.0.25rc1. > Yo might want to test that out to see if we have already > fixed this issue.If I use 3.0.25rc1 it does not work for domain members and non domain members. Do anyone use sambas msdfs code inside an active directory domain? Andrea