Ralf Aumüller
2006-Aug-28 10:31 UTC
[Samba] Can't connect to Samba share when using "security = server"
Hello, when I try to connect from Client-1 (Windows 2003 Server with AD-Server) to a share on Samba-Server-1 (security = server, password server = Samba-Server-2) I got the error "No network provider accepted the given network path". There is no popup for the login information. If I try to access the share from a PC running Windows XP Professional everything works without any problems (after giving my credentials). Even when I change the configuration of Samba-Server-1 to "security = user" and copy the accout info from smbpasswd file from Samba-Server-2 to Samba-Server-1 I can connect to the share. So the problem seems to be with the "authentication forwarding". (All Samba-servers work like expected except if i try to conect from Client-1 with Windows 2003 Server and AD to Samba-Server-1). Name: Client-1 OS: Windows 2003 Server AD-Server for Domain A Name: Samba-Server-1 OS: Solaris 10 with Samba 3.0.23b Samba-configuration: security = server password server = Samba-Server-2 Name: Samba-Server-2 OS: Solaris 10 with Samba 3.0.23b Configured as an PDC for Domain B Hope someone can help, Ralf
Felipe Augusto van de Wiel
2006-Aug-28 15:42 UTC
[Samba] Can't connect to Samba share when using "security = server"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/28/2006 07:13 AM, Ralf Aum?ller escreveu:> Hello, > > when I try to connect from Client-1 (Windows 2003 Server with AD-Server) > to a share on Samba-Server-1 (security = server, password server > Samba-Server-2) I got the error "No network provider accepted the given > network path". There is no popup for the login information. > If I try to access the share from a PC running Windows XP Professional > everything works without any problems (after giving my credentials).'Client-1' is joined to the domain? Are you able to connect to 'Client-1' from one of the Samba Servers? Client-1 is able to connect to other Samba Servers? If using another Windows the same share in Samba-Server-1 works, looks like a problem related with Client-1 setup. Perhaps you could try to check the machine account information on the server to see what you get.> Even when I change the configuration of Samba-Server-1 to "security = user" > and copy the accout info from smbpasswd file from Samba-Server-2 to > Samba-Server-1 I can connect to the share.Using 'Client-1'? Maybe you could try 'security = domain'.> So the problem seems to be with the "authentication forwarding". > (All Samba-servers work like expected except if i try to conect from > Client-1 with Windows 2003 Server and AD to Samba-Server-1).[...]> Hope someone can help, > RalfI hope this helps. :) - -- Felipe Augusto van de Wiel <felipe@paranacidade.org.br> Coordenadoria de Tecnologia da Informa??o (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFE8w7ICj65ZxU4gPQRAnTYAJ9FriHsoo3Q70UkXWmzCKdF1mSc3QCgiaWL 1jK+D+9Lf5zCwy6N+QIzhl4=nu7g -----END PGP SIGNATURE-----
Maybe Matching Threads
- Update from 6.6 to 6.7 > automount logs error message
- Update from 6.6 to 6.7 > automount logs error message
- Update to Centos 7.7 / Arch ppc64le / Problem with nvidia driver
- Applying a transformation to multiple data frame columns
- Samba as a PDC and LDAP - migration