Nelvalhil
Posts: 6
Joined: Mon Jun 10, 2019 12:47 pm

Can access via \\Raspberrypi, also can see (and use) my shared Samba folder. Can't access via internal IP (wlan0)

Thu Nov 07, 2019 12:45 pm

Hi all,

I've set the IP of my RPI (3B+) to ..1.15 and confirmed that in ifconfig. Now I rebooted the RPI and wanted to access it via windows explorer, except it won't let me. Any ideas?

All help would be greatly appreciated as I am stuck for a couple of days on this now. Thanks again

dustnbone
Posts: 201
Joined: Tue Nov 05, 2019 2:49 am

Re: Can access via \\Raspberrypi, also can see (and use) my shared Samba folder. Can't access via internal IP (wlan0)

Thu Nov 07, 2019 3:26 pm

Can you verify IP connectivity by pinging the Pi from the Windows box?

Have you configured Samba on the Pi to share folders? I don't think it does this by default in Raspbian.

How are you connecting through Windows Explorer? Are you manually entering a //SERVER/share address or trying to browse to it through "Network"?

Have you tried to connect to the Pi from another device like an Android phone?

Also, setting a static IP address on a network that has a running DHCP server can cause address conflicts if the assigned IP is within the range that gets assigned automatically.

If the DHCP server assigns that address before the Pi boots up, the Pi sets itself to it's statically assigned address and now you have 2 devices on the same network with the same IP.

You can set the DHCP server to assign from a narrower range of IPs that doesn't include your static IP.

Nelvalhil
Posts: 6
Joined: Mon Jun 10, 2019 12:47 pm

Re: Can access via \\Raspberrypi, also can see (and use) my shared Samba folder. Can't access via internal IP (wlan0)

Thu Nov 07, 2019 5:18 pm

First of all, I would like to thank you for taking time out of your day to help me. It is hugely appreciated!
dustnbone wrote:
Thu Nov 07, 2019 3:26 pm
Can you verify IP connectivity by pinging the Pi from the Windows box?
I am not sure what you mean with the windows box. I did however check if I could find the Pi IP being used on the service page from my router; it was listed there with the same IP I had set it on.

I did however tried to ping the RPI with both Nmap and a W10 promt command on both a wired and wireless machine.
dustnbone wrote:
Thu Nov 07, 2019 3:26 pm
Have you configured Samba on the Pi to share folders? I don't think it does this by default in Raspbian.
Yes, I can actually use my shared folder fine, 100% with no issue at all. I can also manually type //Raspberrypi @ windows explorer and it sends me straight through. I just cannot get access via typing the assigned IP.
dustnbone wrote:
Thu Nov 07, 2019 3:26 pm
How are you connecting through Windows Explorer? Are you manually entering a //SERVER/share address or trying to browse to it through "Network"?
As I said just above here, I can both access it via //RaspberryPi or browse to it through network, the shared folder is always listed there and available.
dustnbone wrote:
Thu Nov 07, 2019 3:26 pm
Have you tried to connect to the Pi from another device like an Android phone?
Yes, I tried on multiple devices, both android and other windows machines in my network (wired, wireless)
dustnbone wrote:
Thu Nov 07, 2019 3:26 pm
Also, setting a static IP address on a network that has a running DHCP server can cause address conflicts if the assigned IP is within the range that gets assigned automatically.

If the DHCP server assigns that address before the Pi boots up, the Pi sets itself to it's statically assigned address and now you have 2 devices on the same network with the same IP.

You can set the DHCP server to assign from a narrower range of IPs that doesn't include your static IP.
I tried a bunch of different IPs on the Pi, I am quite sure there is not another device also switching IPs.

Strange thing is, when I was setting up the shared Samba folder I could access my Pi via windows explorer just fine. Now it has been a while and I am done with setting up the Samba folder I just cannot access the RPI via IP to save my life.

Thanks again for thinking with me !

hortimech
Posts: 381
Joined: Wed Apr 08, 2015 5:52 pm

Re: Can access via \\Raspberrypi, also can see (and use) my shared Samba folder. Can't access via internal IP (wlan0)

Thu Nov 07, 2019 10:06 pm

I think you should post your smb.conf, you seem to be getting exactly the opposite problem to what people normally get, that is they can connect via IP but not via hostname.

Nelvalhil
Posts: 6
Joined: Mon Jun 10, 2019 12:47 pm

Re: Can access via \\Raspberrypi, also can see (and use) my shared Samba folder. Can't access via internal IP (wlan0)

Thu Nov 07, 2019 10:43 pm

Yeah, I also found it so weird. I'll make sure I post the file tomorrow as I can't right now

Nelvalhil
Posts: 6
Joined: Mon Jun 10, 2019 12:47 pm

Re: Can access via \\Raspberrypi, also can see (and use) my shared Samba folder. Can't access via internal IP (wlan0)

