Security options Of the security options settings, the (Cool web site)
Security options Of the security options settings, the first option (security) is the most important one to get right. It defines the type of security used to give access to the shared file systems and printers to the client computers. Security Sets how password and user information is transferred to the Samba server from the client computer. As noted earlier, it s important to get this value right. The default value for security (security=user) is different than the default value for security (security=share) in pre-2.0 versions of Samba. If you are coming from an earlier version of Samba and clients are failing to access your server, this setting is a good place to start. Here are your options: user The most common type of security used to share files and printers to Windows 95/98/2000 and Windows NT clients. It is the default set with Samba in the current release. This setting is appropriate if users are doing a lot of file sharing (as opposed to a Samba server used mostly as a print server). It requires that a user provide a user name/password before using the server. The easiest way to get this method working is to give a Red Hat Linux user account to every client user who will use the Red Hat Linux Samba server. This provides basically the same file permissions to a user account through Samba as the same user would get if he or she were logged in directly to Red Hat Linux. Caution Apparently, there is a bug in Windows for Workgroups that causes the password that the user types in to be ignored from a “connect drive” dialog box. Instead, Windows uses the user name and password in effect for the user’s current Windows login session. One way around this problem, although it is clumsy from a security standpoint, is to assign the same user name/password combination for each user on the Red Hat computer that they use in Windows. share The share value for security works best for just print sharing or for providing file access that is more public (guest sharing). A client doesn’t need to provide a valid user name and password to access the server. However, the user will typically have a guest level of permission to access and change files. See the sidebar describing guest accounts for further information. server The security option that, from the client s point of view, is the same as user security, in that the client still has to provide a valid user name/password combination to use the Samba server at all. The difference is on the server side. With server security, the user name/password is sent to another SMB server for validation. If this fails, Samba will try to validate the client using user security. domain The security option that, from the client s point of view, looks the same as user security. This setting is used only if the Samba server has been added to a Windows NT domain (using the smbpasswd command). When a client tries to connect to the Samba server in this mode, its user name and password are sent to a Windows NT Primary or Backup Domain controller. This is accomplished the same way that a Windows NT server would perform validation. Valid Red Hat Linux user accounts must still be set up. Encrypt Passwords Controls whether encrypted passwords can be negotiated with the client. This is off (No) by default. For domain security, this value must be true. Later versions of Windows NT (4.0 SP3 or later) and Windows 98 and Windows 2000 expect encrypted passwords to be on.
We recommend high quality webhost to host and run your jsp application: christian web host services.