I'm just getting started, and getting quite a strange result. I've been able to mount my (login hal) Linux home directory as E: on my w95 system, but when I try to "smbmount //isdn2/AMDAHL-WORK /mnt/amdahlwork", where /mnt/amdahlwork is an empty directory on Linux, isdn2 is defined in /etc/hosts as 192,168.1.2, the address the W95 box uses, and AMDAHL-WORK is the name under which a certain W95 directory is shared, I get # smbmount //isdn2/AMDAHL-WORK /mnt/amdahlwork Added interface ip=192.168.1.10 bcast=192.168.1.255 nmask=255.255.255.0 Added interface ip=159.199.240.71 bcast=159.199.240.127 \ nmask=255.255.255.192 Connection to isdn2 failed Could not umount /mnt/amdahlwork: Device or resource busy smbmount: exit Now "mount" shows it as having been mounted -- the list includes //isdn2/AMDAHL-WORK on /mnt/amdahlwork type smbfs (0) but ls /mnt/amdahlwork ==> ls: /mnt/amdahlwork: Input/output error Last night, in addition, "ls /mnt" did not show amdahlwork after the mount. After "umount //isdn2/AMDAHL-WORK", it reappeared. FWIW, /var/log/samba/log.smb contains [2000/08/28 22:39:56, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 1014 are available. [2000/08/28 22:39:56, 0] smbd/server.c:main(683) standard input is not a socket, assuming -D option. I'd appreciate any advice. I am a UNIX network engineer, can read tcpdump output, etc., but am totally inexperienced using W95 sharing or with Samba. Thanks, Hal Hal Morris: hal@panix.com -- Editor of: * H-SHEAR Web pages: http://www.h-net.msu.edu/~shear * Tales of the Early Republic: http://WWW.EarlyRepublic.net Web Resources: Bibliography, Biographical Dict... (work in progress) * Jacksonian Miscellanies: free email bi-weekly of source excerpts.
On Tue, 29 Aug 2000, Hal Morris wrote:> but when I try to "smbmount //isdn2/AMDAHL-WORK /mnt/amdahlwork", where > /mnt/amdahlwork is an empty directory on Linux, isdn2 is defined in > /etc/hosts as 192,168.1.2, the address the W95 box uses, and AMDAHL-WORK > is the name under which a certain W95 directory is shared, I getDoes the win95 box answer to the (netbios?) name isdn2?> # smbmount //isdn2/AMDAHL-WORK /mnt/amdahlwork > Added interface ip=192.168.1.10 bcast=192.168.1.255 nmask=255.255.255.0 > Added interface ip=159.199.240.71 bcast=159.199.240.127 \ > nmask=255.255.255.192 > Connection to isdn2 failed > Could not umount /mnt/amdahlwork: Device or resource busy > smbmount: exitThe "Could not umount" is smbmount tripping itself up. It can't umount on some errors because it is itself keeping the mount open. That leaves it mounted but not connected to anything which causes Input/output error later. I have a patch for this, but this is not your problem. The real problem is "Connection to isdn2 failed". Can you connect like this if you use smbclient? ie 'smbclient //isdn2/AMDAHL-WORK'> FWIW, /var/log/samba/log.smb containssmbmount doesn't log to the samba log. /Urban
Hello, I am new to this list, and I haven't seen anything in the FAQ or the last 6 months of the discussion on this topic. Our clients (WinNT 4.0 SP4 and later) work well with the Samba 2.0.5a on Redhat 6.1. However, when we also install NAV Enterprise edition (the kind that updates from a server instead of from the Internet directly) my clients are no longer able to: 1) browse the Samba server (although they can find it). 2) login to the samba server. People who are using the NT server can still login, use and broswe the NT server (it also has NAV stuff installed though). Does NAV change some protocol? It adds some dll, but it doesn't show up in the network properties, so I don't know if it is changing netbui or changes the login somehow. Does anyone know how I can track this? Has anyone else heard this? Could it be Samba's fault? Thanks in advance. Bill ------------------------------------------------- This mail sent through IMP: mail.tasis.ch