Cannot access shares on windows-computers on same network

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
User avatar
SprinterDriver
Level 4
Level 4
Posts: 260
Joined: Sun Jan 25, 2015 3:35 pm
Location: Norway

Cannot access shares on windows-computers on same network

Post by SprinterDriver »

Hi.

My Linux Mint 18.1 Mate is connected to Wifi. In that same network, there is four windows computers (XP and W7).

At first, when running file manager I was not able to see none of the Windows shares.

Therefore I followed a tutorial I found, and managed to install some packages (sorry I cannot remember it now) and also I managed to change the samba config file so that this Mint machine is at the same workgroup as the windows machines.
I beleive it was this forum thread (based on website history):
viewtopic.php?t=223812

In file manager now, under Places --> Network --> Browse network I see the name of the windows computers. But when I attempt to open (double click on their names in file browser), I get this error message:
Unable to mount location
Failed to retrieve share list from server: Connection refused
[ok]
Hope you can help me troubleshoot this.

The contents of smb.conf file

Code: Select all

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

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

# https://forums.linuxmint.com/viewtopic.php?t=223812
# Løser problemet (forhåpentligvis) med fildeling på XP maskiner...
netbios name = mintbox
name resolve order = bcast host lmhosts wins

# server string is the equivalent of the NT Description field
	server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### 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

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# 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 sever" 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

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   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 <<kahan@informatik.tu-muenchen.de> 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 uid = 10000-20000
;   idmap gid = 10000-20000
;   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 (default) 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 =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[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.
# Un-comment the following parameter to make 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

[edit]
I just remembers some things that I assume is important with this issue:
* All the Windows computers can see each other, and browse each others files.
* When I use Ping command from Linux Mint, I get no response when I ping the Windows computers by their names - but I get response when I ping the other computers by IP.
* When I ping from Windows machines on this computers name, it doesn't find it (claims it cant resolve the name). But I haven't set up any shares on this Mint computer - could that explain why?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
So I got this bright idea. But when I tried to grab the light bulb, I did not hurt my hands as expected from a warm bulb, because it turned out to be one of those LED bulbs.
User avatar
coffee412
Level 8
Level 8
Posts: 2263
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: Cannot access shares on windows-computers on same network

Post by coffee412 »

On your mint computer what is the contents of your /etc/hosts file? Can you post that?
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
User avatar
SprinterDriver
Level 4
Level 4
Posts: 260
Joined: Sun Jan 25, 2015 3:35 pm
Location: Norway

content of my hosts file

Post by SprinterDriver »

The contents of hosts file is

Code: Select all

127.0.0.1	localhost
127.0.1.1	thiscomputername

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
So I got this bright idea. But when I tried to grab the light bulb, I did not hurt my hands as expected from a warm bulb, because it turned out to be one of those LED bulbs.
User avatar
coffee412
Level 8
Level 8
Posts: 2263
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: content of my hosts file

Post by coffee412 »

SprinterDriver wrote:The contents of hosts file is

Code: Select all

127.0.0.1	localhost
127.0.1.1	thiscomputername

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Thank you. Normally I use static ips on all my computers in the shop. This makes things much easier to work with them.

Code: Select all

127.0.0.1	localhost
10.0.1.1	dino.athome.net		dino	
10.0.1.61	coffee.athome.net	coffee
10.0.1.62	max.athome.net		max
10.0.1.63	christie.athome.net	christie
10.0.1.65	coffee1-PC
10.0.1.12	mythtv.athome.net	mythtv
10.0.1.40	icewarp.athome.net	icewarp
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
For what your doing I would recommend static ips. Then, Have you created your samba passwords on the samba server(s)? smbpasswd....

coffee
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
User avatar
SprinterDriver
Level 4
Level 4
Posts: 260
Joined: Sun Jan 25, 2015 3:35 pm
Location: Norway

Re: Cannot access shares on windows-computers on same network

Post by SprinterDriver »

Hi.

I have not created any password on the samba server as I know.

How comes I should use static IP?

I see that you have a sort of "domain setup", and I doesn't think that is the optimal solution for me. I still have some Windows computer in the network, and I doesn't see how I would get it work with computers with different os installed.
Also I have read some other web sites that similar problems have being asked, and I've not seen anywhere that suggest static IP addresses.
So I got this bright idea. But when I tried to grab the light bulb, I did not hurt my hands as expected from a warm bulb, because it turned out to be one of those LED bulbs.
User avatar
coffee412
Level 8
Level 8
Posts: 2263
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: Cannot access shares on windows-computers on same network

Post by coffee412 »

SprinterDriver wrote:Hi.

I have not created any password on the samba server as I know.

How comes I should use static IP?

I see that you have a sort of "domain setup", and I doesn't think that is the optimal solution for me. I still have some Windows computer in the network, and I doesn't see how I would get it work with computers with different os installed.
Also I have read some other web sites that similar problems have being asked, and I've not seen anywhere that suggest static IP addresses.
1. Using a static IP even if you have just one computer on the network saves you grief when troubleshooting an issue and is just good practice for any workstations. If it were a Laptop or cellphone or tablet that is mobile then stick with Dynamic. Also, Printers should always be static IPs.

So, To be clear on this point:

The following items should always be static IPs:

1. Workstations
2. Servers
3. Printers
4. Access Points / routers

Its no fun trouble shooting an issue only to find the reason its not working is that its IP address has changed. Its also not fun changing the configs for some device everytime the IP address changes. Keep in mind that A dynamic IP address has a good chance of changing on every reconnect to the network.

Ok, On the "Domain Setup" you eluded too: You should always follow the "Best Practice Rule". This means there is a right way to setup a network and if you do it the wrong way it may still work but will cause a lot of frustration down the road or lead to problems later on that will involve a lot more work on your end. Therefore, Each computer should have a FQDN (Fully qualified domain name).

Examples from my hosts file are "coffee.athome.net". Just using "coffee" does not cut it. Since I assume this is an internal or private network you can just name it anything you want.

If your going to share resources between windows computers and linux computers then it is advisable to create accounts on the windows computers for every person that will be accessing them. If its just one person then you should be set. However, You do have to create a password in order to connect to the windows computer. Unless you just configure your windows computer to share to anyone. This is not advised.

Read up on smbpasswd its extremely easy. Always follow the Best Practices rule and your problems will be few. Those that do not will always have issues with their networks.

coffee
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
User avatar
coffee412
Level 8
Level 8
Posts: 2263
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: Cannot access shares on windows-computers on same network

Post by coffee412 »

As for your particular problem once you get your ips and FQDN straightened out you will find that you will be able to ping your windows computers.

If your sharing files from your Mint box to windows then you have to have samba installed and setup correctly.

Here is a good howto on that:

https://www.howtogeek.com/howto/ubuntu/ ... on-ubuntu/

Here is my smb.conf file just for reference. Dino is my file server and I run a raid5 external box off of him that I share out. This is dino's smb.conf file.

Code: Select all

coffee@dino ~ $ cat /etc/samba/smb.conf
[global]
	netbios name = dino
	domain master = yes
	preferred master = yes 
	local master = yes
	wins support = yes
	wins proxy = yes
	os level = 65
	name resolve order = bcast host lmhosts wins 
        security = user
        workgroup = workgroup
        guest account = coffee
        log file = /var/log/samba/%m.log


[Renue]
        comment = Raid Storage for Windows
        path = /mnt/raid5/storage
        writable = yes
        read only = no
        guest ok = yes


[Dino Raid]
        comment = Storage on Dino
        path = /mnt/raid5
        writable = yes
        read only = no
        guest ok = yes
        guest only = yes 
coffee@dino ~ $ 
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
altair4
Level 20
Level 20
Posts: 11453
Joined: Tue Feb 03, 2009 10:27 am

Re: Cannot access shares on windows-computers on same network

Post by altair4 »

I didn't recklessly jump into this topic as I usually do for three reasons:

[1] I read this post: viewtopic.php?f=53&t=241327&p=1290806#p1290806
I figured this was more a networking issue than a file sharing / Samba issue and I'm not comfortable getting into that level.

[2] The Failed to retrieve share list from server part of the error message is usually a name resolution error and the name resolve order addition to your smb.conf file usually fixes it - assuming you don't have other issues like multiple subnets / routers or firewalls , etc..

[3] The Connection refused part of the error message is just plain odd.

My recommendation is a simple test of the coffee412 suggested solution without modifying anything:

** Go to a Windows machine and find your ip address at the moment:

Code: Select all

ipconfig
** Now go back to the mint machine, open a terminal and run:

Code: Select all

caja smb://192.168.0.100
Change 192.168.0.100 to the actual ip address of the Windows box.

See If you still get a Failed to retrieve share list from server: Connection refused error.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
User avatar
SprinterDriver
Level 4
Level 4
Posts: 260
Joined: Sun Jan 25, 2015 3:35 pm
Location: Norway

Yes - I can access a shared folder by IP address

Post by SprinterDriver »

Hi.

One steps ahead now. Running the caja command with ip address worked like a charm. A dialog box popped up asking for username and password, and I could see all the shares on the windows machine.

Comments to altair4 post:
1. That problem was eventually solved by itself. After four or five attempts, Mint eventually connected to the network.
2. I have only one router and one subnet.


Comments on coffee412 last post:
I've never had the need of putting FQDN to any of my Windows computers. As soon as I find out How, I will try.
Ok - I just tried to search internet for "windows xp set FQDN" and I just cannot find a recipee. Do I have to make the Linux Mint machine a domain controller and then on the Windows computers, add them to the domain?
Or if I have a computer now named "computer1 - would it be as simple as to rename it to something like "computer1.athome.no"?

So far I haven't shared anything on my Mint computer, but I will.

Thanks for sharing your smb.conf file. Have to admit that networking isn't what I can very well, so I may ask some basic/stupid question.
One of those: The Linux Mint computer may be powered on 24/7 - would it be a good idea to put it as domain master? Would that be a bad idea.
So I got this bright idea. But when I tried to grab the light bulb, I did not hurt my hands as expected from a warm bulb, because it turned out to be one of those LED bulbs.
altair4
Level 20
Level 20
Posts: 11453
Joined: Tue Feb 03, 2009 10:27 am

Re: Cannot access shares on windows-computers on same network

Post by altair4 »

Running the caja command with ip address worked like a charm. A dialog box popped up asking for username and password, and I could see all the shares on the windows machine.
Since this is coffee412's thread not mine I would just like to point out that you now know the answer to your question to him:
How comes I should use static IP?
Ultimately all machines in a network connect to each other with an ip address not a name. Different techniques are used to "resolve" a request by a user to connect to a machine by name like the whole netbios / master browser thing, the bcast first in "name resolve order", and even it's modern replacement mDNS. But all they do is convert a name to an ip address.

If all of your machines have a static ip address you cut out the middle man. Each machine can "map" to the other with their ip address.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
User avatar
coffee412
Level 8
Level 8
Posts: 2263
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: Cannot access shares on windows-computers on same network

Post by coffee412 »

Code: Select all

I've never had the need of putting FQDN to any of my Windows computers. As soon as I find out How, I will try.
Ok - I just tried to search internet for "windows xp set FQDN" and I just cannot find a recipee. Do I have to make the Linux Mint machine a domain controller and then on the Windows computers, add them to the domain?
Or if I have a computer now named "computer1 - would it be as simple as to rename it to something like "computer1.athome.no"?

So far I haven't shared anything on my Mint computer, but I will.

Thanks for sharing your smb.conf file. Have to admit that networking isn't what I can very well, so I may ask some basic/stupid question.
One of those: The Linux Mint computer may be powered on 24/7 - would it be a good idea to put it as domain master? Would that be a bad idea.
Top
Edit the following file: c:\windows\system32\drivers\etc\hosts

Enter your network info into it for any device on the network. ;)

