[Samba] Problems with 2003 Server and Samba 3.0.1
I am following your thread and I am having problem to map samba share on my win2003 server. It works on win2k but not in win2003 server. I am running the latest SAMBA version 3.0.21b. I have set security = server Please advice. Thanks Bing -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Problems with 2003 Server and Samba 3.0.1
We have a Windows 2003 server that is a member of a Samba 2.2.8a domain. We can browse to this Samba server through My Network Places and map a drive to a share on this server. We also have a number of Samba 3.0.1 servers (running Solaris 8 and Red Hat 7.0). These are member servers of the Samba 2.2.8a domain. Using My Network Places on the Windows 2003 server, double clicking on one of these 3.0 Samba servers displays the following message: \\server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The request is not supported. The Windows 2003 server can also not map a drive to any Samba 3.0.1 shares. Windows 2000 Server and Windows XP machines can browse to the Samba 3.0.1 servers and map drives. These Samba servers were recently upgraded from Samba 2.2.8a to Samba 3.0.1. There were no browsing or mapping problems on Windows 2003 server when the samba servers were running 2.2.8a. It doesn't seem to matter if the Windows 2003 server is a member of the Samba 2.2.8a domain or not, the problem remains the same. What do I have to do to map drives from 2003 to Samba 3.0.1? Below is the smb.conf on our 3.0.1 server. - [global] workgroup = WALLACE server string = %h hosts allow = 192.168.191. 192.168.192. 192.168.193. 192.168.198. 127. log file = /var/log/samba/%m.log case sensitive = no preserve case = yes short preserve case = yes security = server password server = wallace.quadstone.com domain master = no domain logons = no local master = yes preferred master = no wins support = no os level = 50 guest account = samba socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384 SO_RCVBUF=16384 [homes] comment = Home Directories browseable = yes guest ok = yes writable = yes - Michael -- Michael Keightley [EMAIL PROTECTED]Tel: +44 131 240 3137 Systems Manager, Quadstone Limited,Fax: +44 131 220 4492 16 Chester Street, Edinburgh EH3 7RA, Scotland http://www.quadstone.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems with 2003 Server and Samba 3.0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 9 Jan 2004, Michael Keightley wrote: The Windows 2003 server can also not map a drive to any Samba 3.0.1 shares. Windows 2000 Server and Windows XP machines can browse to the Samba 3.0.1 servers and map drives. These Samba servers were recently upgraded from Samba 2.2.8a to Samba 3.0.1. There were no browsing or mapping problems on Windows 2003 server when the samba servers were running 2.2.8a. It doesn't seem to matter if the Windows 2003 server is a member of the Samba 2.2.8a domain or not, the problem remains the same. I think this might be fixed in 3.0.2pre1, but could you send me a level 10 debug log off list so I can verify what your problem is? Thanks. security = server hmmm...have you considered try security = domain ? it could also be an issue in your configuration with SMB signing. password server = wallace.quadstone.com domain master = no cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc If we're adding to the noise, turn off this song --Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE//swiIR7qMdg1EfYRArwhAJoDWaRCVSirTLC/o2GAkQigxGN1KACeOJ2v /M4Bb3HBf0gHcBbfh9cQAl8= =oiFu -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems with 2003 Server and Samba 3.0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 9 Jan 2004, Michael Keightley wrote: It is fixed in 3.0.2pre1. Also changing to security = domain and running net join in 3.0.1 fixed it. I've attached the log file anyway for security = server with 3.0.1. Do you recommend using security = domain rather than security = server? Yes. security = server has been deprecated in favor of domain mode security for quite a while (though maybe not documented in an official manner). cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc If we're adding to the noise, turn off this song --Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE//txAIR7qMdg1EfYRAr86AJ98FQYHHS6I2pA0MKInPiVmEOOgNgCgqJrX eYaSVekfjFKWkJTaNfmhAGM= =q612 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems with 2003 Server and Samba 3.0.1
On Fri, Jan 09, 2004 at 04:33:59PM +, Michael Keightley wrote: It is fixed in 3.0.2pre1. Also changing to security = domain and running net join in 3.0.1 fixed it. I've attached the log file anyway for security = server with 3.0.1. Do you recommend using security = domain rather than security = server? Always :-). security = server is a nasty hack for Win9x level servers and really shouldn't be encouraged. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problems with 2003 Server and Samba 3.0.1
On Fri, Jan 09, 2004 at 09:43:26AM -0600, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 9 Jan 2004, Michael Keightley wrote: The Windows 2003 server can also not map a drive to any Samba 3.0.1 shares. Windows 2000 Server and Windows XP machines can browse to the Samba 3.0.1 servers and map drives. These Samba servers were recently upgraded from Samba 2.2.8a to Samba 3.0.1. There were no browsing or mapping problems on Windows 2003 server when the samba servers were running 2.2.8a. It doesn't seem to matter if the Windows 2003 server is a member of the Samba 2.2.8a domain or not, the problem remains the same. I think this might be fixed in 3.0.2pre1, but could you send me a level 10 debug log off list so I can verify what your problem is? Thanks. security = server hmmm...have you considered try security = domain ? it could also be an issue in your configuration with SMB signing. I broke that so many times over the course of my NTLM2 changes it became quite silly. I think it's finally all OK in 3.0.2pre1, but it's also a good reason to upgrade your network to 'security=domain'. Andrew Bartlett -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