Sun Nov 10, 2019 2:38 pm

  • [global]

    ## Browsing/Identification ###

    # Change this to the workgroup/NT-domain name your Samba server will part of
    workgroup = WORKGROUP

    #### Networking ####

    # The specific set of interfaces / networks to bind to
    # This can be either the interface name or an IP address/netmask;
    # interface names are normally preferred
    ; interfaces = 127.0.0.0/8 eth0

    # Only bind to the named interfaces and/or networks; you must use the
    # 'interfaces' option above to use this.
    # It is recommended that you enable this feature if your Samba machine is
    # not protected by a firewall or is a firewall itself. However, this
    # option cannot handle dynamic or non-broadcast interfaces correctly.
    ; bind interfaces only = yes



    #### Debugging/Accounting ####

    # This tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/log.%m

    # Cap the size of the individual log files (in KiB).
    max log size = 1000

    # We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
    # Append [email protected] if you want important messages to be sent to syslog too.
    logging = file

    # Do something sensible when Samba crashes: mail the admin a backtrace
    panic action = /usr/share/samba/panic-action %d


    ####### Authentication #######

    # Server role. Defines in which mode Samba will operate. Possible
    # values are "standalone server", "member server", "classic primary
    # domain controller", "classic backup domain controller", "active
    # directory domain controller".
    #
    # Most people will want "standalone server" or "member server".
    # Running as "active directory domain controller" will require first
    # running "samba-tool domain provision" to wipe databases and create a
    # new domain.
    server role = standalone server

    obey pam restrictions = yes

    # This boolean parameter controls whether Samba attempts to sync the Unix
    # password with the SMB password when the encrypted SMB password in the
    # passdb is changed.
    unix password sync = yes

    # For Unix password sync to work on a Debian GNU/Linux system, the following
    # parameters must be set (thanks to Ian Kahan <<[email protected]> for
    # sending the correct chat script for the passwd program in Debian Sarge).
    passwd program = /usr/bin/passwd %u
    passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

    # This boolean controls whether PAM will be used for password changes
    # when requested by an SMB client instead of the program listed in
    # 'passwd program'. The default is 'no'.
    pam password change = yes

    # This option controls how unsuccessful authentication attempts are mapped
    # to anonymous connections
    map to guest = bad user

    ########## Domains ###########

    #
    # The following settings only takes effect if 'server role = primary
    # classic domain controller', 'server role = backup domain controller'
    # or 'domain logons' is set
    #

    # It specifies the location of the user's
    # profile directory from the client point of view) The following
    # required a [profiles] share to be setup on the samba server (see
    # below)
    ; logon path = \\%N\profiles\%U
    # Another common choice is storing the profile in the user's home directory
    # (this is Samba's default)
    # logon path = \\%N\%U\profile

    # The following setting only takes effect if 'domain logons' is set
    # It specifies the location of a user's home directory (from the client
    # point of view)
    ; logon drive = H:
    # logon home = \\%N\%U

    # The following setting only takes effect if 'domain logons' is set
    # It specifies the script to run during logon. The script must be stored
    # in the [netlogon] share
    # NOTE: Must be store in 'DOS' file format convention
    ; logon script = logon.cmd

    # This allows Unix users to be created on the domain controller via the SAMR
    # RPC pipe. The example command creates a user account with a disabled Unix
    # password; please adapt to your needs
    ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

    # This allows machine accounts to be created on the domain controller via the
    # SAMR RPC pipe.
    # The following assumes a "machines" group exists on the system
    ; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

    # This allows Unix groups to be created on the domain controller via the SAMR
    # RPC pipe.
    ; add group script = /usr/sbin/addgroup --force-badname %g

    ############ Misc ############

    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting
    ; include = /home/samba/etc/smb.conf.%m

    # Some defaults for winbind (make sure you're not using the ranges
    # for something else.)
    ; idmap config * : backend = tdb
    ; idmap config * : range = 3000-7999
    ; idmap config YOURDOMAINHERE : backend = tdb
    ; idmap config YOURDOMAINHERE : range = 100000-999999
    ; template shell = /bin/bash

    # Setup usershare options to enable non-root users to share folders
    # with the net usershare command.

    # Maximum number of usershare. 0 means that usershare is disabled.
    # usershare max shares = 100

    # Allow users who've been granted usershare privileges to create
    # public shares, not just authenticated ones
    usershare allow guests = yes

    #======================= Share Definitions =======================

    [homes]
    comment = Home Directories
    browseable = no

    # By default, the home directories are exported read-only. Change the
    # next parameter to 'no' if you want to be able to write to them.
    read only = yes

    # File creation mask is set to 0700 for security reasons. If you want to
    # create files with group=rw permissions, set next parameter to 0775.
    create mask = 0700

    # Directory creation mask is set to 0700 for security reasons. If you want to
    # create dirs. with group=rw permissions, set next parameter to 0775.
    directory mask = 0700

    # By default, \\server\username shares can be connected to by anyone
    # with access to the samba server.
    # The following parameter makes sure that only "username" can connect
    # to \\server\username
    # This might need tweaking when using external authentication schemes
    valid users = %S

    # Un-comment the following and create the netlogon directory for Domain Logons
    # (you need to configure Samba to act as a domain controller too.)
    ;[netlogon]
    ; comment = Network Logon Service
    ; path = /home/samba/netlogon
    ; guest ok = yes
    ; read only = yes

    # Un-comment the following and create the profiles directory to store
    # users profiles (see the "logon path" option above)
    # (you need to configure Samba to act as a domain controller too.)
    # The path below should be writable by all users so that their
    # profile directory may be created the first time they log on
    ;[profiles]
    ; comment = Users profiles
    ; path = /home/samba/profiles
    ; guest ok = no
    ; browseable = no
    ; create mask = 0600
    ; directory mask = 0700

    [printers]
    comment = All Printers
    browseable = no
    path = /var/spool/samba
    printable = yes
    guest ok = no
    read only = yes
    create mask = 0700

    # Windows clients look for this share name as a source of downloadable
    # printer drivers
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/printers
    browseable = yes
    read only = yes
    guest ok = no
    # Uncomment to allow remote administration of Windows print drivers.
    # You may need to replace 'lpadmin' with the name of the group your
    # admin users are members of.
    # Please note that you also need to set appropriate Unix permissions
    # to the drivers directory for these users to have write rights in it
    ; write list = root, @lpadmin

    [folder1]
    path = /home/pi/RPiTest
    writeable = Yes
    create mask = 0777
    directory mask = 0777
    public = no
'Folder1' is the shared folder I made, should public be yes?

Return to “Troubleshooting”