Here is a good analogy for learning the basics of networking:

You live in a neighborhood. Well, This is your domain. Your domain is (Ill use mine for an example) home.net . Now, The homeowners all have a last name like Smith. So, Their sub domain is Smith.athome.net . Now, There are quite a few Smiths in the neighborhood. Theres Paul, Dave, Joe ect.. So, They are listed as joe.Smith.athome.net, Paul.Smith.home.net ect.. These are the fully qualified domain names.

Now everyone knows everyone in the neighborhood. So, when Joe goes to visit Paul he knows here he lives. But he will keep a list just in case with all his neighborhood families on it. This is your hosts file.

Now, There are those outside your neighborhood. They have no idea where Paul.Smith.athome.net lives. So, What they do is ask someone in the neighborhood where Paul lives. Well, This Someone is a DNS service. Someone replies "He lives at 13254 Maple Street". Well, That street address is your IP address.

To answer your other question about a Domain Controller:

Someone cannot seem to find anyone that knows where Paul lives. Well, Someone then asks where he can find out. He is told that the post office is a great place to find out. Well, The post office is the Domain Controller. They have a listing of everyone in the neighborhood. Of course, If you live in the neighborhood you do not really need a Domain controller if you have a updated hosts file. But sometimes updating this host file with tens of hundreds of computers on the network can be very hard to do. So, You use a domain controller to do all that work (besides other stuff).

