Hi, I'm curious to know how I can programmatically differentiate between a Samba share and a Windows NT share from a Windows program. For both, GetVolumeInformation() claims the file system is "NTFS". This isn't very helpful. I need to be able to tell the two apart because "real" NTFS supports various things Samba's "simulated" NTFS doesn't, such as 100-nanasecond time resolution and all file attributes. Is it possible? It seems like this would be a common question, but extensive searching turned up nothing... Thanks, Jordan Russell
Hi Jordan Russell, you wrote:> I'm curious to know how I can programmatically differentiate between > a Samba share and a Windows NT share from a Windows program. Forboth,> GetVolumeInformation() claims the file system is "NTFS". This isn't > very helpful. I need to be able to tell the two apart because "real" > NTFS supports various things Samba's "simulated" NTFS doesn't, suchas> 100-nanasecond time resolution and all file attributes. > > Is it possible? It seems like this would be a common question, but > extensive searching turned up nothing...read the docs: fstype (S) This parameter allows the administrator to configure the string that specifies the type of filesystem a share is using that is reported by smbd(8) when a client queries the filesystem type for a share. The default type is NTFS for compatibility with Windows NT but this can be changed to other strings such as Samba or FAT if required. Default: fstype = NTFS Example: fstype = Samba der tom
tandrew1304@earthlink.net
2003-Apr-09 21:39 UTC
[Samba] Re: Detecting Samba server from Windows?
you guys are very strange sometimes :) seriously, about 90% of peoples problems with samba on here could be fixed by doing 2 things.. 1. make Windows 9x network id and password = unix user you want to log in as 2. add "netbios name = <NT-server-name>" in the global section of smb.conf NT based kernels (XP/2000/NT) require the "netbios name" to be set, otherwise it will not work. security level = user, win9x uses your login id and password in windows, to log into samba, NT/2000/XP prompts you for an id and password. if you DON'T do this for 9x, you will have problems logging into IPC$ to fix this, just simply change your windows 9x id and password, because basically prompting for a password to IPC$ means it cannot find the userid and password you specified. NT/2000/XP prompts you for it when it tries to access the server, 9x prompts you for it when you startup your computer. just two different methods is all :) if you do just those 2 things, you shouldn't have to modify your smb.conf file AT ALL from the original defaults :) thats what I do under redhat 8 and 9 and Mandrake 8 and 9, and works just fine under all platforms :) -Tom- = = = Original message = = -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 7 Apr 2003, Jordan Russell wrote:> That's not useful. For one thing, changing fstype from NTFScan impact> "compatibility with Windows NT" as eluded to in the docs, andalso,> requiring users to modify their Samba configuration just somy program> can detect Samba would defeat the whole purpose of auto-detectingSamba> in the first place. I might as well just ask users to manuallyspecify> whether shares are Samba shares!Samba servers reply to the name __SAMBA__. this might help you. Other than that you could add something to the server string. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+lDm2IR7qMdg1EfYRAnCPAJ0YPB70uyKpuP6kud5HrB47XgC11ACgvWd8 yTabcDvNtRR23Mc643EzaQA=J/yq -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba ___________________________________________________________ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com.
Tom.Williams@diversifiedsoftware.com
2003-Apr-09 21:54 UTC
[Samba] Re: Detecting Samba server from Windows?
Since I've got a NT PDC around I've solved my login problems by using "password=domain" in my Samba configs on AIX, Solaris, HP-UX, and Linux and that works out very well for us. :) Peace..... ("another") Tom |---------+------------------------------------------------------------------> | | <tandrew1304@earthlink.net> | | | Sent by: | | | samba-bounces+tom.williams=diversifiedsoftware.com@list| | | s.samba.org | | | | | | | | | 04/09/03 02:39 PM | | | | |---------+------------------------------------------------------------------> >-----------------------------------------------------------------------------------| | | | To: <samba@lists.samba.org> | | cc: | | Subject: Re: [Samba] Re: Detecting Samba server from Windows? | >-----------------------------------------------------------------------------------| "Our mission is to help our clients achieve more cost-effective data center operations." you guys are very strange sometimes :) seriously, about 90% of peoples problems with samba on here could be fixed by doing 2 things.. 1. make Windows 9x network id and password = unix user you want to log in as 2. add "netbios name = <NT-server-name>" in the global section of smb.conf NT based kernels (XP/2000/NT) require the "netbios name" to be set, otherwise it will not work. security level = user, win9x uses your login id and password in windows, to log into samba, NT/2000/XP prompts you for an id and password. if you DON'T do this for 9x, you will have problems logging into IPC$ to fix this, just simply change your windows 9x id and password, because basically prompting for a password to IPC$ means it cannot find the userid and password you specified. NT/2000/XP prompts you for it when it tries to access the server, 9x prompts you for it when you startup your computer. just two different methods is all :) if you do just those 2 things, you shouldn't have to modify your smb.conf file AT ALL from the original defaults :) thats what I do under redhat 8 and 9 and Mandrake 8 and 9, and works just fine under all platforms :) -Tom- = = = Original message = = -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 7 Apr 2003, Jordan Russell wrote:> That's not useful. For one thing, changing fstype from NTFScan impact> "compatibility with Windows NT" as eluded to in the docs, andalso,> requiring users to modify their Samba configuration just somy program> can detect Samba would defeat the whole purpose of auto-detectingSamba> in the first place. I might as well just ask users to manuallyspecify> whether shares are Samba shares!Samba servers reply to the name __SAMBA__. this might help you. Other than that you could add something to the server string. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+lDm2IR7qMdg1EfYRAnCPAJ0YPB70uyKpuP6kud5HrB47XgC11ACgvWd8 yTabcDvNtRR23Mc643EzaQA=J/yq -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba ___________________________________________________________ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba