Description of Problem: With nautilus, I cannot access the content of an SMP server (the machine itself for instance or any Windows NT server) Version-Release number of selected component (if applicable): RedHat 8.0 samba-2.2.5-10 samba-common-2.2.5-10 samba-client-2.2.5-10 nautilus-2.0.6-6 How Reproducible: Make your machine an SMP server (modify the smb.conf file, the smbpasswd file and the smbusers file) Open Nautilus, use the smb:// browsing functionality. Find your own server (or any other Windows NT server), click on it... The files are never displayed or it ask for the login and passwd to be send encrypted (they are not validated by the server anyway...) Steps to Reproduce: 1. Setup the SMB server and the smbfiles according to the RedHat 8.0 manual: [root@cherbourg samba]# diff smb.conf smb.conf.org 18c18 < workgroup = WIN --- > workgroup = MYGROUP 21c21 < server string = RedHat Linux 8.0. Samba 2.2.5 Server --- > server string = Samba Server 2. Open Nautilus and browse your own machine Actual Results: No files displayed File server not opened Uncrypted login and passwd asked, and not validated. Expected Results: Access to the content of the file servers Additional Information: The other way around it works: Windows NT machines access the machine I setup as a file server. It seems to prove that the problem is on the Linux SMB client side. I think it is a problem of encryption. Somehow the user name or the passwd is not recognised (I generated a smbpasswd and a smbusers file however) Maybe I have a daemon to restart after having modified the smbusers file. I restarted smbd but it did not change anything.
You might try with your Linux firewall totally disabled. (run /etc/init.d/ipchains stop, and verify with "ipchains -L" that there are no rules)
Actually, I had NO firewalls at all... I had to install ipchains, to reboot the machine and here is what I got: [root@cherbourg ted]# /etc/rc.d/init.d/ipchains stop Flushing all chains: ipchains: Incompatible with this kernel [FAILED] Removing user defined chains: ipchains: Incompatible with this kernel [FAILED] Resetting built-in chains to the default ACCEPT policy:ipchains: Protocol not available [FAILED] Obviously there has been no changes with Nautilus I tried to stop iptables also but it has not solved either my problem with Nautilus... Daniel
Very old bug with no information. There have been lots of changes since then, and it certainly works for me. (Though making sure that the firewall isn't blocking the relevant ports, 137 and 138, is always reasonable.)