similar to: How to add basic security to my samba share?

Hi I am still struggling to setup a home network of: - 2 laptops running Windows 7 Home - 1 laptop running Windows 10 Home - 1 Raspberry Pi ‘RPHS’ running Rasbian Jesse and Samba 4.1.17-Debian The current status is that only one of the Windows machines can see the Samba shared drive /mnt/data. The other machines don’t discover the Pi at all. I’m wondering if there is something wrong with my

Hi Rowland Thanks for your review. I will check all the points you raise, but one I do not understand is: "do all machines have the same dns domain name?" What is the dns domain name in the context of a NetBios workgroup? The only dns I am aware of is the one provided by my ISP, and that won't be relevant I think. Best regards David -----Original Message----- From: Rowland

On 02/01/16 18:10, DavidA wrote: > Hi > > I am still struggling to setup a home network of: > > - 2 laptops running Windows 7 Home > - 1 laptop running Windows 10 Home > - 1 Raspberry Pi ‘RPHS’ running Rasbian Jesse and Samba 4.1.17-Debian > > The current status is that only one of the Windows machines can see the Samba shared drive /mnt/data. The other machines don’t

Hi I have configured a Raspberry Pi (running Raspbian o/s) to act as a Samba server to share files with my home Windows workgroup. One of my Windows 7 laptops can see the share fine, but the other WIndows 7 laptop refuses to see the Pi server at all. I have checked all the obvious things (Workgroup name, password etc) and don't know what else to do. I would welcome any suggestions. In case it

On 18/12/15 19:46, DavidA wrote: > Hi > > I'm still struggling with this problem. Here is my situation: > > I have two Windows 7 laptops, call them A and B, and a Raspberry Pi > Samba server on a home network, all with the same workgroup name. The > Pi's name is RPHS. > > A and B can see each other (their names appear under Network in > Explorer on both

On 13/12/15 09:36, DavidA wrote: > Hi > > Here's some more info about my problem: > > ========================================== > > log.nmbd contains: > > Samba name server RPHS is now a local master browser for workgroup > HOME on subnet 192.168.2.8 > > ***** > [2015/12/12 20:48:19.709456, 0] >

Hi Rowland Thanks for your reply. I see: $ cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters 127.0.1.1 RPHS So I guess I should edit the hosts file and specify RPHS's fixed IP address. I don't think domain name is relevant for a home network so I won't specify one. Will

Hi Rowland >Sorry, but a dns domain is just as relevant for a home network as it is for >a work network, please use one Ok, thanks. I know this is well out of your area, but I wonder where I would specify the dns domain in Windows? David -----Original Message----- From: Rowland penny Sent: Sunday, January 03, 2016 9:23 AM To: samba at lists.samba.org Subject: Re: [Samba] Please review

On 12/12/15 18:37, DavidA wrote: > Hi > > I have configured a Raspberry Pi (running Raspbian o/s) to act as a Samba > server to share files with my home Windows workgroup. One of my Windows 7 > laptops can see the share fine, but the other WIndows 7 laptop refuses to > see the Pi server at all. I have checked all the obvious things > (Workgroup > name, password etc) and

Hi I am still having trouble getting Windows 10 and Windows 7 laptops to communicate with a Samba server (4.1.17-Debian) running on Rasbian Jesse. Running Wireshark on one of the laptops I notice these sequential packet transfers: Laptop –> Pi BJNP Scanner command: discover Pi –> Laptop ICMP 'Destination unreachable (Port unreachable)' This happens even on a laptop

Hi I'm still struggling with this problem. Here is my situation: I have two Windows 7 laptops, call them A and B, and a Raspberry Pi Samba server on a home network, all with the same workgroup name. The Pi's name is RPHS. A and B can see each other (their names appear under Network in Explorer on both laptops). Both A and B can access the Pi if I specify the IP Address in

Hi Rowland > (just a thought, you have given the Samba server a fixed ipaddress, > hostname and domain name, haven't you ?). The Pi has a fixed IP address and hostname. I see: $ cat /etc/hostname RPHS $ cat /etc/resolv.conf # Generated by resolvconf nameserver 208.67.222.123 nameserver 208.67.220.123 So the DNS seems arbitrary. I don't understand what the DNS should be for a

On 02/01/16 20:59, DavidA wrote: > Hi Rowland > >> (just a thought, you have given the Samba server a fixed ipaddress, >> hostname and domain name, haven't you ?). > > The Pi has a fixed IP address and hostname. I see: > > $ cat /etc/hostname > RPHS OK, try running these commands: hostname hostname -s hostname -d hostname -f hostname -i If your rpi has the

Hi Rowland > Possibly a firewall problem, temporarily turn off the firewall on the win7 > laptop that cannot see your rpi, if this works, you know where to look. Thanks for the suggestion. I disabled Kaspersky Internet Security Firewall and Windows Firewall but still can't see the rpi. I can, however, see the other Windows laptops (with firewall on or off). Any other thoughts

# Global parameters [global] server string = Samba file and print server server role = standalone server map to guest = Bad User obey pam restrictions = Yes passwd program = /usr/bin/passwd '%u' passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . passwd chat timeout = 120 username map = /etc/samba/smbusers unix

On Fri, 1 Feb 2019 13:53:26 -0500 <mmcg29440 at frontier.com> wrote: > Just call me Marty. Ham13 is a login name on another system. OK. I'm > posting the smb.conf and thee smbclient responses form both Linux > PC's. One running Mint 19.1 and the other running Mint 18.3. The 18.3 > machine does connect to the network. All I want to do use the file > manager to connect

Hi, I am running Samba 3.0.1 on a Debian/Sid machine. I have installed winbind to access the AD of the local network, which I want to use for UNIX logons. wbinfo -u shows all the users of the AD, but "getent passwd" only shows the contents of the file /etc/passwd. I have been following the instruction for winbind (Chapter 21) in the Samba-HOWTO-Collection. Any comments would be

Hi Here's some more info about my problem: ========================================== log.nmbd contains: Samba name server RPHS is now a local master browser for workgroup HOME on subnet 192.168.2.8 ***** [2015/12/12 20:48:19.709456, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) find_domain_master_name_query_fail: Unable to find the Domain Master

I have a problem with a Member Server on Samba 3.0.28a running on Ubuntu Heady. Both systems were recently upgraded using Ubuntu's automated upgrade. It's also possible I broke a working configuration by accident. The shares on the Member server are visible on the XP clients and some users can authenticate properly. At least one user on one XP desktop cannot. The shares are visible

Le Thu, 8 Oct 2020 18:31:38 +0100 Rowland penny via samba <samba at lists.samba.org> ?crivait: > You do not normally run winbind on standalone server, so I think you > need to post the [global] portion of your old smb.conf, so we can > find out just what you are running. Here is the old one: [global] name resolve order = wins lmhosts host bcast passwd chat =