I have a problem. When I mount my CD (witch is on WIN97 machine) using smbmount I do not see all files in all dirs. If dir have more then, let say, 100 files (it is not the same every time), I do not see all files. This is a problem because on my Linux box I do not have CD-ROM, so if I have to install some packages I first have to copy rpm files on disk, and then install them witch is annoying. What is the problem here. I am not posting smb.conf because I think that problem is not there, but in win settings. Thanks for your help. ??????????????????????????????????????????????????????????????? Regards to You all from Igor Colovic Europe, Yugoslavia, Belgrade cigor@EUnet.yu DeplhiPro@yahoo.com http://members.tripod.com/~Colovic_Igor/index.html ICQ# 16921517
*- Igor Colovic wrote about "Problems with smbmount" | I have a problem. When I mount my CD (witch is on WIN97 machine) using | smbmount I do not see all files in all dirs. If dir have more then, let say, | 100 files (it is not the same every time), I do not see all files. | | This is a problem because on my Linux box I do not have CD-ROM, so if I have | to install some packages I first have to copy rpm files on disk, and then | install them witch is annoying. What is the problem here. | | I am not posting smb.conf because I think that problem is not there, but in | win settings. | Apply this patch to the linux kernel source .../fs/smbfs/proc.c. I patched 2.0.34 with it, I don't know about .35 or any of the .1.X kernels though. I forget who passed this on to me but it fixed those problems for me. -- Brian --------------------------------------------------------------------- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." - unknown Mechanical Engineering servis@purdue.edu Purdue University http://www.ecn.purdue.edu/~servis --------------------------------------------------------------------- -------------- next part -------------- diff -u --recursive --new-file linux-2.0.33.orig/fs/smbfs/proc.c linux-2.0.33/fs/smbfs/proc.c --- linux-2.0.33.orig/fs/smbfs/proc.c Thu Apr 30 18:23:30 1998 +++ linux-2.0.33/fs/smbfs/proc.c Thu Apr 30 18:24:59 1998 @@ -1217,15 +1217,15 @@ WSET(param, 10, 8 + 4 + 2); /* resume required + close on end + continue */ + } #ifdef CONFIG_SMB_WIN95 - /* Windows 95 is not able to deliver answers - to FIND_NEXT fast enough, so sleep 0.2 seconds */ - current->timeout = jiffies + HZ / 5; - current->state = TASK_INTERRUPTIBLE; - schedule(); - current->timeout = 0; + /* Windows 95 is not able to deliver answers + to FIND_NEXT fast enough, so sleep 0.2 seconds */ + current->timeout = jiffies + HZ / 5; + current->state = TASK_INTERRUPTIBLE; + schedule(); + current->timeout = 0; #endif - } result = smb_trans2_request(server, command, 0, NULL, 12 + mask_len + 2, param,
Good Morning (well it is here...) I'm having problems using smbmount to mount a Win95 share to the server.>From Win95 I can browse the network, map available shares on the server,copy files to the server....... in other words everything works as advertised. When I try: #smbmount //name/dir temp -Uusername -Ppass -I192.168.1.25 -c client I get the following:mount failed. Operation not supported on this device I've tried Upper/Lower case and a number of other options, but all fail with the same message If I use smbclient I can see all available shares on the client machine, but I cannot mount them!!!! arrgghhh....... Server is running RH5.0 with Samba 1.9.17.p???? Any ideas folks?? Graham ------------------------------------------------------- Graham K Dodd Network Systems Analyst DSN: 480-5670 / 5233 Fax : 480-2332 Email: Graham.Dodd@ramstein.af.mil -------------------------------------------------------
Hi folks;
This is my situation:
I'm running RH 5.1 and samba 1.9p10 to serve an intranet of mixed
Win95 OSR2 & DOS 6.22. I have some scripts on the server side that mounts
Win95 shares through smbmount.
Everything was OK up to here.
But I had to upgrade to kernel version 2.1.135 (long story) and
problems begun:
After the kernel upgrade the scripts begun to fail, exiting with
an error of "SMBFS need mount version 6". I also got this error when
using
smbclient.
To solve this, I compiled and installed samba 2.0.0 prealpha, and
the error changed:
Everything works fine when using the shared resources on the
server from my W95 & DOS boxes. Smbclient also works fine to mount W95
shares, but the error with smbmount persists and is different now. This is
where I need your help:
Everytime I try to mount a Win95 share with smbmount, I get a "BAD
user/passwd" error, and cannot mount the resource. But I have no problems
when the resource has no password.
When using the debug option, I get the message "using encrypted
password" (I think this is the error), even when I have set "encrypted
password = no" in the smb.conf file.
I don't know what to do or where the error should be, and the most
extrange thing is that the problem is unidirectional, from my Linux box to
the Win95 side, and only when using smbmount.
If you can give me any clue, I would be grateful.
Thanks in advance
Javier
/* ------------------------------------------------------------------------ */
Javier E. B?rtoli | Fac. de Ingenier?a Qu?mica
| Universidad Nacional del Litoral
jbertoli@fiqus.unl.edu.ar | Santa Fe - Argentina
/* ------------------------------------------------------------------------ */
"Life is what happens to you when you're busy making other
plans"
(J. Lennon)
Hello all, I run a Debian system and have recently began having problems with smbmount. I have updated to the latest version only to find that I can't use smbmount at all. The problem: $ smbmount //10.0.0.1/Write mnt timeout connecting to 10.0.0.1:445 1942: session request to 10.0.0.1 failed (SUCCESS - 0) timeout connecting to 10.0.0.1:445 1942: session request to 10 failed (SUCCESS - 0) timeout connecting to 10.0.0.1:445 1942: session request to *SMBSERVER failed (SUCCESS - 0) SMB connection failed Questions: Why is samba trying to connect to port 445 on the server (this is blocked by the firewall, but until now has never been a problem. Does anyone have any ideas? Am I even posting in the right place, or should I send bug-reports to Debian? Thanks in advance, .George Borisov.