Re: Samba problems
At 12:29 PM -0300 3/26/05, Alejandro Pulver wrote: Hello, I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). Let me see if I understand the situation: You have a FreeBSD box running Samba. You have Win2k boxes which connect to file shares on that FreeBSD box. When they do, the PC's can not access partitions on the FreeBSD box, unless the FreeBSD box has already accessed them. I don't quite understand the reference to NTFS. Are you saying that the *FreeBSD* box is mounting NTFS partitions, and it then makes those partitions available to the PC's via Samba? Where are those NTFS partitions located? Are they on the hard drives of the FreeBSD box? Or is the FreeBSD box mounting them from some other file server? Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and 'tmp'. What am I doing wrong? What *exactly* is your /etc/fstab file? The fact that you have directories under /mnt does not tell us anything about what filesystems you are mounting, or how they are getting mounted. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
On Tue, 29 Mar 2005 11:52:15 -0500 Garance A Drosihn [EMAIL PROTECTED] wrote: At 12:29 PM -0300 3/26/05, Alejandro Pulver wrote: Hello, I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). Let me see if I understand the situation: You have a FreeBSD box running Samba. You have Win2k boxes which connect to file shares on that FreeBSD box. When they do, the PC's can not access partitions on the FreeBSD box, unless the FreeBSD box has already accessed them. Yes. I don't quite understand the reference to NTFS. Are you saying that the *FreeBSD* box is mounting NTFS partitions, and it then makes those partitions available to the PC's via Samba? Where are those NTFS partitions located? Are they on the hard drives of the FreeBSD box? Or is the FreeBSD box mounting them from some other file server? The NTFS slice I mount at '/mnt/w2k' is in the server. I only have two machines. Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and 'tmp'. What am I doing wrong? What *exactly* is your /etc/fstab file? The fact that you have directories under /mnt does not tell us anything about what filesystems you are mounting, or how they are getting mounted. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] This is my '/etc/fstab': # DeviceMountpoint FStype Options DumpPass# /dev/ad2s4b noneswapsw 0 0 /dev/ad2s4a / ufs rw 1 1 /dev/ad2s4e /tmpufs rw 2 2 /dev/ad2s4f /usrufs rw 2 2 /dev/ad2s4d /varufs rw 2 2 devfs /devdevfs rw 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/fd0/floppy msdosfs rw,noauto 0 0 /dev/ad0s5 /mnt/w2kntfsro 0 0 /dev/ad0s1 /mnt/wxpmsdosfs rw 0 0 /dev/ad2s1 /mnt/debext2fs rw,noauto 0 0 /dev/da0s1 /mnt/cammsdosfs rw,noauto 0 0 procfs /proc procfs rw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 Please see the complete thread (there is more information there). Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
Alejandro Pulver [EMAIL PROTECTED] wrote: On Sun, 27 Mar 2005 11:02:44 +0200 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: On Sat, 26 Mar 2005 20:37:51 +0100 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and'tmp'. What am I doing wrong? Who owns the subdirectories and who is your guest user? My guest user is 'nobody', but I also tried with 'ale' and 'root' (wich owns the mount point). Did you see in samba's log that the guest user was changed? How did you change it, with guest user or with force user? As your problem can be reproduced, increasing samba's debug level might help. Samba should log why read access was denied. If you access the samba share with mount_smbfs, do you see the same behavior? The directory '/mnt/w2k' is owned by 'root' and the group 'wheel', the permissions are rwxr-xr-x. I saw in SWAT that the connection from the other machine was mapped to the desired local user in all cases (I tried nobody, ale and root). I used guest account = user. Something strange is happening: I can access the sahre '/mnt' (and 'w2k') with 'smbclient' (using the 'guest' user), but if I do it with 'mount_smbfs //[EMAIL PROTECTED]/mnt /home/ale/tmp' then the problem appears, even with 'root' (I can not see/access entries until I list them with any user from '/mnt/w2k'). I think the problem is with Samba, not 'mount_smbfs'. This message appears (many times) in debug level 0: [2005/03/27 15:04:38, 1] smbd/service.c:make_connection_snum(648) mariana (192.168.1.1) connect to service mnt initially as user nobody (uid=65534, gid=65534) (pid 1217)[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 0, length 4096 returned[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. The other message I noticed (but I think it is not an error) in level 3 is: [2005/03/27 14:16:19, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [nobody] - [nobody] FAILED with error NT_STATUS_WRONG_PASSWORD[2005/03/27 14:16:19, 3] auth/auth.c:check_ntlm_password(219) check_ntlm_password: Checking password for unmapped user [EMAIL PROTECTED] with the new password interface[2005/03/27 14:16:19, 3] auth/auth.c:check_ntlm_password(222) check_ntlm_password: mapped user is: [EMAIL PROTECTED] The one that also called my attention was: [2005/03/27 14:16:30, 3] smbd/error.c:error_packet(105) error string = Is a directory [2005/03/27 14:16:30, 3] smbd/error.c:error_packet(129) error packet at smbd/nttrans.c(862) cmd=162 (SMBntcreateX) NT_STATUS_FILE_IS_A_DIRECTORY However I do not know about the internal working of Samba so perhaps I missed some important messages. I made different logs with different debug levels. They are in ftp://ftp.varnet.to (public FTP) in a directory called samba_logs. The local machine is called ale and the other mariana. The best log in level 3 is in the directory log.3_2. Today I tried your smb.conf and it worked as well as mine. I had a look at you logs, but didn't get more information out of them than you did. I get lock offset warnings as well, so they don't seem to be the problem. Perhaps you should ask on a samba list again. Fabian -- http://www.fabiankeil.de ___ freebsd-questions@freebsd.org mailing list
Re: Samba problems
On Mon, 28 Mar 2005 15:17:57 +0200 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: On Sun, 27 Mar 2005 11:02:44 +0200 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: On Sat, 26 Mar 2005 20:37:51 +0100 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and'tmp'. What am I doing wrong? Who owns the subdirectories and who is your guest user? My guest user is 'nobody', but I also tried with 'ale' and 'root'(wich owns the mount point). Did you see in samba's log that the guest user was changed? How did you change it, with guest user or with force user? As your problem can be reproduced, increasing samba's debug level might help. Samba should log why read access was denied. If you access the samba share with mount_smbfs, do you see the same behavior? The directory '/mnt/w2k' is owned by 'root' and the group 'wheel', the permissions are rwxr-xr-x. I saw in SWAT that the connection from the other machine was mapped to the desired local user in all cases (I tried nobody, ale and root). I used guest account = user. Something strange is happening: I can access the sahre '/mnt' (and 'w2k') with 'smbclient' (using the 'guest' user), but if I do it with'mount_smbfs //[EMAIL PROTECTED]/mnt /home/ale/tmp' then the problem appears, even with 'root' (I can not see/access entries until I list them with any user from '/mnt/w2k'). I think the problem is with Samba, not 'mount_smbfs'. This message appears (many times) in debug level 0: [2005/03/27 15:04:38, 1] smbd/service.c:make_connection_snum(648) mariana (192.168.1.1) connect to service mnt initially as user nobody (uid=65534, gid=65534) (pid 1217)[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 0, length 4096 returned[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. The other message I noticed (but I think it is not an error) in level 3 is: [2005/03/27 14:16:19, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [nobody] - [nobody] FAILED with error NT_STATUS_WRONG_PASSWORD[2005/03/27 14:16:19, 3] auth/auth.c:check_ntlm_password(219) check_ntlm_password: Checking password for unmapped user [EMAIL PROTECTED] with the new password interface[2005/03/27 14:16:19, 3] auth/auth.c:check_ntlm_password(222) check_ntlm_password: mapped user is: [EMAIL PROTECTED] The one that also called my attention was: [2005/03/27 14:16:30, 3] smbd/error.c:error_packet(105) error string = Is a directory [2005/03/27 14:16:30, 3] smbd/error.c:error_packet(129) error packet at smbd/nttrans.c(862) cmd=162 (SMBntcreateX) NT_STATUS_FILE_IS_A_DIRECTORY However I do not know about the internal working of Samba so perhaps I missed some important messages. I made different logs with different debug levels. They are in ftp://ftp.varnet.to (public FTP) in a directory called samba_logs. The local machine is called ale and the other mariana. The best log in level 3 is in the directory log.3_2. Today I tried your smb.conf and it worked as well as mine. I had a look at you logs, but didn't get more information out of them than you did. I get lock offset warnings as well, so they don't seem to be the problem. Perhaps you should ask on a samba list again. Fabian
Re: Samba problems
Alejandro Pulver [EMAIL PROTECTED] wrote: On Sat, 26 Mar 2005 20:37:51 +0100 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and'tmp'. What am I doing wrong? Who owns the subdirectories and who is your guest user? My guest user is 'nobody', but I also tried with 'ale' and 'root' (wich owns the mount point). Did you see in samba's log that the guest user was changed? How did you change it, with guest user or with force user? As your problem can be reproduced, increasing samba's debug level might help. Samba should log why read access was denied. If you access the samba share with mount_smbfs, do you see the same behavior? The directory '/mnt/w2k' is owned by 'root' and the group 'wheel', the permissions are rwxr-xr-x. If you only want read access, this looks fine. Fabian -- http://www.fabiankeil.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
On Sun, 27 Mar 2005 11:02:44 +0200 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: On Sat, 26 Mar 2005 20:37:51 +0100 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and'tmp'. What am I doing wrong? Who owns the subdirectories and who is your guest user? My guest user is 'nobody', but I also tried with 'ale' and 'root' (wich owns the mount point). Did you see in samba's log that the guest user was changed? How did you change it, with guest user or with force user? As your problem can be reproduced, increasing samba's debug level might help. Samba should log why read access was denied. If you access the samba share with mount_smbfs, do you see the same behavior? The directory '/mnt/w2k' is owned by 'root' and the group 'wheel', the permissions are rwxr-xr-x. If you only want read access, this looks fine. Fabian -- http://www.fabiankeil.de Hello, Thank you for your reply. I saw in SWAT that the connection from the other machine was mapped to the desired local user in all cases (I tried nobody, ale and root). I used guest account = user. Something strange is happening: I can access the sahre '/mnt' (and 'w2k') with 'smbclient' (using the 'guest' user), but if I do it with 'mount_smbfs //[EMAIL PROTECTED]/mnt /home/ale/tmp' then the problem appears, even with 'root' (I can not see/access entries until I list them with any user from '/mnt/w2k'). I think the problem is with Samba, not 'mount_smbfs'. This message appears (many times) in debug level 0: [2005/03/27 15:04:38, 1] smbd/service.c:make_connection_snum(648) mariana (192.168.1.1) connect to service mnt initially as user nobody (uid=65534, gid=65534) (pid 1217)[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 0, length 4096 returned[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets[2005/03/27 15:04:44, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. The other message I noticed (but I think it is not an error) in level 3 is: [2005/03/27 14:16:19, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [nobody] - [nobody] FAILED with error NT_STATUS_WRONG_PASSWORD[2005/03/27 14:16:19, 3] auth/auth.c:check_ntlm_password(219) check_ntlm_password: Checking password for unmapped user [EMAIL PROTECTED] with the new password interface[2005/03/27 14:16:19, 3] auth/auth.c:check_ntlm_password(222) check_ntlm_password: mapped user is: [EMAIL PROTECTED] The one that also called my attention was: [2005/03/27 14:16:30, 3] smbd/error.c:error_packet(105) error string = Is a directory [2005/03/27 14:16:30, 3] smbd/error.c:error_packet(129) error packet at smbd/nttrans.c(862) cmd=162 (SMBntcreateX) NT_STATUS_FILE_IS_A_DIRECTORY However I do not know about the internal working of Samba so perhaps I missed some important messages. I made different logs with different debug levels. They are in ftp://ftp.varnet.to (public FTP) in a directory called samba_logs. The local machine is called ale and the other mariana. The best log in level 3 is in the directory log.3_2. Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Samba problems
Hello, I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and 'tmp'. What am I doing wrong? Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
First of all, make sure those mounts are accessible for normal users, if you haven't. It's under the options for the mount in /etc/fstab, I think. You can always do a 'man fstab' if unsure. Does the username/password (check out 'smbpasswd') you are using to connect to samba exist in the samba user database? If not, samba won't know who you are, and will use the default guest user to access files (usually very restricted). That might be why you can access the mounts when you log in to the server, but not through server. If you go with the first, ALL users will have access. If you want to restrict it to, say, a certain group, you have to go with the second solution I think (and add users in the samba user database). Hope I got the issue correctly, else I dunno :-). Regards, Stefan Haglund Hello, I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and 'tmp'. What am I doing wrong? Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
On Sat, 26 Mar 2005 16:59:11 +0100 Stefan Haglund [EMAIL PROTECTED] wrote: First of all, make sure those mounts are accessible for normal users, if you haven't. It's under the options for the mount in /etc/fstab, I think. You can always do a 'man fstab' if unsure. Does the username/password (check out 'smbpasswd') you are using to connect to samba exist in the samba user database? If not, samba won't know who you are, and will use the default guest user to access files (usually very restricted). That might be why you can access the mounts when you log in to the server, but not through server. If you go with the first, ALL users will have access. If you want to restrict it to, say, a certain group, you have to go with the second solution I think (and add users in the samba user database). Hope I got the issue correctly, else I dunno :-). Regards, Stefan Haglund Hello, Thank you for your reply. I am using the security level SHARE with guest enabled (I have only two machines on my network). The mounts are accessible by normal users (like ale), the permissions in '/mnt/w2k/' are 'rwxr-xr-x', the owner is root and group wheel. I would like to add that I also have another share that is a FAT32 partition (WinXP) and I can browse it from the other machine (like everything else). I tried to map the guest account to the user ale that I use (and I can access '/mnt/w2k'), but nothing happened. This only happens in a NTFS mount point. The files and directories show as truncated, and I can not see (determine size, copy, determine if it is a file or directory, etc.) them until I do an operation over them with any normal user in the server, then I can see the files/dirs affected by the operation I did (ls, etc.). Before I only see the entries (names) without attributes (permissions, directory flag, etc.). Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
On Sat, 26 Mar 2005 13:54:37 -0300 Alejandro Pulver [EMAIL PROTECTED] wrote: On Sat, 26 Mar 2005 16:59:11 +0100 Stefan Haglund [EMAIL PROTECTED] wrote: First of all, make sure those mounts are accessible for normal users, if you haven't. It's under the options for the mount in /etc/fstab, I think. You can always do a 'man fstab' if unsure. Does the username/password (check out 'smbpasswd') you are using to connect to samba exist in the samba user database? If not, samba won't know who you are, and will use the default guest user to access files (usually very restricted). That might be why you can access the mounts when you log in to the server, but not through server. If you go with the first, ALL users will have access. If you want to restrict it to, say, a certain group, you have to go with the second solution I think (and add users in the samba user database). Hope I got the issue correctly, else I dunno :-). Regards, Stefan Haglund Hello, Thank you for your reply. I am using the security level SHARE with guest enabled (I have only two machines on my network). The mounts are accessible by normal users (like ale), the permissions in '/mnt/w2k/' are 'rwxr-xr-x', the owner is root and group wheel. I would like to add that I also have another share that is a FAT32 partition (WinXP) and I can browse it from the other machine (like everything else). I tried to map the guest account to the user ale that I use (and I can access '/mnt/w2k'), but nothing happened. This only happens in a NTFS mount point. The files and directories show as truncated, and I can not see (determine size, copy, determine if it is a file or directory, etc.) them until I do an operation over them with any normal user in the server, then I can see the files/dirs affected by the operation I did (ls, etc.). Before I only see the entries (names) without attributes (permissions, directory flag, etc.). Thanks and Best Regards, Ale I even tried mapping the guest account to root but it still does not work. Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
Alejandro Pulver [EMAIL PROTECTED] wrote: I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and 'tmp'. What am I doing wrong? Who owns the subdirectories and who is your guest user? I'm using samba version 3.0.11 and can't reproduce the described behavior. My smb.conf is: [global] workgroup = W62 netbios name = TP51 server string = Samba Server auf Laptop security = user encrypt passwords = yes log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY wins support = yes dns proxy = no [fk] comment = No place like home path = /home/fk valid users = fk public = no writable = yes printable = no [mnt] comment = Quick test path = /mnt valid users = fk public = no writable = yes printable = no [EMAIL PROTECTED] /mnt $ls -l total 8 drwxr-xr-x 1 fk wheel 0 Apr 22 2009 ad0s1 drwxr-xr-x 1 fk wheel 4096 Jan 1 1980 ad0s2 drwxr-xr-x 5 fk wheel 512 Mar 25 19:14 datenspeicher drwxr-xr-x 2 fk wheel 512 Mar 26 19:03 test ad0s1 is ntfs, ad0s2 is fat32. Both can be used without any problems. I just noticed the strange dates. If I unmount ad0s1 and ad0s2, the dates make more sense. [EMAIL PROTECTED] /mnt #ls -l total 8 drwxr-xr-x 2 fk wheel 512 Mar 26 18:58 ad0s1 drwxr-xr-x 2 fk wheel 512 Mar 26 15:03 ad0s2 drwxr-xr-x 5 fk wheel 512 Mar 25 19:14 datenspeicher drwxr-xr-x 2 fk wheel 512 Mar 26 19:03 test Interesting. I'm using FreeBSD 5.4-PRERELEASE #2: Fri Mar 25 17:53:21 CET 2005. Fabian -- http://www.fabiankeil.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
Could you output the /etc/fstab? As far as I know, the major difference is that writing to NTFS isn't fully supported in Linux (last I checked). Maybe there is something Samba tries to do, that conflicts with that. Other than that I don't know, sorry. :-) Regards, Stefan Haglund On Sat, 26 Mar 2005 16:59:11 +0100 Stefan Haglund [EMAIL PROTECTED] wrote: First of all, make sure those mounts are accessible for normal users, if you haven't. It's under the options for the mount in /etc/fstab, I think. You can always do a 'man fstab' if unsure. Does the username/password (check out 'smbpasswd') you are using to connect to samba exist in the samba user database? If not, samba won't know who you are, and will use the default guest user to access files (usually very restricted). That might be why you can access the mounts when you log in to the server, but not through server. If you go with the first, ALL users will have access. If you want to restrict it to, say, a certain group, you have to go with the second solution I think (and add users in the samba user database). Hope I got the issue correctly, else I dunno :-). Regards, Stefan Haglund Hello, Thank you for your reply. I am using the security level SHARE with guest enabled (I have only two machines on my network). The mounts are accessible by normal users (like ale), the permissions in '/mnt/w2k/' are 'rwxr-xr-x', the owner is root and group wheel. I would like to add that I also have another share that is a FAT32 partition (WinXP) and I can browse it from the other machine (like everything else). I tried to map the guest account to the user ale that I use (and I can access '/mnt/w2k'), but nothing happened. This only happens in a NTFS mount point. The files and directories show as truncated, and I can not see (determine size, copy, determine if it is a file or directory, etc.) them until I do an operation over them with any normal user in the server, then I can see the files/dirs affected by the operation I did (ls, etc.). Before I only see the entries (names) without attributes (permissions, directory flag, etc.). Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
On Sat, 26 Mar 2005 20:37:51 +0100 Fabian Keil [EMAIL PROTECTED] wrote: Alejandro Pulver [EMAIL PROTECTED] wrote: I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). My configuration file is as follows: = BEGIN = # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2004/12/11 19:24:02 # Global parameters [global] workgroup = VARNET server string = FreeBSD 5.3 security = SHARE log file = /var/log/samba/log.%m max log size = 50 dns proxy = No [mnt] comment = Mounted Filesystems path = /mnt guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [ale] comment = Ale's Home DIrectory path = /home/ale guest ok = Yes = END === Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and'tmp'. What am I doing wrong? Who owns the subdirectories and who is your guest user? I'm using samba version 3.0.11 and can't reproduce the described behavior. My smb.conf is: [global] workgroup = W62 netbios name = TP51 server string = Samba Server auf Laptop security = user encrypt passwords = yes log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY wins support = yes dns proxy = no [fk] comment = No place like home path = /home/fk valid users = fk public = no writable = yes printable = no [mnt] comment = Quick test path = /mnt valid users = fk public = no writable = yes printable = no [EMAIL PROTECTED] /mnt $ls -l total 8 drwxr-xr-x 1 fk wheel 0 Apr 22 2009 ad0s1 drwxr-xr-x 1 fk wheel 4096 Jan 1 1980 ad0s2 drwxr-xr-x 5 fk wheel 512 Mar 25 19:14 datenspeicher drwxr-xr-x 2 fk wheel 512 Mar 26 19:03 test ad0s1 is ntfs, ad0s2 is fat32. Both can be used without any problems. I just noticed the strange dates. If I unmount ad0s1 and ad0s2, the dates make more sense. [EMAIL PROTECTED] /mnt #ls -l total 8 drwxr-xr-x 2 fk wheel 512 Mar 26 18:58 ad0s1 drwxr-xr-x 2 fk wheel 512 Mar 26 15:03 ad0s2 drwxr-xr-x 5 fk wheel 512 Mar 25 19:14 datenspeicher drwxr-xr-x 2 fk wheel 512 Mar 26 19:03 test Interesting. I'm using FreeBSD 5.4-PRERELEASE #2: Fri Mar 25 17:53:21 CET 2005. Fabian -- http://www.fabiankeil.de Hello, Thank you for your reply. My guest user is 'nobody', but I also tried with 'ale' and 'root' (wich owns the mount point). The directory '/mnt/w2k' is owned by 'root' and the group 'wheel', the permissions are rwxr-xr-x. Y have the same strange dates. Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems - stopped working
On 01/06/05 02:14 PM, Louis LeBlanc sat at the `puter and typed: Anyone else seeing problems with Samba3? swat dumps core every time I try to connect - SIGABRT. Smbd nmbd don't pick up the phone (yes, netstat -an shows listeners on ports 139 and 443). They don't log anything, just no answer. Well, I got the network mounts working (no printer shares), and have rebuilt samba3 several times. Swat still cores, and I can't figure it out. It's still going south in the authentication phase, and even if I put it in demo mode with the -a switch. I haven't had authentication problems with any other apps. My current port config is as follows: $ make showconfig === The following configuration options are set for samba-3.0.10,1: LDAP=on With LDAP support ADS=on With Active Directory support CUPS=on With CUPS printing support WINBIND=on With WinBIND support ACL_SUPPORT=off With ACL support SYSLOG=off With Syslog support QUOTAS=off With Quota support UTMP=on With UTMP support MSDFS=off With MSDFS support SAM_XML=off With XML smbpasswd backend SAM_MYSQL=off With MYSQL smbpasswd backend SAM_PGSQL=off With PostgreSQL smbpasswd backend SAM_OLD_LDAP=off With Samba2.x LDAP smbpasswd backend PAM_SMBPASS=off With SMB PAM module EXP_MODULES=off With experimental module(s) POPT=on With installed POPT library Anyone else running samba-3.0.10.1 from the ports that saw this? Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Training is everything. The peach was once a bitter almond; cauliflower is nothing but cabbage with a college education. -- Mark Twain, Pudd'nhead Wilson's Calendar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Samba problems - stopped working
Anyone else seeing problems with Samba3? swat dumps core every time I try to connect - SIGABRT. Smbd nmbd don't pick up the phone (yes, netstat -an shows listeners on ports 139 and 443). They don't log anything, just no answer. I'm running 5.3 RELEASE, rebuilt yesterday. I don't know when it stopped working, but I'm running the latest samba3 port - rebuilt just today while trying to fix the problem. While building samba, the only apparent problems are the following warnings: checking rpcsvc/yp_prot.h presence... yes configure: WARNING: rpcsvc/yp_prot.h: present but cannot be compiled configure: WARNING: rpcsvc/yp_prot.h: check for missing prerequisite headers? configure: WARNING: rpcsvc/yp_prot.h: see the Autoconf documentation configure: WARNING: rpcsvc/yp_prot.h: section Present But Cannot Be Compiled configure: WARNING: rpcsvc/yp_prot.h: proceeding with the preprocessor's result configure: WARNING: rpcsvc/yp_prot.h: in the future, the compiler will take precedence configure: WARNING: ## -- ## configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## configure: WARNING: ## -- ## checking for rpcsvc/yp_prot.h... yes and: checking sys/mount.h presence... yes configure: WARNING: sys/mount.h: present but cannot be compiled configure: WARNING: sys/mount.h: check for missing prerequisite headers? configure: WARNING: sys/mount.h: see the Autoconf documentation configure: WARNING: sys/mount.h: section Present But Cannot Be Compiled configure: WARNING: sys/mount.h: proceeding with the preprocessor's result configure: WARNING: sys/mount.h: in the future, the compiler will take precedence configure: WARNING: ## -- ## configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## configure: WARNING: ## -- ## checking for sys/mount.h... yes After seeing these, I went back and removed all the autoconf and automake packages and let them be rebuilt as dependencies, but these warnings still show up. There are also a number of build warnings, but nothing that seems critical to me, but there are some Passing arg blah of blah from incompatible pointer type errors in a lot of the auth based code. Checking the swat core, it is pretty obvious that the abort() was called somewhere in the authentication calls. Anyone else? Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ A banker is a fellow who lends you his umbrella when the sun is shining and wants it back the minute it begins to rain. -- Mark Twain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Samba problems...v2.2.8a
Hi again, I've got a problem with Samba this time. I can't seem to get it to allow me to map drives, on a normal basis. I seem to be able to get things working - but...once my workstation reboots, I get errors about password or username is invalid. There is nothing in the log file(s), and nothing seems to work. Once I synch my password to my windows password, everything is fine again (smbpasswd feature). I'm trying to make my Samba server either (a) independent of my Windows box, or (b) completely tied into my Windows Active Directory auth scheme...which I'd like to get away from. Can someone help me out? Pasting my smb.conf file below for reference, in case it makes sense to anyone. For what it's worth - I'm trying to completely migrate the entire server infrastructure AWAY from Windows...to a totally FreeBSD/Samba/etc network. smb.conf file [global] workgroup = Bounds netbios name = Server1 server string = Server1 log file = /var/log/log.%m max log size = 50 security = user unix password sync = no ; lanman auth = no ; lm announce = no log file = /var/log/samba.log log level = 9 change notify timeout = 300 deadtime = 15 encrypt passwords = yes oplocks = yes socket options = TCP_NODELAY [C$] comment = C$ path= /stor1/WinEmulate valid users = backup read only = Yes browseable = No create mask = 0770 [Shared] comment = Shared path= /stor1/shared valid users = ralph read only = No browseable = Yes create mask = 0750 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + Ralph | Internet Systems Security + + Boundariez.com | -Specializing in Paranoia- + -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + ralph[!at]boundariez[dot!]com | Never understimate the power + +AIM: SekurityWizard | stupid people + +ICQ: 2206039|in large groups+ -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Samba problems
Brian, When you say The error you're seeing, RPCPROG_NFS: Program not registered, is nfsd complaining that it can't talk to portmap (which registers RPC services). Are we talking the portmapper on the local computer, or the portmapper on the remote computer. Also for anyone else, I've gotten further with my mount_smbfs problem, but still getting errors. It returns: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /home mount_smbfs: vfsload(smbfs): File exists ANY time I use mount_smbfs, it doesn't even matter if the computer I'm trying to connect to has Samba or not. It returns it for all calls to mount_smbfs. I did add NETSMB, NETSMBCRYPTO, LIBICONV, LIBMCHAIN, and SMBFS to my kernel config and recompiled as well as issuing kldload smbfs so that smbfs was added to my /boot/loader.conf. If I've done something I shouldn't have please by all means correct me. Zac Brown On Tue, 20 Jan 2004 11:13:46 -0500 Brian Minder [EMAIL PROTECTED] wrote: On Mon, Jan 19, 2004 at 09:27:33PM -0600, Zac Brown wrote: The problems in the earlier post are irrelevant because I figured out I was trying to connect to the wrong IP now but I have a new problem. When I use mount_smbfs I get the following error: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /mnt/home mount_smbfs: unable to open connection: syserr = Connection refused And when I try to mount the nfs share I get the following error: phineas# mount -t nfs 192.168.0.3:/home/zac /mnt/home 192.168.0.3:/home/zac: nfsd: RPCPROG_NFS: Program not registered Any help or enlightenment would be greatly appreciated. Thanks in advance. Make sure you have the following line in your /etc/rc.conf: nfs_client_enable=YES This will start portmap when the system boots. The error you're seeing, RPCPROG_NFS: Program not registered, is nfsd complaining that it can't talk to portmap (which registers RPC services). Sorry, but I don't have any experience with SMBFS mounts, so I can't be of much help there. Hope that helps, -Brian -- [EMAIL PROTECTED]1024/8C7C4DE9 -- Zac Brown http://rufius.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Samba problems
Brian, When you say The error you're seeing, RPCPROG_NFS: Program not registered, is nfsd complaining that it can't talk to portmap (which registers RPC services). Are we talking the portmapper on the local computer, or the portmapper on the remote computer. Also for anyone else, I've gotten further with my mount_smbfs problem, but still getting errors. It returns: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /home mount_smbfs: vfsload(smbfs): File exists ANY time I use mount_smbfs, it doesn't even matter if the computer I'm trying to connect to has Samba or not. It returns it for all calls to mount_smbfs. I did add NETSMB, NETSMBCRYPTO, LIBICONV, LIBMCHAIN, and SMBFS to my kernel config and recompiled as well as issuing kldload smbfs so that smbfs was added to my /boot/loader.conf. If I've done something I shouldn't have please by all means correct me. BTW: My rc.conf contains the following entries in that order for reference: nfs_client_enable=YES nfs_client_flags= mountd_enable=YES rpcbind_enable=YES portmap_enable=YES Zac Brown On Tue, 20 Jan 2004 11:13:46 -0500 Brian Minder [EMAIL PROTECTED] wrote: On Mon, Jan 19, 2004 at 09:27:33PM -0600, Zac Brown wrote: The problems in the earlier post are irrelevant because I figured out I was trying to connect to the wrong IP now but I have a new problem. When I use mount_smbfs I get the following error: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /mnt/home mount_smbfs: unable to open connection: syserr = Connection refused And when I try to mount the nfs share I get the following error: phineas# mount -t nfs 192.168.0.3:/home/zac /mnt/home 192.168.0.3:/home/zac: nfsd: RPCPROG_NFS: Program not registered Any help or enlightenment would be greatly appreciated. Thanks in advance. Make sure you have the following line in your /etc/rc.conf: nfs_client_enable=YES This will start portmap when the system boots. The error you're seeing, RPCPROG_NFS: Program not registered, is nfsd complaining that it can't talk to portmap (which registers RPC services). Sorry, but I don't have any experience with SMBFS mounts, so I can't be of much help there. Hope that helps, -Brian -- [EMAIL PROTECTED]1024/8C7C4DE9 -- Zac Brown http://rufius.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Samba problems
Problem resolved, IP conflict :) Thanks for everyone's suggestions. On Tue, 20 Jan 2004 16:10:02 -0600 Zac Brown [EMAIL PROTECTED] wrote: Brian, When you say The error you're seeing, RPCPROG_NFS: Program not registered, is nfsd complaining that it can't talk to portmap (which registers RPC services). Are we talking the portmapper on the local computer, or the portmapper on the remote computer. Also for anyone else, I've gotten further with my mount_smbfs problem, but still getting errors. It returns: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /home mount_smbfs: vfsload(smbfs): File exists ANY time I use mount_smbfs, it doesn't even matter if the computer I'm trying to connect to has Samba or not. It returns it for all calls to mount_smbfs. I did add NETSMB, NETSMBCRYPTO, LIBICONV, LIBMCHAIN, and SMBFS to my kernel config and recompiled as well as issuing kldload smbfs so that smbfs was added to my /boot/loader.conf. If I've done something I shouldn't have please by all means correct me. Zac Brown On Tue, 20 Jan 2004 11:13:46 -0500 Brian Minder [EMAIL PROTECTED] wrote: On Mon, Jan 19, 2004 at 09:27:33PM -0600, Zac Brown wrote: The problems in the earlier post are irrelevant because I figured out I was trying to connect to the wrong IP now but I have a new problem. When I use mount_smbfs I get the following error: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /mnt/home mount_smbfs: unable to open connection: syserr = Connection refused And when I try to mount the nfs share I get the following error: phineas# mount -t nfs 192.168.0.3:/home/zac /mnt/home 192.168.0.3:/home/zac: nfsd: RPCPROG_NFS: Program not registered Any help or enlightenment would be greatly appreciated. Thanks in advance. Make sure you have the following line in your /etc/rc.conf: nfs_client_enable=YES This will start portmap when the system boots. The error you're seeing, RPCPROG_NFS: Program not registered, is nfsd complaining that it can't talk to portmap (which registers RPC services). Sorry, but I don't have any experience with SMBFS mounts, so I can't be of much help there. Hope that helps, -Brian -- [EMAIL PROTECTED]1024/8C7C4DE9 -- Zac Brown http://rufius.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Zac Brown http://rufius.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS Samba problems
Well I'm a new user to FreeBSD, decided I'd give 4.9 a shot yesterday since I had this extra HDD sitting around. Well all goes well, I have video sound working, but now I've run into the snag of getting a hold of my data off of my linux samba/nfs server. When I tried to use mount_smbfs to mount a samba share I received this error: phineas# mount_smbfs -I 192.168.0.4 //[EMAIL PROTECTED]/homes /mnt/home mount_smbfs: unable to open connection: syserr = Operation timed out This of course upset me because using the XFCe4 File Manager I was able to login to the linux samba/nfs server via smbclient and view my data. I hunted long and hard through all the mailing list entries for an answer to my problem and have come up with nothing. I've also googled numerous times on the google.com/bsd site to no avail. I'm really missing the smbmount command because it would all be fine if I could just use that. My next attempt was with NFS in which I setup my linux server with, setup my FreeBSD as a client just as the bsddiary.com version explained. I then issued the command: phineas# mount 192.168.0.4:/home/zac /mnt/home 192.168.0.4:/home/zac: nfsd: RPCPROG_NFS: RPC: Port mapper failure -RPC: Unable to send It repeats the 2nd statement till I press ctrl+c in the console. At this point I'd just be happy to be able to mount a share and listen to my mp3's and access my school work etc. Any help would be greatly appreciated. Thanks in advance, -- Zac Brown http://rufius.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Samba problems
The problems in the earlier post are irrelevant because I figured out I was trying to connect to the wrong IP now but I have a new problem. When I use mount_smbfs I get the following error: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /mnt/home mount_smbfs: unable to open connection: syserr = Connection refused And when I try to mount the nfs share I get the following error: phineas# mount -t nfs 192.168.0.3:/home/zac /mnt/home 192.168.0.3:/home/zac: nfsd: RPCPROG_NFS: Program not registered Any help or enlightenment would be greatly appreciated. Thanks in advance. On Mon, 19 Jan 2004 19:23:35 -0600 Zac Brown [EMAIL PROTECTED] wrote: Well I'm a new user to FreeBSD, decided I'd give 4.9 a shot yesterday since I had this extra HDD sitting around. Well all goes well, I have video sound working, but now I've run into the snag of getting a hold of my data off of my linux samba/nfs server. When I tried to use mount_smbfs to mount a samba share I received this error: phineas# mount_smbfs -I 192.168.0.4 //[EMAIL PROTECTED]/homes /mnt/home mount_smbfs: unable to open connection: syserr = Operation timed out This of course upset me because using the XFCe4 File Manager I was able to login to the linux samba/nfs server via smbclient and view my data. I hunted long and hard through all the mailing list entries for an answer to my problem and have come up with nothing. I've also googled numerous times on the google.com/bsd site to no avail. I'm really missing the smbmount command because it would all be fine if I could just use that. My next attempt was with NFS in which I setup my linux server with, setup my FreeBSD as a client just as the bsddiary.com version explained. I then issued the command: phineas# mount 192.168.0.4:/home/zac /mnt/home 192.168.0.4:/home/zac: nfsd: RPCPROG_NFS: RPC: Port mapper failure -RPC: Unable to send It repeats the 2nd statement till I press ctrl+c in the console. At this point I'd just be happy to be able to mount a share and listen to my mp3's and access my school work etc. Any help would be greatly appreciated. Thanks in advance, -- Zac Brown http://rufius.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Zac Brown http://rufius.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Samba problems
On Monday 19 January 2004 10:27 pm, Zac Brown wrote: The problems in the earlier post are irrelevant because I figured out I was trying to connect to the wrong IP now but I have a new problem. When I use mount_smbfs I get the following error: phineas# mount_smbfs -I 192.168.0.3 //[EMAIL PROTECTED]/homes /mnt/home mount_smbfs: unable to open connection: syserr = Connection refused And when I try to mount the nfs share I get the following error: phineas# mount -t nfs 192.168.0.3:/home/zac /mnt/home 192.168.0.3:/home/zac: nfsd: RPCPROG_NFS: Program not registered Any help or enlightenment would be greatly appreciated. Thanks in advance. Try mount_nfs 192.168.0.3:/home/zac /mnt/home and/or mount_smbfs -I -W YOUR WORKGROUPHERE 192.168.0.3 //[EMAIL PROTECTED]/homes /mnt/home Tim Kellers CPE/NJIT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Samba problems
mount_smbfs -I -W YOUR WORKGROUPHERE 192.168.0.3 //[EMAIL PROTECTED]/homes /mnt/home Arg.. of course that should be mount_smbfs -W YOUR WORKGROUPHERE -I 192.168.0.3 //[EMAIL PROTECTED]/homes Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
samba problems
this may be a wrong list for this question, but I believe that many people should've had the same problems. I get these messages in samba log every now and then read_data: read failure for 4. Error = Connection reset by peer [2003/09/24 12:02:27, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer after that the windows client starts having problems with profiles stored on the server. possibly other problems as well, but I haven't tracked that down. does anyone know what this means ? google shows different opinions about quality of network connection, network cards and drivers, windows patches and other things. Can someone confirm what is the problem ? thank you all ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