Therefore, On a small network with static IPs you really do not need a domain controller. Everyone is in the hosts file :)

I hope this helps.

coffee
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
User avatar
SprinterDriver
Level 4
Level 4
Posts: 260
Joined: Sun Jan 25, 2015 3:35 pm
Location: Norway

Re: Cannot access shares on windows-computers on same network

Post by SprinterDriver »

Thank you coffee412 for a very good explanation. So then I don't need an domain controller at all, and I now understand that the FQDN of other machines only exists in the hosts file.

I've run the caja smb://192.168.0.100 comand, I got a password dialog box - entering a valid user name on that machine. And I then got the list of all shared folders on that computer. So far so good.

Next I double clicked one shared folder. A second time I'm asked for username/psw - and this time I got to actually see the contents.

Umm - it actually also works when I write the same command, but computername instead of IP: caja smb://computername. And it behaves the same. And I haven't edit any lines in the hosts file.

That is - problem solved. However - I like to keep the discussion alive for a bit longer so I can learn more, I have a long way to go to go before I can tell that I've learned to use Linux :?

I have another computer on the network (non essential for backup only) that have no password for login for one active user only. When I do the caja smb command on that computer, I get asked for user/psw but it seems to not accept empty passwords. Any way around this? (I can always create a new user account with an actual password)

