Hi All, I run a Linux box with caldera Openlinux 2.3, 2.2.17 kernel (SMP), and I have a very serious problem getting samba to work properly (despite the fact I have it working just fine on a plain pent-133, and on that machine it shows up in network neighborhood, and I can double click on it, drag and drop files, etc). However, we are in the process of converting our application from NT to linux, but I MUST have access to a NT Server share to make this work (as it reads data from it), but when I have used smbmount with a destination IP, it will let me mount the drive, BUT, after a while, I get a smbfs-retry (error: -3) code, and I lose communication with the NT Share, and when I try to shutdown the system i will either get hung up during the process, or a kernel panic happens. I would like to be able to prove the ability of linux to run large scale applications, but if I can't solve this problem, I will be forced to continue running on windows. Does ANYONE on here have an idea as to how I can get this 2nd box to show up in network neighborhood, and more importantly maintain communications with the NT Server Share (which is VERY important)... Please help if you can... -Bill Parker
Bill Parker wrote:> > Hi All, > > I run a Linux box with caldera Openlinux 2.3, 2.2.17 kernel (SMP), > and I have a very serious problem getting samba to work properly (despite > the fact I have it working just fine on a plain pent-133, and on that > machine it shows up in network neighborhood, and I can double click on > it, drag and drop files, etc). > > However, we are in the process of converting our application from > NT to linux, but I MUST have access to a NT Server share to make this > work (as it reads data from it), but when I have used smbmount with a > destination IP, it will let me mount the drive, BUT, after a while, I > get a smbfs-retry (error: -3) code, and I lose communication with theWhy are you using an IP address? If everything is setup correctly you shouldn't need it with the 2.2.xx kernel smbmount tools. In this case, linux is just acting as a proxy for NT, this isn't really showing linux standing on it's own. If that is what you want, you should have a test computer setup with the files on the hard drive of the linux computer. Is this the only thing that the NT server is doing, serving these files? If so, you can have the linux computer take over the computer name of the NT server, and shut down the NT comp. You can even have it use a guest user while you are creating users on linux and setting their groups. Did you know that with smbmount, you are acting as ONE user from NT Server's perspective? Whatever user you choose should be able to access all of the files with whatever the highest privilege ANY user will need from linux. You will then have to make the same restrictions on linux, which will now be much harder now that you are acting as one user/group pair for the smbmounted drive. If you are forced to specify an ip address, I suspect something is wrong. HTH
On Thu, 16 Nov 2000, Bill Parker wrote:> However, we are in the process of converting our application from > NT to linux, but I MUST have access to a NT Server share to make this > work (as it reads data from it), but when I have used smbmount with a > destination IP, it will let me mount the drive, BUT, after a while, I > get a smbfs-retry (error: -3) code, and I lose communication with the > NT Share, and when I try to shutdown the system i will either get hung > up during the process, or a kernel panic happens.You normally don't get the "-3" error on it's own, what are the messages before that? I suspect that you are suffering from the "smb_retry: caught signal" bug. There is a workaround for that in 2.2.18-pre21. (http://www.hojdpunkten.ac.se/054/samba/pre-patches.html) The system getting hung up is known (if you unplug the network and access the smbfs mount your process will wait forever for responses to its query), kernel panics are not. If you can capture the oops and run that through ksymoops it might tell something.> an idea as to how I can get this 2nd box to show up in network > neighborhood, and more importantly maintain communications with the > NT Server Share (which is VERY important)...I'm guessing the browsing problem is either a smb.conf problem (double check vs your working box?) or simply that nmbd isn't running. /Urban
Bill Parker wrote:> > At 06:37 PM 11/16/2000 -0800, you wrote: > >Bill Parker wrote: > >> > >> Hi All, > >> > >> I run a Linux box with caldera Openlinux 2.3, 2.2.17 kernel (SMP), > >> and I have a very serious problem getting samba to work properly (despite > >> the fact I have it working just fine on a plain pent-133, and on that > >> machine it shows up in network neighborhood, and I can double click on > >> it, drag and drop files, etc). > >> > >> However, we are in the process of converting our application from > >> NT to linux, but I MUST have access to a NT Server share to make this > >> work (as it reads data from it), but when I have used smbmount with a > >> destination IP, it will let me mount the drive, BUT, after a while, I > >> get a smbfs-retry (error: -3) code, and I lose communication with the > > > >Why are you using an IP address? If everything is setup correctly you > shouldn't need it with the 2.2.xx kernel smbmount tools. > > Welp, that is the $64 question I have been racking MY brains over for > almost a week. The first machine I set up on Samba worked just fine, > and despite the success I had there, when I try to get a 2nd machine > working with Samba, it just DOES not want to work. The smb.conf files > on the two linux boxes are the same (minus obvious IP address differences) > but the ONLY difference on the 2nd box is that it is NOT plugged into > the same switch that the OTHER three linux boxes are, but it does have > an IP in the same class C as the other boxes. > > Example: > > Box 1 (nermal) xxx.yyy.zzz.25 (plugged into switch which sees router) > Box 2 (odie) xxx.yyy.zzz.11 (same switch) > Box 3 (pooky) xxx.yyy.zzz.55 (same switch) > Box 4 (html) xxx.yyy.zzz.15 (switch in other part of building > but using ip of router for internet access) > > Does BOX 4 need to be plugged into the same switch to make this > work, or have I lost all my marbles? :) > > btw, all of the box machines are capable of IP masq, if that makes > a difference... > > -BillYes, the router makes a difference. Network neighborhood is based on broadcasts, and the router won't propagate them unless you configure it to do so. You can run a WINS server instead, which is what I suggest.