Hi all, I've just finished upgrading my install to Red Hat 7.2 (from Red Hat 6 and 5.4 before that in case its relevant) but since the upgrade I cant access Samba. Initially I thought it was just that the upgrade has renamed the smb.conf file, but it still doesn?t work after renaming the backedup version. The Windows workstations display an error saying the domain controller cannot be contacted and if I run smbclient -L linux on the box itself I am asked for a password (is it the same as the linux account I am logged in as?) and I get the following error Session setup failed: code 0 (however this isnt the user with the encrypted password setup - see below) I looked this up on Google but all that came up was a patch that had something to do with PAM. I should also mention that up until this point the whole thing has been running on unencrypted passwords as there are Win95 boxes on the network (I have been led to believe these cant do encrypted passwords) but the point of the upgrade was to allow for Win2K workstation compatibility so I guess the whole thing will have to go encrypted now anyway. I have setup one user with encrypted passwords but couldn?t get in as that either (besides the domain controller message indicated that the servers not even responding rather than a password problem) Do I need the patch mentioned on google or am I missing something? Any advice appreciated. Ash -------------- next part -------------- HTML attachment scrubbed and removed
Ash Ridley wrote:> Hi all, > > I've just finished upgrading my install to Red Hat 7.2 (from Red Hat 6 > and 5.4 before that in case its relevant) but since the upgrade I cant > access Samba. Initially I thought it was just that the upgrade has > renamed the smb.conf file, but it still doesn?t work after renaming > the backedup version. > > The Windows workstations display an error saying the domain controller > cannot be contacted and if I run smbclient -L linux on the box itself > I am asked for a password (is it the same as the linux account I am > logged in as?) and I get the following error > > Session setup failed: code 0 > (however this isnt the user with the encrypted password setup - see > below) > > I looked this up on Google but all that came up was a patch that had > something to do with PAM. > > I should also mention that up until this point the whole thing has > been running on unencrypted passwords as there are Win95 boxes on the > network (I have been led to believe these cant do encrypted passwords) > but the point of the upgrade was to allow for Win2K workstation > compatibility so I guess the whole thing will have to go encrypted now > anyway. I have setup one user with encrypted passwords but couldn?t > get in as that either (besides the domain controller message indicated > that the servers not even responding rather than a password problem) > > Do I need the patch mentioned on google or am I missing something? Any > advice appreciated. > > Ash >Just some random thoughts: Have you checked your ipchains (firewall) settings? Redhat 7.2 installs with firewall enabled as default - check that ports 137-139 can get through to your workstations. Win95 can do encrypted passwords by updating with (all) the security patches (don't know if you should also employ some registry hack - look in the samba doc directory). Remember that the users has to be in both passwd and smbpasswd when you do encrypted passwords. Check that the user in smbpasswd is enabled (no D in the field to the right) and has a password Check the "hosts allow" in smb.conf Make sure that "smbclient -L //server_netbios_name" works before you try from the Win95 and Win2k workstations. Set the log-level higher (e.g. 3) in smb.conf and look in the logs when you try to connect. Eirik Thorsnes