There is one important thing I must remember to tell you.
I was looking around in another thread, and I found that a package called samba-common-bin is not installed in Linux Mint Mate. So I installed that one, and I reboot the computer (I might not need to reboot, but I did anyway).
During the install of samba-common-bin I was warned that the smb.conf file should be replaced. I knew I had posted the contents of smb.conf in this forum so I just selected replace the file. But when I opened the smb.conf file, I realized that the contents where not changed at all - how comes?
So I got this bright idea. But when I tried to grab the light bulb, I did not hurt my hands as expected from a warm bulb, because it turned out to be one of those LED bulbs.
User avatar
coffee412
Level 8
Level 8
Posts: 2263
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: Cannot access shares on windows-computers on same network

Post by coffee412 »

I have another computer on the network (non essential for backup only) that have no password for login for one active user only. When I do the caja smb command on that computer, I get asked for user/psw but it seems to not accept empty passwords. Any way around this? (I can always create a new user account with an actual password)
Assign a password to that computer.

samba-common is needed to either share out files/directories or to connect to windows shares. I forget :) - Im getting old.

As for the smb.conf file, I dont know. It may have just changed something that you missed ??

coffee
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
wedjlok

Re: Cannot access shares on windows-computers on same network

Post by wedjlok »

I have to jump in and say that I have just recently encountered a somewhat similar issue. I have 2 computers running Mint 18.1 and a Surface-Pro 4 running Windows 10 on my network. I can access all of the systems from the Windows machine, and all of the systems from one of the Linux machines but not from the other Linux machine.

Now I COULD access the them all from all machines at one point, but I ran into a boot up issue where I an error:

Code: Select all

User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by others.
After following the thread here:
viewtopic.php?t=166434
I was then able to regain access on that machine and everything acted normally again, with the exception of the network shares no longer being seen by that machine. When I go into the Network folder, it shows Windows Network, but then will not mount anything from it, just like was previously mentioned in this post.
altair4
Level 20
Level 20
Posts: 11453
Joined: Tue Feb 03, 2009 10:27 am

Re: Cannot access shares on windows-computers on same network

Post by altair4 »

@wedjlok, Just my opinion of course but I would suggest posting this error on your other post or starting a new one.

When you do post the output of the following commands from whatever machine gave you that error:

Code: Select all

testparm -s

Code: Select all

net usershare info --long

Code: Select all

hostname
It looks like you used the file manager ( Nemo or Caja ) to share your home directory. The output of the above commands will clarify things.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
User avatar
SprinterDriver
Level 4
Level 4
Posts: 260
Joined: Sun Jan 25, 2015 3:35 pm
Location: Norway

Results from Terminal commands

Post by SprinterDriver »

Thanks. Here is the results from the commands suggested:

I'm not sure what you meant by "output of the following commands from whatever machine gave you that error". Anyway I run this command on the only LM computer in this network. All other computers is Windows.

Code: Select all

username@computername ~ $ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
	workgroup = NA
	server string = %h server (Samba, Ubuntu)
	server role = standalone server
	security = USER
	map to guest = Bad User
	obey pam restrictions = Yes
	pam password change = Yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
	unix password sync = Yes
	syslog = 0
	log file = /var/log/samba/log.%m
	max log size = 1000
	name resolve order = bcast host lmhosts wins
	dns proxy = No
	wins support = Yes
	usershare allow guests = Yes
	panic action = /usr/share/samba/panic-action %d
	idmap config * : backend = tdb


[printers]
	comment = All Printers
	path = /var/spool/samba
	create mask = 0700
	printable = Yes
	browseable = No


[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers
username@computername ~ $ 

This command doesn't return any text at all.

Code: Select all

username@computername ~ $ net usershare info --long
username@computername ~ $ 

Code: Select all

username@computername ~ $ hostname
<valid computer name>
username@computername ~ $ ^C
There is one interesting observation that I have seen by running LM 17.3 Mate 64 bit Live-session on another computer in same network. That computer had never any issues by browsing shared resources on windows computers, included those that doesn't require username and password to access the files.
So I got this bright idea. But when I tried to grab the light bulb, I did not hurt my hands as expected from a warm bulb, because it turned out to be one of those LED bulbs.
Locked

Return to “Networking”