Description of problem: I can mount Windows shared resources and ls the mounted point, browse with nautilus, ... When I try to mount an OS/2 shared resource, it seems that everything is going fine, but when I try to ls this, it hangs. I can just Ctrl^C the process. If I do it with Nautilus, using "connect to server" option, it opens the connextion Dialog and thenNautilus is shoing the working mouse pointer, but nothing happens. And if in the Browsing File System (nautilus with location bar) using smb://OS2SERVER/SHARED, it opens the connection dialog again, and the first time, can show the content of the remote share, but when I try to open an object, it don't matter if is a folder or if is a file, nautilus says that there isn't any assotiated application to open that object, and closing the dialog, the object dissapear. Version-Release number of selected component (if applicable): Fedora Core 2, Fedora Core rc3, Fedora Core 3. Samba 3.0.7, 3.0.8pre1-0.pre1.3 and I tried the final 3.0.8 downloaded from Samba Site. From Red Hat 9 (Samba 2.2.2 I think) the everything is running fine. How reproducible: Every time I try to connect to my OS/2 Server Steps to Reproduce: 1. smbmount //OS2SERVER/SHARED /mnt/drive -o username=my_user_name 2. ls /mnt/drive Actual results: nothing happen Expected results: Should list the content. Additional info: You can see that in messages.log fragment I attached, that there are some messages saying that the message is long, and something with a tdb lock function of a cache file.
Created attachment 106426 [details] Messages.log Here you can find what happens in the messages.log when I try to mount an OS/2 shared resource. Later, you can find what happens in the messages.log when I mount a Windows shared resource. As you can see, there is no problem to mount the XP resource.
Smbfs is part of the Linux kernel, not part of Samba. I'm reassigning this to the correct maintainer. You might want to try using mount -t cifs ... instead. cifs is much better maintained than smbfs.
Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you.