(no subject)
in [Samba]
|
From: Stan Hoeppner on 3 Feb 2010 00:10 James Hurlburt put forth on 2/2/2010 4:56 PM: > NET805: NETWORK DEVICE NO LONGER EXISTS READING DRIVE U > > Abort, Retry, Fail? Hi James, You didn't happen to put the new Samba server on a different IP subnet or VLAN than the old server did you? You didn't show the IP's and subnet masks of each machine. IIRC, NETBIOS can have problems crossing some routers and VLANs, possibly other network boundaries. If you aren't already, the first thing I'd do is get the new server on an IP address consecutive to the old server and make sure they're jacked into the same switch. This should eliminate any possible network topology issues causing problems. Is the new server a virtual machine? Make sure the hypervisor is allowing NETBIOS traffic to flow from the physical NIC to/from the VM. Actually, I should say, make sure it isn't disallowing such traffic. This is unlikely, but it's best to check. Running in a VM can often cause goofy hard to solve problems because of things not working at low levels the way we expect them to. Lastly, disable any iptables rules on the new server or other firewall scripting software, and disable SELinux if it is enabled. Look at netstat -an on both servers when connecting with the clients, and make sure all the same ports are being used. That's about all I can think of at this point. As Gunter mentioned, a network trace couldn't hurt. I'd probably try a few of the less time consuming recommendations above before resorting to the trace. -- Stan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: kornel kornatka on 6 Feb 2010 06:10 2010/2/6 Greg Byshenk <samba(a)byshenk.net> > On Sat, Feb 06, 2010 at 11:31:31AM +0100, kornel kornatka wrote: > > > I Have a problem: > > > > I'm sharing ~600 folders on my samba server: > > > > [SHARE 192.168.0.20] > > comment = Private share for host 192.168.0.20 > > browseable = yes > > writable = yes > > path = /var/archives/USERS/192.168.0.20 > > public=yes > > hosts deny = 192.168. EXCEPT 192.168.0.20 > > > > [SHARE 192.168.0.21] > > comment = Private share for host 192.168.0.21 > > browseable = yes > > writable = yes > > path = /var/archives/USERS/192.168.0.21 > > public=yes > > hosts deny = 192.168. EXCEPT 192.168.0.21 > > . > > . > > . > > > > But any user can see all shares even those without permissions (each host > > can see ~600 shares and only one is working for him) > > I don't know how to hide shares for each host so that he can see only > share > > created for him. > > > > For Example host 192.168.0.10 will see only "SHARE 192.168.0.10" > > > I'm not a samba expert, but what you're doing seems clumsy to me. > > Why not create a single share something like this: > > [privateshare] > comment = Private share for local machines > browseable = yes > writable = yes > path = /var/archives/USERS/%I > public = yes > hosts deny = 192.168. EXCEPT %I > > This allows every host to see just a single folder of its own -- and also > makes for a much simpler smb.conf. > > > -- > greg byshenk - gbyshenk(a)byshenk.net - Leiden, NL > As you can see I'm beginner with samba. I've changed my conf as you said... it's not working But in my understanding ... : Samba can't know possibilities of %I variable to create shares. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Michael Wood on 6 Feb 2010 06:20 On 6 February 2010 13:05, kornel kornatka <ds14.kornel(a)gmail.com> wrote: > 2010/2/6 Greg Byshenk <samba(a)byshenk.net> [...] >> Why not create a single share something like this: >> >> [privateshare] >> comment = Private share for local machines >> browseable = yes >> writable = yes >> path = /var/archives/USERS/%I >> public = yes >> hosts deny = 192.168. EXCEPT %I >> >> This allows every host to see just a single folder of its own -- and also >> makes for a much simpler smb.conf. > > As you can see I'm beginner with samba. > I've changed my conf as you said... it's not working > But in my understanding ... : > Samba can't know possibilities of %I variable to create shares. I agree with Greg. I believe Samba should create the shares on the fly when the user connects, the same way it does for the [homes] share. I have not tried this, though. -- Michael Wood <esiotrot(a)gmail.com> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Greg Byshenk on 6 Feb 2010 06:20 On Sat, Feb 06, 2010 at 11:31:31AM +0100, kornel kornatka wrote: > I Have a problem: > > I'm sharing ~600 folders on my samba server: > > [SHARE 192.168.0.20] > comment = Private share for host 192.168.0.20 > browseable = yes > writable = yes > path = /var/archives/USERS/192.168.0.20 > public=yes > hosts deny = 192.168. EXCEPT 192.168.0.20 > > [SHARE 192.168.0.21] > comment = Private share for host 192.168.0.21 > browseable = yes > writable = yes > path = /var/archives/USERS/192.168.0.21 > public=yes > hosts deny = 192.168. EXCEPT 192.168.0.21 > . > . > . > > But any user can see all shares even those without permissions (each host > can see ~600 shares and only one is working for him) > I don't know how to hide shares for each host so that he can see only share > created for him. > > For Example host 192.168.0.10 will see only "SHARE 192.168.0.10" I'm not a samba expert, but what you're doing seems clumsy to me. Why not create a single share something like this: [privateshare] comment = Private share for local machines browseable = yes writable = yes path = /var/archives/USERS/%I public = yes hosts deny = 192.168. EXCEPT %I This allows every host to see just a single folder of its own -- and also makes for a much simpler smb.conf. -- greg byshenk - gbyshenk(a)byshenk.net - Leiden, NL -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: kornel kornatka on 6 Feb 2010 06:40 2010/2/6 Michael Wood <esiotrot(a)gmail.com> > On 6 February 2010 13:05, kornel kornatka <ds14.kornel(a)gmail.com> wrote: > > 2010/2/6 Greg Byshenk <samba(a)byshenk.net> > [...] > >> Why not create a single share something like this: > >> > >> [privateshare] > >> comment = Private share for local machines > >> browseable = yes > >> writable = yes > >> path = /var/archives/USERS/%I > >> public = yes > >> hosts deny = 192.168. EXCEPT %I > >> > >> This allows every host to see just a single folder of its own -- and > also > >> makes for a much simpler smb.conf. > > > > As you can see I'm beginner with samba. > > I've changed my conf as you said... it's not working > > But in my understanding ... : > > Samba can't know possibilities of %I variable to create shares. > > I agree with Greg. > > I believe Samba should create the shares on the fly when the user > connects, the same way it does for the [homes] share. > > I have not tried this, though. > > -- > Michael Wood <esiotrot(a)gmail.com> > * * I've tested new configuration [privateshare %I] comment = Private share for local machines browseable = yes writable = yes path = /var/archives/USERS/%I public = yes Works preaty good :) obviously - the hosts allow is no need now (thats why it wasn't working earlier) Thank you for your help! :) Regards Kornel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
|
Pages: 1 Prev: [Samba] winbind error? Next: [Samba] permissions on Samba share mount point in RHEL 5 |