mount_smbfs in base?
is mount_smbfs, smbutil and friends part of base system? this is FreeBSD amd64 9.1-RELEASE then what is extra in samba port? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs in base?
El día Saturday, June 01, 2013 a las 02:09:58AM +0800, Quark escribió: is mount_smbfs, smbutil and friends part of base system? this is FreeBSD amd64 9.1-RELEASE $ which mount_smbfs /usr/sbin/mount_smbfs $ which smbutil /usr/bin/smbutil then what is extra in samba port? a SMB client and server matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - Never being an iSlave WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail phone: +49-170-4527211 | - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs in base?
- Original Message - From: Matthias Apitz g...@unixarea.de To: freebsd-questions@freebsd.org Cc: Sent: Saturday, 1 June 2013 12:01 AM Subject: Re: mount_smbfs in base? El día Saturday, June 01, 2013 a las 02:09:58AM +0800, Quark escribió: is mount_smbfs, smbutil and friends part of base system? this is FreeBSD amd64 9.1-RELEASE $ which mount_smbfs /usr/sbin/mount_smbfs $ which smbutil /usr/bin/smbutil I saw that, but suspected I must have done something stupid that those binaries got placed there. then what is extra in samba port? a SMB client and server so this SMB client is recentish than what is in base? I 'guess' samba was GPL, is it OK to let live GPL s/w in base when such strides are being attempted to oust GCC? matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - Never being an iSlave WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail phone: +49-170-4527211 | - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs in base?
On Fri, May 31, 2013 at 1:41 PM, Quark unixuser2000-f...@yahoo.com wrote: I saw that, but suspected I must have done something stupid that those binaries got placed there. then what is extra in samba port? a SMB client and server so this SMB client is recentish than what is in base? Yes. I 'guess' samba was GPL, is it OK to let live GPL s/w in base when such strides are being attempted to oust GCC? mount_smbfs isn't GPL. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs problem after upgrade Samba 3.4 - 3.5
On 11/03/10 00:04, Bartosz Stec wrote: Hi, Hello! I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //peo at mars http://lists.freebsd.org/mailman/listinfo/freebsd-questions/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. smb://192.168.1.8/%22. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. My knowledge about Samba is limited at best, but it seems that I found possible couse and working override (solution?). Check this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=151887 If this fixes your problem too, please submit followup - more information port maintainer gets, less time he's gonna need to fix this. Yes, it fixed my problem. Submitting followup, thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
re: mount_smbfs problem after upgrade Samba 3.4 - 3.5
Hi, Hello! I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //peo at mars http://lists.freebsd.org/mailman/listinfo/freebsd-questions/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. smb://192.168.1.8/%22. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. My knowledge about Samba is limited at best, but it seems that I found possible couse and working override (solution?). Check this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=151887 If this fixes your problem too, please submit followup - more information port maintainer gets, less time he's gonna need to fix this. -- Bartosz Stec ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mount_smbfs problem after upgrade Samba 3.4 - 3.5
Hi, I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //p...@mars/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs problem after upgrade Samba 3.4 - 3.5
On 10/31/10 14:06, Per olof Ljungmark wrote: Hi, I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //p...@mars/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. Thanks! Just noted another post from yesterday, same issue: Issue wit Samba 3.5.6 and Mac OS X 10.5 I've filed a bug report to see if the maintainer could have a look. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mount_smbfs hostname resolution
I'm trying to mount a share on the ADS of my university. I have, after many hours of tinkering, managed to find out why it doesn't work and even managed to access the share with smbclient. Though I now know (or at least suspect) the cause of the problem, I do not know how to apply the solution. I can reach the ADS server via the -I parameter, which circumvents the local address resolution. However the ads just returns the name of another server to connect to (output excerpts from smbclient -d3): ... got principal=hs-ad-...@ads.hs-karlsruhe.de ... As you can see hs-ad-01 is a local name again. It cannot be resolved and the connection fails. However this can be circumvented by adding a search entry in /etc/resolv.conf: search hs-karlsruhe.de Et voilà: # ping hs-ad-01 PING hs-ad-01.hs-karlsruhe.de (193.196.64.10): 56 data bytes ... And suddenly the smbclient connection works: ... resolve_lmhosts: Attempting lmhosts lookup for name IZ-AD-280x20 resolve_wins: Attempting wins lookup for name IZ-AD-280x20 resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name IZ-AD-280x20 Connecting to 193.196.65.128 at port 445 Connecting to 193.196.65.128 at port 139 ... Another side effect is that I don't have to use the -I parameter any more the smbclient command gets conveniently short: smbclient -U user%pass //ADS/DFS smb: \ Unfortunately this mount_smbfs appears not to use hostname resolution, all that I get from it: # mount_smbfs //user@ads/dfs /mnt/tmp mount_smbfs: can't get server address: syserr = Operation timed out Of course I can use the -I parameter: # mount_smbfs -Iads.hs-karlsruhe.de //user@ads/dfs /mnt/tmp mount_smbfs: unable to open connection: syserr = Connection reset by peer My guess is that moung_smbfs receives the principal (hs-ad-01 is only one of many available candidates among which the load is balanced) and cannot resolve it or even doesn't handle redirection at all. Directly connecting to one of the providers also does not work: # mount_smbfs -Ihs-ad-01 //user@ads/dfs /mnt/tmp mount_smbfs: unable to open connection: syserr = Connection reset by peer With this meagre output I don't really have a way of determining the true nature of the issue. All that I can say is that smbclient works and mount_smbfs does not. Unfortunately the net/samba34 does not install the smbmount utility of the samba suit. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Multiple mount_smbfs commands fail in bash script
Hi all, I'm having some problems with a bash script. It's a backup script that periodically checks if a list of systems is online, and if so, uses samba to mount a specified list of shares, rsyncs them to a local directory and unmounts again. This used to run fine till a few months ago (I don't know what the trigger was that caused them to first fail). Now, when the script is run, it gives the following error when mounting the shares: mount_smbfs: can't get handle to requester (no /dev/nsmb* device) Which is strange, as there are (by last count) 1170 /dev/nsmb* devices in /dev/ (is that normal?) Searching the internet, FreeBSD and Samba mailing lists gave me no recent info, and the old info wasn't helpful. I've narrowed it down to the point where I think it's caused by one process trying to open two (or more) shares at the same time. (a simple script mounting two shares gives the same error). I can mount the shares from the command line without problems, it's only in the bash script it gives me problems. ~/.nsmbrc and /etc/nsmb.conf are correct, smbd, nmbd and winbindd are running. The system is FreeBSD 8.0 Stable. Anyone got any suggestions? Regards, Bernard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Multiple mount_smbfs commands fail in bash script
On Thu, 02 Sep 2010 10:24:05 +0200 Bernard Scharp freebsd-questi...@itsacon.net articulated: Hi all, I'm having some problems with a bash script. It's a backup script that periodically checks if a list of systems is online, and if so, uses samba to mount a specified list of shares, rsyncs them to a local directory and unmounts again. This used to run fine till a few months ago (I don't know what the trigger was that caused them to first fail). Now, when the script is run, it gives the following error when mounting the shares: mount_smbfs: can't get handle to requester (no /dev/nsmb* device) Which is strange, as there are (by last count) 1170 /dev/nsmb* devices in /dev/ (is that normal?) Searching the internet, FreeBSD and Samba mailing lists gave me no recent info, and the old info wasn't helpful. I've narrowed it down to the point where I think it's caused by one process trying to open two (or more) shares at the same time. (a simple script mounting two shares gives the same error). I can mount the shares from the command line without problems, it's only in the bash script it gives me problems. ~/.nsmbrc and /etc/nsmb.conf are correct, smbd, nmbd and winbindd are running. The system is FreeBSD 8.0 Stable. Anyone got any suggestions? Could you post the script? Anything else would be pure guess work. You also might consider posting this on the BASH mail forum: bug-b...@gnu.org although you might have to subscribe first: http://lists.gnu.org/mailman/listinfo/bug-bash -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Vital papers will demonstrate their vitality by spontaneously moving from where you left them to where you can't find them. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Multiple mount_smbfs commands fail in bash script
Could you post the script? Anything else would be pure guess work. You Well, I can recreate it with something as simple as: #!/usr/local/bin/bash mount_smbfs //u...@remotehost/share1/ /tmp/mnt/ mount_smbfs //u...@remotehost/share2/ /tmp/mnt2/ also might consider posting this on the BASH mail forum: bug-b...@gnu.org although you might have to subscribe first: http://lists.gnu.org/mailman/listinfo/bug-bash I'l look into that, (though I doubt this is a bash issue). Thanks! Bernard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Multiple mount_smbfs commands fail in bash script
On Thu, 02 Sep 2010 14:02:35 +0200, Bernard Scharp
freebsd-questi...@itsacon.net wrote:
Could you post the script? Anything else would be pure guess work. You
Well, I can recreate it with something as simple as:
#!/usr/local/bin/bash
mount_smbfs //u...@remotehost/share1/ /tmp/mnt/
mount_smbfs //u...@remotehost/share2/ /tmp/mnt2/
Excuse me, it may just be a stupid question... but... why do
you use bash for this purpose? Do you require any special
bash feature that cannot be done using the standard shell,
sh? I often see the urge to use bash for scripting as a
typical Linuxism, which is usually non-portable (if that
was your goal). FreeBSD's standard scripting shell is sh,
so why not use it until you reach the ends of its functionality?
Just a guess, regarding your initial question, as I don't have
experience with Windows related things: Did you have the
chance to monitor correct operations of your script in the
past? Did the mound and umount (!) calls work properly? Have
you checked your commands running them in the standard dialog
shell (csh)? I assume you're running them as root (or at least
with sufficient permissions), so I don't think the problem
is there, as the error message
mount_smbfs: can't get handle to requester (no /dev/nsmb* device)
doesn't look like refering to that problem.
The error message originates from /usr/src/contrib/smbfs/lib/smb/ctx.c;
having a look around, and remembering that you said
[...] there are (by last count) 1170 /dev/nsmb* devices
in /dev/ (is that normal?)
I found smb_ctx_gethandle() near line 600 (version 7 OS here):
/*
* well, no clone capabilities available - we have to scan
* all devices in order to get free one
*/
for (i = 0; i 1024; i++) {
snprintf(buf, sizeof(buf), /dev/%s%d, NSMB_NAME, i);
fd = open(buf, O_RDWR);
if (fd = 0) {
ctx-ct_fd = fd;
return 0;
}
}
The limit seems to be 1024, if I read that correctly - allthough
I'm considered a C hacker, I'm no OS-level C hacker. :-)
Afterwards, smb_ctx_lookup() fails and gives the error message
mentioned earlier.
Remove the /dev/nsmb* devices and try again. Make sure no other
SMB stuff is currently mounted, just to be sure, as I don't have
any idea what could fail.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Multiple mount_smbfs commands fail in bash script
On 02/09/2010 15:29, Polytropon wrote:
On Thu, 02 Sep 2010 14:02:35 +0200, Bernard Scharp
freebsd-questi...@itsacon.net wrote:
Could you post the script? Anything else would be pure guess work. You
Well, I can recreate it with something as simple as:
#!/usr/local/bin/bash
mount_smbfs //u...@remotehost/share1/ /tmp/mnt/
mount_smbfs //u...@remotehost/share2/ /tmp/mnt2/
Excuse me, it may just be a stupid question... but... why do
you use bash for this purpose? Do you require any special
bash feature that cannot be done using the standard shell,
sh? I often see the urge to use bash for scripting as a
typical Linuxism, which is usually non-portable (if that
was your goal). FreeBSD's standard scripting shell is sh,
so why not use it until you reach the ends of its functionality?
The script above is a (heavily) reduced version, used to isolate the
problem. The real script is much longer, and uses a bunch of logic to
walk through a list of different systems (each with their own lists of
shares, loaded from external files), taking snapshots of the previous
backup, logging which systems were backed up, rolling back operations if
a backup fails, etc.
Just a guess, regarding your initial question, as I don't have
experience with Windows related things: Did you have the
chance to monitor correct operations of your script in the
past? Did the mound and umount (!) calls work properly? Have
you checked your commands running them in the standard dialog
shell (csh)? I assume you're running them as root (or at least
with sufficient permissions), so I don't think the problem
is there, as the error message
mount_smbfs: can't get handle to requester (no /dev/nsmb* device)
doesn't look like refering to that problem.
I am running it as root, and I just tried running the (test)script
(without the bash reference) under a csh shell, and got the same error,
so it's not a bash problem.
As for monitoring the operations of the script, it has worked fine
before (for several years), so I'm pretty sure the code is correct.
The error message originates from /usr/src/contrib/smbfs/lib/smb/ctx.c;
having a look around, and remembering that you said
[...] there are (by last count) 1170 /dev/nsmb* devices
in /dev/ (is that normal?)
I found smb_ctx_gethandle() near line 600 (version 7 OS here):
/*
* well, no clone capabilities available - we have to scan
* all devices in order to get free one
*/
for (i = 0; i 1024; i++) {
snprintf(buf, sizeof(buf), /dev/%s%d, NSMB_NAME, i);
fd = open(buf, O_RDWR);
if (fd = 0) {
ctx-ct_fd = fd;
return 0;
}
}
The limit seems to be 1024, if I read that correctly - allthough
I'm considered a C hacker, I'm no OS-level C hacker. :-)
Neither am I. Hadn't even thought of grepping in /usr/src for the error
message :-)
Afterwards, smb_ctx_lookup() fails and gives the error message
mentioned earlier.
Remove the /dev/nsmb* devices and try again. Make sure no other
SMB stuff is currently mounted, just to be sure, as I don't have
any idea what could fail.
Can I just `rm /dev/nsmbX` them? (messing in /dev/ is a level of FreeBSD
I'm not familiar with)
Thanks for all your help!
Bernard
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Multiple mount_smbfs commands fail in bash script
On Thu, 02 Sep 2010 15:52:25 +0200, Bernard Scharp freebsd-questi...@itsacon.net wrote: Neither am I. Hadn't even thought of grepping in /usr/src for the error message :-) It's often a good starting point to see where problems might be caused from. Can I just `rm /dev/nsmbX` them? (messing in /dev/ is a level of FreeBSD I'm not familiar with) Yes, I would guess so. The content of /dev/ is dynamically generated since FreeBSD 5, if I remember correctly. As the nsmb nodes don't seem to be in use any longer, it would be no problem to remove them. The mount_smbfs program will generate them if needed. Just as an addition: After your script successfully performed the operations needing the mounted SMB shares, it could remove the corresponding device files. Still, this looks like a bug to me, a can't image anybody needs more than 1024 of them kind of bug. I would have imagined that IF a program needs files in a temporary way, it removes them after use. Just to be sure, unmount all SMB related things, as I can't predict what would happen if a nsmb device disappears when in use. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs and Kerberos
Sorry for the necro post.. but the source on mount_smbfs definitely has kerberos options.. http://www.opensource.apple.com/source/smb/smb-431.2/mount_smbfs/mount_smbfs.c mount_smbfs on OSX seems to have Kerberos support, does mount_smbfs on FreeBSD support Kerberos? No, but if it's in Darwin, it shouldn't be that hard to port (although some parts of CIFS seem to be trailing quite a bit). To be honest, I don't see anything about Kerberos in the man pages I have available for Darwin. -- Lowell Gilbert, embedded/networking software engineer, Boston area [url]http://be-well.ilk.org/~lowell/[/url] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mount_smbfs + suspend = kernel panic
Hi guys, I use mount_smbfs on my notebook and I have a little nasty problem.. Sometimes I have kernel panic when resuming after the suspend. The issue seems to happen when I go to suspend with my USB network (WiFi) adapter plugged in (I do use /etc/rc.d/netif stop rum0 before going to suspend), then I resume the notebook without the adapter, then I suspend it again, and finally I resume it with the adapter plugged in. The system panics. Maybe there are any workarounds to avoid the problem.. Should I do umount all smbfs' before I go to suspend?.. Is there any other more elegant way? Here is the kernel buffer and the backtrace: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x20:0xc081fa05 stack pointer = 0x28:0xe8cf2adc frame pointer = 0x28:0xe8cf2af8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 37632 (smbiod4) trap number = 12 panic: page fault cpuid = 0 Uptime: 7d12h57m21s Physical memory: 2022 MB Dumping 275 MB: (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 260 244 228 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 212 196 180 164 148 132 116 100 84 68 52 36 20 4 #0 doadump () at pcpu.h:196 #1 0xc07e8767 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc07e8a39 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc0aecd3c in trap_fatal (frame=0xe8cf2a9c, eva=24) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0aed6bf in trap (frame=0xe8cf2a9c) at /usr/src/sys/i386/i386/trap.c:320 #5 0xc0ad207b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #6 0xc081fa05 in turnstile_broadcast (ts=0x0, queue=0) at /usr/src/sys/kern/subr_turnstile.c:836 #7 0xc07d93f2 in _mtx_unlock_sleep (m=0xc8d82d94, opts=0, file=0xc107c6c3 /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c, line=97) at /usr/src/sys/kern/kern_mutex.c:619 #8 0xc07d9752 in _mtx_unlock_flags (m=0xc8d82d94, opts=0, file=0xc107c6c3 /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c, line=97) at /usr/src/sys/kern/kern_mutex.c:210 #9 0xc106fb73 in smb_iod_invrq (iod=Variable iod is not available. ) at /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c:97 #10 0xc1070d57 in smb_iod_addrq (rqp=0xc8d82d00) at /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c:424 #11 0xc106d28c in smb_rq_enqueue (rqp=0xc8d82d00) at /usr/src/sys/modules/smbfs/../../netsmb/smb_rq.c:193 #12 0xc106d6d8 in smb_rq_simple (rqp=0xc8d82d00) at /usr/src/sys/modules/smbfs/../../netsmb/smb_rq.c:174 #13 0xc106b9e4 in smb_smb_treeconnect (ssp=0xc778d500, scred=0xc7a6e144) at /usr/src/sys/modules/smbfs/../../netsmb/smb_smb.c:561 #14 0xc10708b8 in smb_iod_thread (arg=0xc7a6e100) at /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c:212 #15 0xc07c2159 in fork_exit (callout=0xc10705c0 smb_iod_thread, arg=0xc7a6e100, frame=0xe8cf2d38) at /usr/src/sys/kern/kern_fork.c:810 #16 0xc0ad20f0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 Best regards, EforeZZ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mount_smbfs and Kerberos
mount_smbfs on OSX seems to have Kerberos support, does mount_smbfs on FreeBSD support Kerberos? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs
Is it possible to mount drives on an Active Directory 2003 domain? I've been doing some testing, and I had no problem mounting the netlogon share, but I get an authentication error when I try to mount other drives. (I've altered the hostnames in the examples below.) # mount_smbfs -I domain-controller.utdallas.edu //[EMAIL PROTECTED]/netlogon /mnt/hdrive/ Password: An ls of the mount directory shows the files one would expect to find in our netlogon share. # mount_smbfs -I file-server.utdallas.edu //[EMAIL PROTECTED]/users$/pauls /mnt/hdrive/ Password: mount_smbfs: unable to open connection: syserr = Authentication error I know that the netlogon share doesn't require a logon, but I wonder if the problem isn't that the other mounts require encryption? Is anyone successfully mounting AD 2003 shares on FreeBSD? Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst University of Texas at Dallas http://www.utdallas.edu/ir/security/ smime.p7s Description: S/MIME cryptographic signature
mount_smbfs utf-8
mount_smbfs -E UTF-8:UTF-8 //server/path /mnt/tmp UTF-8 filenames do not show up at all on the FreeBSD 6.2-STABLE client. They show up just fine using smbclient and mounted as nfs, files also show up fine on Windows clients. Is there a limitation with smbfs in handling UTF-8 samba mounts? Or am I giving the wrong options to mount_smbfs? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs 6.2-release and w2k3 standard r2
Hi, I've done lots of googling and I get lots of solutions, but they don't work. I can smbclient to this share just fine: magneto# smbclient -U pgollucci glactus\\unix Password: Domain=[RIDERWAY] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2] smb: \ ls . D0 Fri Jul 6 20:13:59 2007 .. D0 Fri Jul 6 20:13:59 2007 55750 blocks of size 8388608. 55498 blocks available BUT BUT mount_smbfs -W Riderway -I A.B.C.D //[EMAIL PROTECTED]/unix /x1/backups-cdp Password: mount_smbfs: unable to open connection: syserr = Connection refused The share is valid, I can even write to it via smbclient. Does any one have any great ideas ? I've tried with and with -I, -W and replacing HOST with ip out-right. Some machine info below: uname -a FreeBSD magneto. .2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 08:43:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP amd64 kldstat Id Refs AddressSize Name 16 0x8010 967700 kernel 21 0x80a68000 30088smbfs.ko 33 0x80a99000 5358 libiconv.ko 43 0x80a9f000 20a0 libmchain.ko 51 0xb5fea000 9306 ipfw.ko 61 0xb604e000 795 accf_http.ko sysctl kern.securelevel kern.securelevel: 3 ls -ld /var/db/pkg/*samba* magneto# ls -ld /var/db/pkg/*samba* drwxr-xr-x 2 root wheel 512 Jul 6 20:36 /var/db/pkg/samba-3.0.25a,1 drwxr-xr-x 2 root wheel 512 Jul 6 20:19 /var/db/pkg/samba-libsmbclient-3.0.25a_1 namp glactus (the windows box) Not shown: 1665 closed ports PORT STATE SERVICE 25/tcp open smtp 42/tcp open nameserver 80/tcp open http 88/tcp open kerberos-sec 135/tcp open msrpc 389/tcp open ldap 445/tcp open microsoft-ds 464/tcp open kpasswd5 593/tcp open http-rpc-epmap 636/tcp open ldapssl 1025/tcp open NFS-or-IIS 1723/tcp open pptp 3268/tcp open globalcatLDAP 3269/tcp open globalcatLDAPssl 3389/tcp open ms-term-serv MAC Address: 00:1A:A0:1E:1D:DD (Unknown) Device type: general purpose Running: Microsoft Windows 2003/.NET|NT/2K/XP OS details: Microsoft Windows 2003 Server Standart Edition SP1, Microsoft Windows 2003 Server, 2003 Server SP1 or XP Pro SP2 -- Philip M. Gollucci 323.219.4708 Senior System Admin - Riderway, Inc. http://riderway.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs 6.2-release and w2k3 standard r2
On Tuesday 10 July 2007, Philip M. Gollucci wrote: Hi, I've done lots of googling and I get lots of solutions, but they don't work. I can smbclient to this share just fine: magneto# smbclient -U pgollucci glactus\\unix Password: Domain=[RIDERWAY] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2] smb: \ ls . D0 Fri Jul 6 20:13:59 2007 .. D0 Fri Jul 6 20:13:59 2007 55750 blocks of size 8388608. 55498 blocks available BUT BUT mount_smbfs -W Riderway -I A.B.C.D //[EMAIL PROTECTED]/unix /x1/backups-cdp Password: mount_smbfs: unable to open connection: syserr = Connection refused The share is valid, I can even write to it via smbclient. Does any one have any great ideas ? I've tried with and with -I, -W and replacing HOST with ip out-right. IIRC, Win2k3 only uses port 445 for smb/cifs by default, and our mount_smbfs can only use 139 (or thereabouts :) ). It would be nice if mount_smbfs were updated to work more easily with newer versions of Windows, but in the meantime it should be possible to tell the Windows server to also accept connections on the old port. Exactly how I don't remember ATM, but I've done it before. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs 6.2-release and w2k3 standard r2
On Tuesday 10 July 2007, John Nielsen wrote: On Tuesday 10 July 2007, Philip M. Gollucci wrote: Hi, I've done lots of googling and I get lots of solutions, but they don't work. I can smbclient to this share just fine: magneto# smbclient -U pgollucci glactus\\unix Password: Domain=[RIDERWAY] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2] smb: \ ls . D0 Fri Jul 6 20:13:59 2007 .. D0 Fri Jul 6 20:13:59 2007 55750 blocks of size 8388608. 55498 blocks available BUT BUT mount_smbfs -W Riderway -I A.B.C.D //[EMAIL PROTECTED]/unix /x1/backups-cdp Password: mount_smbfs: unable to open connection: syserr = Connection refused The share is valid, I can even write to it via smbclient. Does any one have any great ideas ? I've tried with and with -I, -W and replacing HOST with ip out-right. IIRC, Win2k3 only uses port 445 for smb/cifs by default, and our mount_smbfs can only use 139 (or thereabouts :) ). It would be nice if mount_smbfs were updated to work more easily with newer versions of Windows, but in the meantime it should be possible to tell the Windows server to also accept connections on the old port. Exactly how I don't remember ATM, but I've done it before. I hate not remembering things, so I just verified this on a Windows Server 2003 box I have access to. This feature (listening on port 139) is tied to NETBIOS over TCP/IP. Make sure it's enabled on the WINS tab of the Advanced TCP/IP settings dialog for the interface. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs 6.2-release and w2k3 standard r2
I hate not remembering things, so I just verified this on a Windows Server 2003 box I have access to. This feature (listening on port 139) is tied to NETBIOS over TCP/IP. Make sure it's enabled on the WINS tab of the Advanced TCP/IP settings dialog for the interface. BRILLIANT! Thats the one! Thanks a bunch. -- Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708 Senior System Admin - Riderway, Inc. http://riderway.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mounting external SCO disks and mount_smbfs
Hi all I am trying to mount in my FreeBSD 6,2 box disk that are on a SCO System V Openserver release 5 In SCO it says that the disks filsystem is HTFS. If i try to mount from Fbsd says that there is not external program for this filesystem. What I try is to mount them in order to backup there files. Can I do something to mount them UNIX-UNIX? I have tried to mounting with mount_smbfs because the files are in a Samba share, but when i use cp to backup files to my Fsbd box i get many page errors and timeout. So i dont trust mount_smbfs too much. A solution for this? My actual solution is to Samba share the two box and use a MS Windows with a program i did to do the copy, but i think UNIX will be faster, also will be less network traffic. Thanks in advance Juan Coruña Desarrollo de Software Atlantico ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mounting external SCO disks and mount_smbfs
On 24/05/07, DSA - JCR [EMAIL PROTECTED] wrote: Hi all I am trying to mount in my FreeBSD 6,2 box disk that are on a SCO System V Openserver release 5 In SCO it says that the disks filsystem is HTFS. If i try to mount from Fbsd says that there is not external program for this filesystem. What I try is to mount them in order to backup there files. Can I do something to mount them UNIX-UNIX? I have tried to mounting with mount_smbfs because the files are in a Samba share, but when i use cp to backup files to my Fsbd box i get many page errors and timeout. So i dont trust mount_smbfs too much. A solution for this? Yes, just use a backup client/system of your choice. Copying them to windows is not the first choise, neither is mounting the disk on a FreeBSD-Box. BTW: If you want to do something like this you should use NFS. I would recommend a backup method that is native to SCO. I never used it so I don't know what is available, but there should be something like dump. This will do a backup on the filesystem level and allows incremental backups. There is at least a cpio available. So you create some files containing your backups, and you can transfer them to a remote machine... Alternatively you could check wether there is a backup solution available for SCO. HTH Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error from mount_smbfs
Scott D Friedemann [EMAIL PROTECTED] writes: FreeBSD 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #0 I have run mount_smbfs for the last couple years without incident. Now I find the command no longer works, but gives this error. mount_smbfs -I 192.168.1.100 //drogo/c /mnt/bsdstuff Password: mount_smbfs: unable to open connection: syserr = Cannot allocate memory Can anyone offer a clue? I tracked it as far as an ioctl call for creating what looks like a protocol block. I don't have the time to trace into the kernel right now, and it doesn't look like anything in the smbtools userland has changed in quite a while. Can we assume that you checked the obvious things, like making sure that the system isn't running out of memory? Does this happen with a GENERIC kernel? Are you sure the kernel matches the userland? Also let us know if you can recall when it stopped working. And for what it's worth, I don't get such an error on -STABLE. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error from mount_smbfs
Lowell Gilbert wrote: I tracked it as far as an ioctl call for creating what looks like a protocol block. I don't have the time to trace into the kernel right now, and it doesn't look like anything in the smbtools userland has changed in quite a while. Can we assume that you checked the obvious things, like making sure that the system isn't running out of memory? Does this happen with a GENERIC kernel? Are you sure the kernel matches the userland? Also let us know if you can recall when it stopped working. And for what it's worth, I don't get such an error on -STABLE. I decided to update sources (still patch level 3), build world and the GENERIC kernel and see what happens. No change. Same error. This will occur logging in as root to a console on a machine with 1GB RAM, so memory is not an issue. Building my custom kernel, which has very little customization, yields the same error as before, too. I last used this successfully 16 February 2007. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Error from mount_smbfs
FreeBSD 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #0 I have run mount_smbfs for the last couple years without incident. Now I find the command no longer works, but gives this error. mount_smbfs -I 192.168.1.100 //drogo/c /mnt/bsdstuff Password: mount_smbfs: unable to open connection: syserr = Cannot allocate memory Can anyone offer a clue? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs: charset convertion (-E) doesn't work
Hello. I tried a lot of different methods but I cannot mount a Windows share which is in GB18030 charset to my FreeBSD host in UTF-8 charset. I always gets junk text. this process is better illustrated with this screenshot (I don't copy and paste the console text because that way the junk character in it might confuse email clinets). gopher://sdf.lonestar.org/I/users/weiwu/mount_chinese_smbshare.png In the screenshot, I do have mounted the share with -E parameter which should convert GB18030 folder names to UTF-8 but actually no convertion is done (see the ls | iconv which shows what it should be looking like if the convertion is done) Actually I have never succesfully done charset convertion with mount_smbfs, what did I do wrong? -E parameter which should convert GB18030 folder names to UTF-8 but actually no convertion is done (see the ls | iconv which shows what it should be looking like if the convertion is done) Actually I have never succesfully done charset convertion with mount_smbfs, what did I do wrong? -- [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs/umount for non root user.
Running mount_smbfs as a regular user generates a permission denial in relation to iconv in the kernel. This is apparently a well known problem which can be circumvented by setting the set-user-id-on-execution bit for mount_smbfs. This works for me but leads to the problem that the mount is now seen as belonging to root and the regular user gets a denial on umount. Allowing regular users to mount smb shares with mount_smbfs seems to me fairly benign but to set the set-user-id-on-execution bit for umount would be extremely dangerous. Is there a way around this problem -- this is under FreeBSD 5.4. Taking a look at the sources for mount_smbfs and the associated library, libsmb, I see that conditional compilation for APPLE (Darwin?) switches the effective user id when the set-user-id-on-execution bit is set with the code executed mostly under the identity of the real user and switching to privileged mode only for a few brief activities - notably for installing the iconv table and a few error conditions. Apart from this the code looks very similar to (but not quite identical with) the FreeBSD code. I presume (without any real justification) that these differences in the APPLE version are intended to circumvent the difficulty I am having when running under Darwin. The question is if I modify the FreeBSD code to perform similar switchings of effective user id and recompile am I likely to achieve my desired goal? Has anyone else tried this? Any comments would be welcome. Malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: free-bsd's mount_smbfs having issues with EMC Celerra
The right stuff: sudo mount_smbfs -I server name NOT ip - don't ask me why, I don't know -W workgroup/domain name -d 550 -f 550 //myusername@server name NOT ip - I can answer this if you don't know and ask me why/share mount point That's about it. On 8/30/06, Antony Mawer [EMAIL PROTECTED] wrote: On 31/08/2006 2:18 AM, Jim Stapleton wrote: nevermind, my own dumb mistake with the connection string, first I didn't have the right stuff for logging into a domain, second time around when that was fixed, I had a / where there should have been an @. What was the right stuff for logging into a domain? Can you give an example command line? We've seen some machines where we had to add the -W parameter with the domain name (as the workgroup name, go figure) in order to get mount_smbfs to work... yet smbclient will happily figure this out itself. Cheers Antony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
free-bsd's mount_smbfs having issues with EMC Celerra
I'm trying to connect my FreeBSD notebook to some shares at work, which are on an EMC Celerra box, which uses the windows SMB protocol, but I keep getting an odd error, which right now I'm suspecting is an incompatability between the two, and I was wondering if anyone here has had previous experience with this: 1) I can mount_smbfs shares on my windows desktop at home 2) People here can mount drives on the celerra box from Windows and Linux 3) Every time I try to map a share from FreeBSD, I get the error: mount_smbfs: unable to open connection: resource temporarily unavailable And no, I am not installing windows/linux on my notebook to get this (and sound) working, each has it's own issues which make it much worse for my uses. :-P Thanks -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: free-bsd's mount_smbfs having issues with EMC Celerra
nevermind, my own dumb mistake with the connection string, first I didn't have the right stuff for logging into a domain, second time around when that was fixed, I had a / where there should have been an @. Just point, laugh and make funny faces at me, I deserve it for the latter error. Thanks, -Jim Stapleton On 8/30/06, Jim Stapleton [EMAIL PROTECTED] wrote: I'm trying to connect my FreeBSD notebook to some shares at work, which are on an EMC Celerra box, which uses the windows SMB protocol, but I keep getting an odd error, which right now I'm suspecting is an incompatability between the two, and I was wondering if anyone here has had previous experience with this: 1) I can mount_smbfs shares on my windows desktop at home 2) People here can mount drives on the celerra box from Windows and Linux 3) Every time I try to map a share from FreeBSD, I get the error: mount_smbfs: unable to open connection: resource temporarily unavailable And no, I am not installing windows/linux on my notebook to get this (and sound) working, each has it's own issues which make it much worse for my uses. :-P Thanks -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs LIBSMBCRYPTO [was Re: Kernel module path]
On Wed, 7 Jun 2006 12:28:46 -0500 Nikolas Britton [EMAIL PROTECTED] wrote: (snip) Do you know if they ever fix crypto bug in mount_smbfs in FreeBSD 6.1? Yeah, they did... Assuming you're thinking of the same thing I am, whereby attempting to authenticate to a server for SMB access resulted in being told that cryptography wasn't availabl e (or some such). I think it had something to do with a LIBSMBCRYPTO setting, or similar, but can't recall. -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs locking?
Hi!
Are there any mechanism to lock files (as the Win-clients), shared by
a Windows-server, and reached on a smbfs-mounted file system? I haven'
found any mount options in mount_smbfs's manual.
Bye,
Gábor
--
#!/bin/ksh
Z='21N16I25C25E30, 40M30E33E25T15U!';IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ
';set -- $Z;for i;{ [[ $i = ? ]]print $ibreak;[[ $i = ???
]]j=$ii=${i%?};typeset -i40 i=8#$i;print -n ${i#???};[[ $j = ???
]]print -n ${j#??} j=;typeset +i i;};IFS=' 0123456789 ';set --
$Z;for i;{ [[ $i = , ]]i=2;[[ $i = ?? ]]||typeset -l i;j=$j
$i;typeset +l i;};print $j
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs and NETSMBCRYPTO
Greetings, I have recently run into a problem mounting windows shares on my 6.1 Beta 2 laptop. smbfs is loaded via loader.conf, but I get an error message stating that encryption support is not available. According to this thread: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-02/msg00556.html I now need to add options NETSMBCRYPTO To my kernel config to get encryption support added for mount_smbfs? I am currently running a generic kernel and I have never needed to do this in the past just to mount a windows share. Has something changed recently and I will need to do a buildworld to fix this? I tried kldload netsmbcrypto but I guess the file does not exist. Is there any way for me to mount a windows share without doing a buildworld? I did not pull sources when I built the machine as I intended to just run generic and load anything extra via loader.conf. Thanks for any pointers on this. -Derrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs and NETSMBCRYPTO
Derrick Ryalls wrote: Greetings, I have recently run into a problem mounting windows shares on my 6.1 Beta 2 laptop. smbfs is loaded via loader.conf, but I get an error message stating that encryption support is not available. According to this thread: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-02/msg00556.html I now need to add options NETSMBCRYPTO To my kernel config to get encryption support added for mount_smbfs? Yes. That will fix it. I am currently running a generic kernel and I have never needed to do this in the past just to mount a windows share. Has something changed recently and I will need to do a buildworld to fix this? FWIW... I (and others) were bitten by this. There was a thread not long ago with a few complaining about the change breaking POLA, and possibly an explanation as to why it was changed. However, I can't seem to dig it, or anything for that matter, up out of the archives. Others have mentioned the archive search not working well lately... so you might wait another day or two and search through the archives for the reason why it was changed. I tried kldload netsmbcrypto but I guess the file does not exist. Is there any way for me to mount a windows share without doing a buildworld? I did not pull sources when I built the machine as I intended to just run generic and load anything extra via loader.conf. Thanks for any pointers on this. -Derrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs performance
Hello all, I have the smbfs performance problem while connecting to the Windows (w2k3) share in the AD environment, wint 6.1-PRERELEASE - with the filesystem mounted through mount_smbfs i get 300-350 kBps (kiloBytes per sec) speed, while through the smbclient i get the speeds in excess of 8MB/s. Is this possible bug in mount_smbfs or just the simple misconfiguration? I have configured the /etc/nsmb.conf file as per manual and it really gets connected nicely but afterwards it presents me with catastrophic results. With respect Nenad Mihajlovic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Conflict? :smbfs built in support and mount_smbfs
Hi, I had my kernel built with the following options options NETSMB #SMB/CIFS requester options NETSMBCRYPTO#encrypted password support for SMB which I understand adds the support for smbfs into the kernel itself. BUT when using either mount -t smbfs or mount_smfs , I would get: [SOMETHING ELSE HERE, $0 possibly] can't load smbfs: File exists (aprox error ), implying that it was trying to load the smbfs.ko ... but conflicting with the code built into the kernel? The worse part is that the mount command would fail. I commented out those 2 options *only* and everything works fine again. What gives? Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Conflict? :smbfs built in support and mount_smbfs
Norberto Meijome wrote: Hi, I had my kernel built with the following options options NETSMB #SMB/CIFS requester options NETSMBCRYPTO#encrypted password support for SMB which I understand adds the support for smbfs into the kernel itself. BUT when using either mount -t smbfs or mount_smfs , I would get: [SOMETHING ELSE HERE, $0 possibly] can't load smbfs: File exists (aprox error ), implying that it was trying to load the smbfs.ko ... but conflicting with the code built into the kernel? The worse part is that the mount command would fail. I commented out those 2 options *only* and everything works fine again. What gives? Beto Sorry, forgot to include version info. Freebsd 6.0 Stable, built on Jan 30th 06. world built on Jan 31st , src/contrib/smbfs/mount_smbfs/mount_smbfs.c,v 1.5 2004/09/05 06:42 Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs file name problem
On Mon, Dec 12, 2005 at 12:10:01PM -0500, Incoming Mail List wrote: I've got a problem with file names containing : and ? characters when mounted via mount_smbfs. I have two FBSD machines running SAMBA. Machine-1 mounts a file system from Machine-2 using mount_smbfs(). The ls() command converts a file name such as XX:YY to something like X~Y. If I run tar() to backup XX:YY, it reports an error (tar: X~Y: no such file or directory). AFAIK ':' in filenames _will_ cause problems on Windows. So I dont see any reason share files with ':' via Samba ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs file name problem
I've got a problem with file names containing : and ? characters when mounted via mount_smbfs. I have two FBSD machines running SAMBA. Machine-1 mounts a file system from Machine-2 using mount_smbfs(). The ls() command converts a file name such as XX:YY to something like X~Y. If I run tar() to backup XX:YY, it reports an error (tar: X~Y: no such file or directory). So it appears that when tar() recursively goes down a directory hierarchy and finds the file, it gets the name as X~Y. But when it trys to add the file to the archive, it fails because there is no file on the system with the name X~Y. Is this something that the charsets definition in nsmb.conf can fix? If so, what are the character sets I should use? If not, is there a solution for this issue? Thanks, Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs issue
I am getting an inconsistency when I try to use perl to access file in a smbfs mounted Win XP directory structure My kernel is at 4.11p3. Any help in resolving this problem would be much appreciated. # smbfs mount command which mounts a WinXP share ShareDir on my FreeBSD # box. The directory ~/ShareDir has rwx permissions for ugo. sudo mount_smbfs -N -I dodo -u me -g ggg //[EMAIL PROTECTED]/SharedDir ~/SharedDir # directory/file structure is correct ls -FCR SharedDir/ DirOne/ DirThree/ DirTwo/ SharedDir/DirOne: DSCN1090.JPG* DSCN1091.JPG* DSCN1092.JPG* SharedDir/DirThree: DSCN0820.JPG* ParkStreet.JPG* VicRooms.JPG* SharedDir/DirTwo: Oeuvre17.JPG* # now look at the directory/file structure with find # looks good find SharedDir -print SharedDir SharedDir/DirOne SharedDir/DirOne/DSCN1090.JPG SharedDir/DirOne/DSCN1091.JPG SharedDir/DirOne/DSCN1092.JPG SharedDir/DirThree SharedDir/DirThree/DSCN0820.JPG SharedDir/DirThree/ParkStreet.JPG SharedDir/DirThree/VicRooms.JPG SharedDir/DirTwo SharedDir/DirTwo/Oeuvre17.JPG # translate the find command to perl and run the perl script # PROBLEM the files no longer appear find2perl SharedDir -print testcase.pl perl testcase.pl SharedDir SharedDir/DirOne SharedDir/DirThree SharedDir/DirTwo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs variable error
On Wed, 23 Mar 2005 23:39:58 -0500, jason henson [EMAIL PROTECTED] wrote: John DeStefano wrote: I get the following error when I try to mount_smbfs a LAN file share as root with 5.3-RELEASE and a GENERIC kernel, both cvsup-ed and compiled this past weekend: /usr/libexec/ld-elf.so.1: mount_smbfs: Undefined symbol vfsisloadable I can't find a whole lot of information about this error. But apparently, vfsisloadable is an outdated parameter that should no longer be referenced in the source. The only other reference I found to this error was a kernel that was missing the proper support, but it seemed that a GENERIC kernel would take care of that. Any ideas on how to verify that my system has got whatever mount_smbfs may need to operate properly, or how to remedy the error? Thank you, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-04/0699.html Did you do a kldstat to see if smbfs.ko is there? It is no longer in GENERIC. Hi Jason, I too found that link, which is where I got the idea that vfsisloadable was an outdated parameter, but I saw that loading the smb_fs module generated an error for that user, so I didn't follow up on that information. I'm glad you pointed this out though, as loading the kernel module works for me. But without your response, how would I ever have known this? It's certainly not mentioned in UPDATING, and the error output was not helpful. Where would I have found this information? Thanks, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs variable error
On Thu, 24 Mar 2005 09:47:44 -0500, John DeStefano [EMAIL PROTECTED] wrote: On Wed, 23 Mar 2005 23:39:58 -0500, jason henson [EMAIL PROTECTED] wrote: John DeStefano wrote: I get the following error when I try to mount_smbfs a LAN file share as root with 5.3-RELEASE and a GENERIC kernel, both cvsup-ed and compiled this past weekend: /usr/libexec/ld-elf.so.1: mount_smbfs: Undefined symbol vfsisloadable I can't find a whole lot of information about this error. But apparently, vfsisloadable is an outdated parameter that should no longer be referenced in the source. The only other reference I found to this error was a kernel that was missing the proper support, but it seemed that a GENERIC kernel would take care of that. Any ideas on how to verify that my system has got whatever mount_smbfs may need to operate properly, or how to remedy the error? Thank you, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-04/0699.html Did you do a kldstat to see if smbfs.ko is there? It is no longer in GENERIC. Hi Jason, I too found that link, which is where I got the idea that vfsisloadable was an outdated parameter, but I saw that loading the smb_fs module generated an error for that user, so I didn't follow up on that information. I'm glad you pointed this out though, as loading the kernel module works for me. But without your response, how would I ever have known this? It's certainly not mentioned in UPDATING, and the error output was not helpful. Where would I have found this information? Thanks, ~John Could someone please direct me to where I can read about when and why the smbfs module was removed from the GENERIC kernel? I can't find it, and it's not in UPDATING or the release notes. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs variable error
John DeStefano wrote: On Wed, 23 Mar 2005 23:39:58 -0500, jason henson [EMAIL PROTECTED] wrote: John DeStefano wrote: I get the following error when I try to mount_smbfs a LAN file share as root with 5.3-RELEASE and a GENERIC kernel, both cvsup-ed and compiled this past weekend: /usr/libexec/ld-elf.so.1: mount_smbfs: Undefined symbol vfsisloadable I can't find a whole lot of information about this error. But apparently, vfsisloadable is an outdated parameter that should no longer be referenced in the source. The only other reference I found to this error was a kernel that was missing the proper support, but it seemed that a GENERIC kernel would take care of that. Any ideas on how to verify that my system has got whatever mount_smbfs may need to operate properly, or how to remedy the error? Thank you, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-04/0699.html Did you do a kldstat to see if smbfs.ko is there? It is no longer in GENERIC. Hi Jason, I too found that link, which is where I got the idea that vfsisloadable was an outdated parameter, but I saw that loading the smb_fs module generated an error for that user, so I didn't follow up on that information. I'm glad you pointed this out though, as loading the kernel module works for me. But without your response, how would I ever have known this? It's certainly not mentioned in UPDATING, and the error output was not helpful. Where would I have found this information? Thanks, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I just found it with google by cutting and pasting. I then did some reading. I find the archive search at freebsd.org kind of sucks. You could also try google.com/bsd. This was also on the current mailing list. I was thinking about submitting something to the doc project about stuff I find, but in the past they have emailed me back showing me it was already in them(usaully in a faq). So I haven't sent to many new items to them. Also in the past I have done a diff between my kernel conf and GENERIC to see the changes between updates, but I have learned most of it well enough to spot most things now. I also don't build in anything I can load. I guess you would have never have know with out many hours of poking around your system, but thats what these lists are for right? :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs variable error
John DeStefano wrote: On Thu, 24 Mar 2005 09:47:44 -0500, John DeStefano [EMAIL PROTECTED] wrote: On Wed, 23 Mar 2005 23:39:58 -0500, jason henson [EMAIL PROTECTED] wrote: John DeStefano wrote: I get the following error when I try to mount_smbfs a LAN file share as root with 5.3-RELEASE and a GENERIC kernel, both cvsup-ed and compiled this past weekend: /usr/libexec/ld-elf.so.1: mount_smbfs: Undefined symbol vfsisloadable I can't find a whole lot of information about this error. But apparently, vfsisloadable is an outdated parameter that should no longer be referenced in the source. The only other reference I found to this error was a kernel that was missing the proper support, but it seemed that a GENERIC kernel would take care of that. Any ideas on how to verify that my system has got whatever mount_smbfs may need to operate properly, or how to remedy the error? Thank you, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-04/0699.html Did you do a kldstat to see if smbfs.ko is there? It is no longer in GENERIC. Hi Jason, I too found that link, which is where I got the idea that vfsisloadable was an outdated parameter, but I saw that loading the smb_fs module generated an error for that user, so I didn't follow up on that information. I'm glad you pointed this out though, as loading the kernel module works for me. But without your response, how would I ever have known this? It's certainly not mentioned in UPDATING, and the error output was not helpful. Where would I have found this information? Thanks, ~John Could someone please direct me to where I can read about when and why the smbfs module was removed from the GENERIC kernel? I can't find it, and it's not in UPDATING or the release notes. Thanks. My mistake, it was never in GENERIC. Or I can't find were it was. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/conf/GENERIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs variable error
I get the following error when I try to mount_smbfs a LAN file share as root with 5.3-RELEASE and a GENERIC kernel, both cvsup-ed and compiled this past weekend: /usr/libexec/ld-elf.so.1: mount_smbfs: Undefined symbol vfsisloadable I can't find a whole lot of information about this error. But apparently, vfsisloadable is an outdated parameter that should no longer be referenced in the source. The only other reference I found to this error was a kernel that was missing the proper support, but it seemed that a GENERIC kernel would take care of that. Any ideas on how to verify that my system has got whatever mount_smbfs may need to operate properly, or how to remedy the error? Thank you, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs variable error
John DeStefano wrote: I get the following error when I try to mount_smbfs a LAN file share as root with 5.3-RELEASE and a GENERIC kernel, both cvsup-ed and compiled this past weekend: /usr/libexec/ld-elf.so.1: mount_smbfs: Undefined symbol vfsisloadable I can't find a whole lot of information about this error. But apparently, vfsisloadable is an outdated parameter that should no longer be referenced in the source. The only other reference I found to this error was a kernel that was missing the proper support, but it seemed that a GENERIC kernel would take care of that. Any ideas on how to verify that my system has got whatever mount_smbfs may need to operate properly, or how to remedy the error? Thank you, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-04/0699.html Did you do a kldstat to see if smbfs.ko is there? It is no longer in GENERIC. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs can't get handle to requester
I have a box running 4.5. I try to execute the mount_smbfs I get mount_smbfs: can't get handle to requester (no /dev/nsmb* device). When I do an ls of the /dev directory I see the following devices: /dev/nsmb0 /dev/smb0 /dev/smb1 Anyone seen this before? Ray ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs without entering password
Petre Bandac wrote: I can't make mount_smbfs to work with the -N switch (ie read its passwords from ~/.nsmbrc) sudo mount_smbfs -I IP-address //[EMAIL PROTECTED]/share /mnt/share works while sudo mount_smbfs -N -I IP-address //[EMAIL PROTECTED]/share /mnt/share gives mount_smbfs: unable to open connection: syserr = Authentication error Where is the ~/.nsmbrc file? -- [WBR], Arcade. [SAT Astronomy/Think to survive!] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs without entering password
I can't make mount_smbfs to work with the -N switch (ie read its passwords from ~/.nsmbrc) sudo mount_smbfs -I IP-address //[EMAIL PROTECTED]/share /mnt/share works while sudo mount_smbfs -N -I IP-address //[EMAIL PROTECTED]/share /mnt/share gives mount_smbfs: unable to open connection: syserr = Authentication error .nsmbrc looks like this # [82.xx.xx.xx:petre:share] password=$$1785a52273d [superduda:petre:share] password=$$1785a52273d [netbios_name:petre] password=$$1785a52273d [82.xx.xx.xx6:petre] password=$$1785a52273d what's the problem ? thanks, petre -- Login: petreName: Petre Bandac Directory: /home/petre Shell: /usr/local/bin/zsh On since Fri Feb 25 17:28 (EET) on ttyv0, idle 4 days 0:05 (messages off) Last login Sun Feb 27 23:26 (EET) on ttyp6 from lubyanka.kgb.ro New mail received Fri Feb 25 18:30 2005 (EET) Unread since Wed Feb 23 16:47 2005 (EET) No Plan. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with mount_smbfs (not working for me)
On Wed, 3 Nov 2004 08:41:24 +0100, Axel S. Gruner [EMAIL PROTECTED] wrote: Hi. I run into a problem with mount_smbfs. Trying to mount a SMB-share on a AS/400 from a FreeBSD 4.10 or FreeBSD 5.3-RC1 gives me the error: mount_smbfs: unable to open connection: syserr = Connection reset by peer Well, i dont like Mr. Peer, and, trying to reach the SMB-share via smbclient works perfectly (but i need a mount on my FreeBSD-System, so thats no choice). Also if i try to mount the SMB-share from a SuSE Linux Box (with mount -t smbfs) it will work, as a result, i think the problem is not the share, it must be mount_smbfs. The syntax i tried was: mount_smbfs -I 10.4.1.222 //[EMAIL PROTECTED]/sfimages /mnt also with the FQDN: mount_smbfs -I suedzwo.suedfac.com //[EMAIL PROTECTED]/sfimages /mnt You have to use the netbios name of your samba server. Change 10.4.1.222 to the netbios name. mount_smbfs -I 10.4.1.222 //[EMAIL PROTECTED]/sfimages /mnt or mount_smbfs -I suedzwo.suedfac.com //[EMAIL PROTECTED]/sfimages /mnt Nelis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with mount_smbfs (not working for me)
Hi Nelis! On Wed, 03 Nov 2004, Nelis Lamprecht wrote: You have to use the netbios name of your samba server. Change 10.4.1.222 to the netbios name. mount_smbfs -I 10.4.1.222 //[EMAIL PROTECTED]/sfimages /mnt or mount_smbfs -I suedzwo.suedfac.com //[EMAIL PROTECTED]/sfimages /mnt Thanks for the quick reply. It does not fix the problem. Why? Because the netbios name was not suedzwo it is a weird QS55SCCB: mount_smbfs -I suedzwo.suedfac.com //[EMAIL PROTECTED]/sfimages /mnt/as400 That worked. Only problem, if i use the /etc/nsmb.conf file, the authentications is not working. I will fix that later for my own. asg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with mount_smbfs (not working for me)
Hi. I run into a problem with mount_smbfs. Trying to mount a SMB-share on a AS/400 from a FreeBSD 4.10 or FreeBSD 5.3-RC1 gives me the error: mount_smbfs: unable to open connection: syserr = Connection reset by peer Well, i dont like Mr. Peer, and, trying to reach the SMB-share via smbclient works perfectly (but i need a mount on my FreeBSD-System, so thats no choice). Also if i try to mount the SMB-share from a SuSE Linux Box (with mount -t smbfs) it will work, as a result, i think the problem is not the share, it must be mount_smbfs. The syntax i tried was: mount_smbfs -I 10.4.1.222 //[EMAIL PROTECTED]/sfimages /mnt also with the FQDN: mount_smbfs -I suedzwo.suedfac.com //[EMAIL PROTECTED]/sfimages /mnt After typing the password, the error message above came up. Thats it. So, the question is, whats wrong with my syntax, or what could cause the problem? On my FreeBSD 4.10 box i also have the following stuff compiled in the kernel: options NETSMB options NETSMBCRYPTO options LIBMCHAIN options LIBICONV options SMBFS Thanks in advance. asg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs
Not sure about right ML (maybe fs@), feel free to forward to another
one if needed. And please Cc: me.
Background:
- I need to syncronize two dir hosted on win machines based on data
contained into an Oracle DB (direction of copy may change based on
owner of file as specified into the DB). I made an sh script that
generate a big Makefile with right direction of cp -p but it fail
copying a lot of identical file (identical means same md5 and with
date of past, already copied previous night (and previous and...).
(a lot of fuzzy word, problem is timestamping a remote smb file).
Environment:
- a freebsd machine (I tested on 4.9-STABLE and 4.10-STABLE)
- at least a real win machine with a NTFS exported share (my real
case has one w2k-server and one wnt4-server).
How to reproduce:
- create a mount point, mount_smb the win share, touch a file
// on the mount point (or at any level deep):
// (you can also change example time but please use even/odd seconds)
//
# foreach s ( `jot -w%02d 10` )
foreach? touch -t 200401020304.${s} sample${s}
foreach? end
# ls -lnT sample*
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:00 2004 sample01
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:02 2004 sample02
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:02 2004 sample03
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:04 2004 sample04
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:04 2004 sample05
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:06 2004 sample06
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:06 2004 sample07
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:08 2004 sample08
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:08 2004 sample09
-rwxr-xr-x 1 0 0 0 Jan 2 03:04:10 2004 sample10
Any datetime will be rounded up to previous even second :-(
If you create a file from the win-side (with touch or notepad or
with your favourite tool) you can specify odd seconds, this means
that is not a NTFS struct limitations (maybe :-).
Who round my time? I need this for an exotic job: syncronize two
win machine using data from an Oracle DB. My approach was using
a Makefile but every night it copies hundreds of already copied
files and it use an expensive WAN link. Yes, I can switch to more
robust check, md5 signatures, extraction of time and manual check
with rounded values, but any other approach leave this problem...
--
TIA,
Riccardo.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs
Why shouldn't it be? Because it's counterintuitive. Unless there's a method to use the multiple mount points as separate entry points to the file system for specialized program transactions similar to the Tru64 FFM file system, what's the point of having it mount itself back over itself on the same mount point? If nothing else, it creates more entries in the mount table and wastes resources. And it really doesn't matter whether you mount via smbfs or nfs multiple times on the same client or once on multiple clients, does it? No, it's not a technical issue for the OS, but it can make for painful system management. If you create an application that allows users to mount up a windows share to access it, you could end up with an unlimited number of mounts for the same file system. When it comes time to unmount that file system, if you haven't kept track of how many times it was mounted you'll have to keep inspecting the mount points to determine when the last unmount has occured or your file system will still be mounted. The application can certainly check the mount status when called upon to mount the file system, but it is convenient to depend upon the mount system calls (in the case of ufs) to return an error when the file system is already mounted. Is there a technical requirement, or benefit, for allowing multiple smbfs mounts of a windows share on the same mount point? -- The mount_smbfs(8) command on 5.2.1 allows multiple mounts using the same source and mount point. This sounds like a bug to me since other file systems such as ufs return an error on such attempts. Anyone know of a reason why this is allowed in mount_smbfs? Why shouldn't it be? The same holds true for nfs. And it really doesn't matter whether you mount via smbfs or nfs multiple times on the same client or once on multiple clients, does it? If you mount one or more times, if you use ufs or any other fs, it is always possible to write simultaneously to one and the same file leading to data loss. That's Unix since the early 1970s, isn't it? Of course you cannot mount a ufs more than once, but that's because the kernel needs to manage the buffer cache non-ambiguously to preserve data consistency in the fs structure. Regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs
The mount_smbfs(8) command on 5.2.1 allows multiple mounts using the same source and mount point. This sounds like a bug to me since other file systems such as ufs return an error on such attempts. Anyone know of a reason why this is allowed in mount_smbfs? J ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs
On Fri, 30 Jul 2004, jon wrote: The mount_smbfs(8) command on 5.2.1 allows multiple mounts using the same source and mount point. This sounds like a bug to me since other file systems such as ufs return an error on such attempts. Anyone know of a reason why this is allowed in mount_smbfs? Why shouldn't it be? The same holds true for nfs. And it really doesn't matter whether you mount via smbfs or nfs multiple times on the same client or once on multiple clients, does it? If you mount one or more times, if you use ufs or any other fs, it is always possible to write simultaneously to one and the same file leading to data loss. That's Unix since the early 1970s, isn't it? Of course you cannot mount a ufs more than once, but that's because the kernel needs to manage the buffer cache non-ambiguously to preserve data consistency in the fs structure. Regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble with mount_smbfs and files with a EURO symbol.
Hi all, I'm making a backup server that needs to copy files from win2k servers using mount_smbfs. Everything is working fine, except for files that contain the '¤' (euro) symbol. It seems that cp doesn't like this, and changes it in a question mark and the file will not be copied. Any ideas? Thanks in advance, Danny PS: first message to this list, nice to meet you all ;-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4.9 mount_smbfs
I have a samba share mounted with mount_smbfs. Afterwards if I open a file on this share from another client, I got permission denied on my own until I close this file on the other client. I have checked the smbstatus on the server and got result with deny_none and no oplocks ... Also meanwhile this file is open it can be read by other clients(fbsd5.0,linux,win). I was told to sniff the traffic, here is what I've got: SMBError - ERRDOS - ERRbadshare The sharing mode specified for an Open conflicts with existing FIDs on the file. Both the server and client are 4.9 with same samba version ... Any advice appreciated -- _(_)_ (_. o_)F3CZ0 (_,) http://feczo.nmi.rulez.org ()__ // // ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9 mount_smbfs
oh one more thing: smbclient works fine so during the file is open by another client I got permission denied if I would like to access the file through the mounted dir, and from smbclient I can get the file without errors on the same machine ... -- _(_)_ (_. o_)F3CZ0 (_,) http://feczo.nmi.rulez.org ()__ // // ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Performance over network with mount_smbfs (warning large mail)
I have a Windows 2003 machine(2) with a share mounted on a Freebsd machine (1) via mount_smbfs Hardware Machine 1 FreeBSD pcmarpxy.mine.nu 4.9-STABLE FreeBSD 4.9-STABLE #1: Fri Jan 30 23:33:38 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MARK i386 PIII 650, 392mb ram system : ata-100 5400 disks on builtin ide data :- 2 ata-100 disks on a promise ata card running under vinum (software raid) raid 0 - real men always run raid 0 :-) BSD is recently cvsupped and compiled etc... samba Version 3.0.1 Machine 2 Windows 2003 all patches. PIII 500 with a promise atx raid card and a pair of 30gb ata-100 5400 rpm. (also raid 0) The machines are connected via a switch running 100mb all interfaces, ports are manually set to 100mb full duplex, neither machine is exactly overloaded. I backup to machine 2 (40gb) via an smb mount to a Windows 2003 server. with smbfs 167604556 bytes sent in 8m.15.133 (330 Kbytes/s) With ftp 167604556 bytes sent in 15.06 seconds (10.62 MB/s) With samba (from samba share on Freebsd box to Windows 2003 box) 167604556 bytes sent in 35.06 seconds (4.56 MB/s) this is something of a disparity!. Anyone got any ideas Some other info sysctl :- netsmb_dev: loaded net.local.stream.sendspace: 8192 net.local.stream.recvspace: 8192 net.local.dgram.maxdgram: 2048 net.local.dgram.recvspace: 4096 net.local.inflight: 0 net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 net.inet.ip.forwarding: 1 net.inet.ip.redirect: 1 net.inet.ip.ttl: 64 net.inet.ip.rtexpire: 1066 net.inet.ip.rtminexpire: 10 net.inet.ip.rtmaxcache: 128 net.inet.ip.sourceroute: 0 net.inet.ip.intr_queue_maxlen: 50 net.inet.ip.intr_queue_drops: 20 net.inet.ip.accept_sourceroute: 0 net.inet.ip.fastforwarding: 0 net.inet.ip.keepfaith: 0 net.inet.ip.subnets_are_local: 0 net.inet.ip.fw.enable: 1 net.inet.ip.fw.autoinc_step: 100 net.inet.ip.fw.one_pass: 1 net.inet.ip.fw.debug: 1 net.inet.ip.fw.verbose: 1 net.inet.ip.fw.verbose_limit: 0 net.inet.ip.fw.dyn_buckets: 256 net.inet.ip.fw.curr_dyn_buckets: 256 net.inet.ip.fw.dyn_count: 241 net.inet.ip.fw.dyn_max: 4096 net.inet.ip.fw.static_count: 59 net.inet.ip.fw.dyn_ack_lifetime: 300 net.inet.ip.fw.dyn_syn_lifetime: 20 net.inet.ip.fw.dyn_fin_lifetime: 1 net.inet.ip.fw.dyn_rst_lifetime: 1 net.inet.ip.fw.dyn_udp_lifetime: 10 net.inet.ip.fw.dyn_short_lifetime: 5 net.inet.ip.fw.dyn_keepalive: 1 net.inet.ip.maxfragpackets: 143 net.inet.ip.maxfragsperpacket: 16 net.inet.ip.sendsourcequench: 0 net.inet.ip.check_interface: 0 net.inet.icmp.maskrepl: 0 net.inet.icmp.icmplim: 200 net.inet.icmp.drop_redirect: 1 net.inet.icmp.log_redirect: 1 net.inet.icmp.icmplim_output: 1 net.inet.icmp.bmcastecho: 0 net.inet.tcp.rfc1323: 1 net.inet.tcp.rfc1644: 0 net.inet.tcp.mssdflt: 512 net.inet.tcp.keepidle: 720 net.inet.tcp.keepintvl: 75000 net.inet.tcp.sendspace: 32768 net.inet.tcp.recvspace: 57344 net.inet.tcp.keepinit: 75000 net.inet.tcp.delacktime: 100 net.inet.tcp.log_in_vain: 0 net.inet.tcp.blackhole: 2 net.inet.tcp.delayed_ack: 1 net.inet.tcp.path_mtu_discovery: 1 net.inet.tcp.slowstart_flightsize: 1 net.inet.tcp.local_slowstart_flightsize: 4 net.inet.tcp.newreno: 1 net.inet.tcp.tcbhashsize: 512 net.inet.tcp.do_tcpdrain: 1 net.inet.tcp.pcbcount: 50 net.inet.tcp.icmp_may_rst: 1 net.inet.tcp.isn_reseed_interval: 0 net.inet.tcp.inflight_enable: 0 net.inet.tcp.inflight_debug: 0 net.inet.tcp.inflight_min: 6144 net.inet.tcp.inflight_max: 1073725440 net.inet.tcp.inflight_stab: 20 net.inet.tcp.syncookies: 1 net.inet.tcp.syncache.bucketlimit: 30 net.inet.tcp.syncache.cachelimit: 15359 net.inet.tcp.syncache.count: 0 net.inet.tcp.syncache.hashsize: 512 net.inet.tcp.syncache.rexmtlimit: 3 net.inet.tcp.msl: 3 net.inet.tcp.rexmit_min: 1000 net.inet.tcp.rexmit_slop: 200 net.inet.tcp.always_keepalive: 1 net.inet.udp.checksum: 1 net.inet.udp.maxdgram: 9216 net.inet.udp.recvspace: 41600 net.inet.udp.log_in_vain: 0 net.inet.udp.blackhole: 1 net.inet.accf.unloadable: 0 net.inet.raw.maxdgram: 8192 net.inet.raw.recvspace: 8192 net.link.generic.system.ifcount: 3 net.link.ether.inet.prune_intvl: 300 net.link.ether.inet.max_age: 1200 net.link.ether.inet.host_down_time: 20 net.link.ether.inet.maxtries: 5 net.link.ether.inet.useloopback: 1 net.link.ether.inet.proxyall: 0 net.link.ether.inet.log_arp_wrong_iface: 1 net.link.ether.inet.log_arp_movements: 1 net.link.ether.ipfw: 0 net.smb.version: 103006 net.smb.tcpsndbuf: 65535 net.smb.tcprcvbuf: 65535 netsmb_dev: loaded A little trace trace looks something like this :- Frame 229 (125 bytes on wire, 125 bytes captured) Ethernet II, Src: 00:60:08:d0:62:2d, Dst: 00:10:4b:b6:f1:7b Internet Protocol, Src Addr: 192.168.0.1 (192.168.0.1), Dst Addr: 192.168.0.4 (192.168.0.4) Transmission Control Protocol, Src Port: 2857 (2857), Dst Port: netbios-ssn (139), Seq: 1126518730, Ack: 2575214210, Len: 59
mount_smbfs
Greetings: I am trying to use mount_smb to mount a share on a windows machine on my local area network. The problem is I think I need to authenticate with a domain controller to do so. I have tried a couple of things, but i have had no success. Here is what i have tried so far. Any thoughts? mount_smbfs -I ip address of the machine that has the share //username@net bios name/share name /mnt for username I have tried: the domain/username and just the username bare. I get the same results. Thanks, Brian _ Check out the great features of the new MSN 9 Dial-up, with the MSN Dial-up Accelerator. http://click.atdmt.com/AVE/go/onm00200361ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs
Brian H wrote: Greetings: I am trying to use mount_smb to mount a share on a windows machine on my local area network. The problem is I think I need to authenticate with a domain controller to do so. I have tried a couple of things, but i have had no success. Here is what i have tried so far. Any thoughts? mount_smbfs -I ip address of the machine that has the share //username@net bios name/share name /mnt for username I have tried: the domain/username and just the username bare. I get the same results. Thanks, Brian I had the same problem. Using the -W domain name option and a bare user name solved it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs problems
Hi, I'm running 4.8-RELEASE on a box that, daily, connects to a windows machine and writes files to a share. This system was working for about a month. But now, every time I issue the mount_smbfs command I get mount_smbfs: unable to open connection: syserr = RPC struct is bad In /var/log/messages I see... /kernel: smb_maperror: Unmapped error 2:2242 Absolutely nothing has changed on either the FreeBSD box or the Windows 2000 server. In fact, neither box had even been rebooted until the discovery of this problem. Subsequently, each box was bounced once, but to no avail. I've googled on both phrases but have found nothing. Can anyone shed light on this or, perhaps, point me in the right direction? -- Regards, Doug -- Regards, Doug ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs problems
Maybe your Google is broken. =) The string mount_smbfs: unable to open connection: syserr = RPC struct is bad returned ten or so relevant results including... http://www.mail-archive.com/[EMAIL PROTECTED]/msg41941.html Looks as though the Windoze user that you are connecting with has a password that is about to expire. Depending on your security policy, maybe consider checking Password never expires for that user. Hope this helps... Chris Doug Poland wrote: Hi, I'm running 4.8-RELEASE on a box that, daily, connects to a windows machine and writes files to a share. This system was working for about a month. But now, every time I issue the mount_smbfs command I get mount_smbfs: unable to open connection: syserr = RPC struct is bad In /var/log/messages I see... /kernel: smb_maperror: Unmapped error 2:2242 Absolutely nothing has changed on either the FreeBSD box or the Windows 2000 server. In fact, neither box had even been rebooted until the discovery of this problem. Subsequently, each box was bounced once, but to no avail. I've googled on both phrases but have found nothing. Can anyone shed light on this or, perhaps, point me in the right direction? -- Christopher Hollow - Technical Consultant Infrastructure Technology Support Toronto, ON ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs: RPC struct is bad
Hi folks, I'm using SMBFS on FreeBSD 4.9-PRERELEASE from 2003-09-18, and running into problems mounting W2K shares. I was last able to mount these shares a month ago. Since then, the only change I'm aware of was the world update (to catch security patches) and accompanying mergemaster. Here's the config: /etc/fstab: //[EMAIL PROTECTED]/backup /smb/foo smbfs noauto,ro,-N 0 0 /etc/nsmb.conf [default] workgroup=BAR [FOO:BACKUP:BACKUP] password=xyzzy Here's the problem: # mount /smb/foo smbfs: unable to open connection: syserr = RPC struct is bad Any ideas? Google, Rambler and a search of the freebsd-questions archive both came up empty-handed. Ciao, Sheldon. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs: RPC struct is bad
On (2003/10/30 11:37), Sheldon Hearn wrote: I'm using SMBFS on FreeBSD 4.9-PRERELEASE from 2003-09-18, and running into problems mounting W2K shares. I was last able to mount these shares a month ago. Since then, the only change I'm aware of was the world update (to catch security patches) and accompanying mergemaster. I've just tried with FreeBSD 4.9-STABLE, using today's sources and I still get: # mount /smb/foo smbfs: unable to open connection: syserr = RPC struct is bad Backups are suffering. Any ideas (even shots in the dark) would be helpful. Thanks, Sheldon. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs: RPC struct is bad
On (2003/10/30 18:16), Sheldon Hearn wrote: I'm using SMBFS on FreeBSD 4.9-PRERELEASE from 2003-09-18, and running into problems mounting W2K shares. I was last able to mount these shares a month ago. Since then, the only change I'm aware of was the world update (to catch security patches) and accompanying mergemaster. I've just tried with FreeBSD 4.9-STABLE, using today's sources and I still get: # mount /smb/foo smbfs: unable to open connection: syserr = RPC struct is bad Backups are suffering. Any ideas (even shots in the dark) would be helpful. Found the problem. The Windows user backup, as which the FreeBSD box authenticates when mounting the Windows shares, was created on the domain controller without Password never expires enabled, and the business concerned doesn't have a password recycling policy designed to handle automatic password expiry of system accounts. SMBFS expects one of several responses to the authentication phase, but your password has expired, please change it isn't one of them. I'll send my findings to Boris, the author of our SMBFS support. At least this is in the archives, now. :-) Ciao, Sheldon. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Rebuild broke mount_smbfs
Hi all Since rebuilding a FreeBSD system recently because of the OpenSSH and Sendmail issues, I've landed in a world of pain with mount_smbfs. The system is now running 4.9-PRERELEASE, and mount_smbfs will mount shares from Windows machines on the network without a problem, but it will no longer mount shares from two Debian linux servers running Samba (one 2.2.3a-12 and one 2.2.3a-6). When I try to mount a share from the two Debian servers, after a few seconds it times out: su-2.05b# mount_smbfs //[EMAIL PROTECTED]/public /mnt/public Password: mount_smbfs: unable to open connection: syserr = Operation timed out It's not an authentication problem, if I use the wrong password, it fails immediately with syserr = Authentication error. I've tried a longer timeout using -T, and manually specifying the workgroup with -W, neither of which have any effect. I can browse the affected shares using smbclient without a problem, but there is a lengthy delay after putting in the password before the connection succeeds. I know that the Samba versions on the Debian servers are somewhat old, but upgrading them is going to take a lot of doing, and I'm unsure whether it will have any effect. If anyone has some words of wisdom I'd greatly appreciate them. Thanks Dale ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs and lowercase
I was mount smb file system with mount_smbfs -c l, but file and folder names are don't convert to lowercase, whats wrong? I was build kernel with options: options NETSMB options NETSMBCRYPTO options LIBMCHAIN options LIBICONV options SMBFS And I was install pakage libiconv-1.8_2 I was mount smbfs: #mount_smbfs -I server.mydomain -E koi8-r:cp866 -c l //[EMAIL PROTECTED]/fold ~/smbfs -- Best regards, anton mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_smbfs and lowercase
On Fri, Sep 12, 2003 at 01:47:02PM +0700, anton wrote: I was mount smb file system with mount_smbfs -c l, but file and folder names are don't convert to lowercase, whats wrong? One thing that's wrong here is that you're asking the same question over and over again every few hours. Don't do that: if someone knows the answer they'll respond. Kris pgp0.pgp Description: PGP signature
putting mount_smbfs -N into /etc/fstab
Hi, I have: //pref/pref /pref smbfs rw,noauto 0 0 in my /etc/fstab and it works, but I have to press the return key to submit the empty password when I mount /pref and thus I have to use the noauto option. I there a way to put the mount_smbfs option -N and also -E koi8-r:cp866 into the /etc/fstab so that no user interaction is required during the boot process? I couldn't find the answer in man mount_smbfs nor in /usr/src/contrib/smbfs/mount_smbfs/* yet. Thanks Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: putting mount_smbfs -N into /etc/fstab
Alexander Farber said: Hi, I have: //pref/pref /pref smbfs rw,noauto 0 0 in my /etc/fstab and it works, but I have to press the return key to submit the empty password when I mount /pref and thus I have to use the noauto option. I there a way to put the mount_smbfs option -N and also -E koi8-r:cp866 into the /etc/fstab so that no user interaction is required during the boot process? I couldn't find the answer in man mount_smbfs nor in /usr/src/contrib/smbfs/mount_smbfs/* yet. This can be solved with the smbfs config file. Please see /usr/src/contrib/smbfs/examples/dot.nsmbrc Petersen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
tip on using mount_smbfs with the nsmb.conf config file
Hi All, After spending 1-2 fruitless hours trying to track down why I couldn't automate my script to log into the local W2K server, I found that the mount_smbfs man file is incorrect. At least with FreeBSD 4.7 anyway. Maybe it just needs updating. The default global location for the nsmb.conf file should be the /etc directory, not the /usr/local/etc directory, as stated in the man file, and a few web pages I googled. ~.nsmbrc worked ok. One for the archives. Cheers, Paul Hamilton ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_smbfs password file
Hello- i log into samba share alot in bsd so i put some entries in my fstab to automate the process a little. is there a password file i can store my smb share password in so fstab can find and and not prompt me for it each time? thanks, b To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mount_smbfs password file
On Tue, Feb 18, 2003 at 10:49:16AM -0600, Brian Henning wrote: From: Brian Henning [EMAIL PROTECTED] To: freebsd [EMAIL PROTECTED] Subject: mount_smbfs password file Date: Tue, 18 Feb 2003 10:49:16 -0600 Hello- i log into samba share alot in bsd so i put some entries in my fstab to automate the process a little. is there a password file i can store my smb share password in so fstab can find and and not prompt me for it each time? Edit /etc/nsmb.conf file. Look in mount_smbfs man page for more details. thanks, b To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Regards, Dancho Penev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mount_smbfs password file
On Tue, Feb 18, 2003 at 10:49:16AM -0600, Brian Henning wrote: is there a password file i can store my smb share password in so fstab can find and and not prompt me for it each time? man mount_smbfs and note the Files section. It points you to an example. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
mount_smbfs sending parameters incorrectly?
I have 2 machines running freebsd-4.7, one of which is a samba server. I am trying to mount a directory on the other machine (my desktop) from the samba server using mount_smbfs, but that doesn't work. I looked at the log files and it seemed that the parameters were being sent incorrectly: [2003/01/05 06:36:03, 3] smbd/reply.c:reply_sesssetup_and_X(858) Domain=[] NativeOS=[AIRYK] NativeLanMan=[7521] [2003/01/05 06:36:03, 3] smbd/reply.c:reply_sesssetup_and_X(868) sesssetupX:name=[] [2003/01/05 06:36:03, 3] smbd/process.c:process_smb(878) Transaction 3 of length 90 [2003/01/05 06:36:03, 3] smbd/process.c:switch_message(685) switch message SMBtconX (pid 75638) it would appear that my username (airyk) is being sent as the NativeOS, and my domain (7521) is being sent as the NativeLanMan parameter. Erik To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
mount_smbfs problems
hello, i am using samba 2.2.4 on freebsd 4.6.2 release. is it possible to mount smb shares using mount_smbfs with a non-root account? or do i have to use sudo? when i try to mount an smb share off my windows xp box onto my freebsd box, i get the following: ~$ mount_smbfs //neelix/mike /mnt/mike Warning: no cfg file(s) found. mount_smbfs: can not setup kernel iconv table (default:tolower): syserr = Operation not permitted however, when i run the same command as root, it works as expected. furthermore, smbclient works under a unpriviledged account. there were no messages outputted to my log files. i've been google'ing for hours, as well as poring through man pages and documentation, and the samba list archive. i would very much appreciate your help. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
mount_smbfs broken?
Hello, I'm trying to use mount_smbfs -N to get it to read the password from /root/.nsmbrc: # A simple configuration example: # First, define a workgroup. [default] workgroup=datasvr # The 'FSERVER' is an NT server. [datasvr] addr=IP [datasvr:mailbackup:mail_backup] # use persistent password cache for user 'mailbackup' password=$$xxx workgroup=datasvr Whereas datasvr is the netbios name of the W2K server, mailbackup the username and mail_backup the share in question (just don't ask why I need to backup my secure mail server on a 2K box) and the password was made with smbutil crypt. Upon invocation of #mount_smbfs -N -I IP //mailbackup@datasvr/mail_backup /mnt I end up with mount_smbfs: unable to open connection: syserr = Authentication error If I use mount_smbfs -I IP //mailbackup@datasvr/mail_backup /mnt I get prompted for a password and it will work perfectly. However, that's not an option to me as I need to mount the share at boottime. A grep through mount_smbfs.c didn't even find a N option although there might be some case insentivity trickery going on I didn't take into account. So my question boils down to: how can I get mount_smbfs to read the PW from the file? And why doesn't mount_smbfs fail if it is invoked with the -N argument but is unable to read the .nsmbrc file? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mount_smbfs broken?
Hello Gabriel, Saturday, November 02, 2002, 12:20:59 PM, you wrote: GA Whereas datasvr is the netbios name of the W2K server, mailbackup the GA username and mail_backup the share in question (just don't ask why I need GA to backup my secure mail server on a 2K box) and the password was GA made with smbutil crypt. Upon invocation of GA #mount_smbfs -N -I IP //mailbackup@datasvr/mail_backup /mnt GA I end up with GA mount_smbfs: unable to open connection: syserr = Authentication error Try to register your users in the /etc/samba/smbpasswd You can add them using /usr/local/samba/bin/smbpasswd 'man smbpasswd' Anton ps May be you have another displacement of samba. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mount_smbfs: can't get handle to requester (no /dev/nsmb* device)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Markku, Wednesday, October 16, 2002, 11:00:57 PM, you wrote: MK libra# smbutil login //maxi@samba MK Password: MK smbutil: can't get handle to requester (no /dev/nsmb* device) MK smbutil: can't get handle to requester (no /dev/nsmb* device) MK smbutil: could not login to server SAMBA: syserr = Invalid argument MK libra# MK I have checked /dev and there is one entry for nsmb0: MK libra# ll /dev/nsmb* MK crw--- 1 root wheel 144, 0 Oct 14 15:23 /dev/nsmb0 MK libra# MK I don't think the problem is server related because it MK works on another Windows workstation on the same LAN. MK Any ideas on what this might be? In order to use mount_smbfs you should include the following options in your kernel config file: options SMBFS options LIBMCHAIN options LIBICONV options NETSMB options NETSMBCRYPTO So try to recompile your kernel with these options. Also run /dev/MAKEDEV all. - -- Best regards, Artemmailto:aokounev;yahoo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (MingW32) iD8DBQE9rrAFbOuJ0KL1C+MRAm30AJ9aFMLgou2YMnnavOzt4ZoFePXRhgCglU13 lrDnA0STH3JQyWEdfV77hjc= =yDke -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
sudo and mount_smbfs authentication problem
I am setting up some scripts which need to mount an unmount SMB shares. I want to do this as an unprivileged user. I have installed sudo, and am operating it manually to ascertain the manner in which I will incor- porate it into my scripts. As root, I have no problem with: /root# mkdir mnt /root# mount_smbfs //photocd@pdx-james/pub mnt Password: /root# ls mnt and sure enough, /root/mnt has the share mounted. Clearly I know and can accurately type the password for login photocd. But as an ordinary user (actually, a wheel user, and I [think I] have sudo set up to allow wheel users to do anything), I get: First without sudo, to see what error I get if sudo isn't doing it's thing: /usr/home/joeblow mount_smbfs //photocd@pdx-james/pub mnt Warning: no cfg file(s) found. mount_smbfs: can not setup kernel iconv table (default:tolower): syserr = Operation not permitted Using sudo, I get: /usr/home/joeblow sudo mount_smbfs //photocd@pdx-james/pub mnt Password: Password: mount_smbfs: unable to open connection: syserr = Authentication error Here is the meat of my sudoers file: # User privilege specification rootALL=(ALL) ALL # Uncomment to allow people in group wheel to run all commands %wheel ALL=(ALL) ALL What is preventing joeblow from using mount_smbfs? The photocd login is authenticated by a Windows NT 4.0 Server domain, if that is relevant. Thanks in advance! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: sudo and mount_smbfs authentication problem
/usr/home/joeblow sudo mount_smbfs //photocd@pdx-james/pub mnt Password: Password: mount_smbfs: unable to open connection: syserr = Authentication error Here is the meat of my sudoers file: # User privilege specification rootALL=(ALL) ALL # Uncomment to allow people in group wheel to run all commands %wheel ALL=(ALL) ALL What is preventing joeblow from using mount_smbfs? You need to enter the sudo password first, and the password to mount the share second. Alternatively, you could edit the sudo config file to allow wheel users to do that command with no password. I think it would look something like this: # Let wheel users mount_smbfs whatever they want without their password %wheel ALL=(ALL) NOPASSWD: /sbin/mount_smbfs -Will To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
