Basic networking - Getting 2 PCs to work with each other.

Soldato
Joined
18 Oct 2002
Posts
10,383
Location
Behind you... Naked!
Right, I have a number of PCs on my network and ?I haver had nothing but trouble since day one.
So, I am going to get to the most basic thing that I can.

I am ONLY going to involve 2 PCs in this question.

Both PCs are connected to my switch, and that is then connected to my Modem/Router.
Both PCs are running a very very fresh install of MINT Cinnamon 21.1.
They both see each other, but they both will not access each others files.
I have made the Public folder, shared with full access.
I have SAMBA installed but I have NOT configured anything.

Why does it do this and what can I do to resolve it?

Thank you.


Secondary Question, Network linked. This is for any Linux PC, when I try to access files that I have already previously accessed..

When I try to access the shared files on one of the Windows PCs, I get a small dialog box to to enter the User, Domain, and Password. I leave the Womain as WORKGROUP but I enter my user name and the password, and I click on the Remember Forever button.

I then get access to it without any issues.

The thing is, that I need to enter these details EVERY time I need to access that Folder, after its is logged on.

I have even used a password keeper ( The one built into Linux ) and yet it still forgets every time?

It has doen this on every install and every distro that I have tried. My username and passwords are the same on the Windows PCs and the Linux PCs on this network that I am trying to get working, btu of course the names are different on the other machine,s just these two.

Any reason for this to?

Again if you can help, then cool.
 
Soldato
OP
Joined
18 Oct 2002
Posts
10,383
Location
Behind you... Naked!
Ok bud.

I have NOT touched the file, this is the one that is in it RIGHT NOW.

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

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

#### 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 syslog@1 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 = classic
# primary domain controller', 'server role = classic 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 =======================

# 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



>->->->->->->

I have NOT as I said, touched this file.

I have tried various MIN and MAX options

Like

MIN PROTOCOL = SMB2
MAX PROTOCOL = SMB2

I have of course tried SMB3 and NT1 too

I have also tried CLIENT MIN ( or MAX ) PROTOCOL = whatever

Although, right now, I am about to have another play cos its nearly 7am and Im still up!
 
Soldato
OP
Joined
18 Oct 2002
Posts
10,383
Location
Behind you... Naked!
Ok, been reading that Wiki with some interest.
much of it is going over my head. I have some weird inability to learn things since my accident, and then all of a sudden, several weeks later, I get sparks of stuff and things happen, and I rememeber and get stuff sorted, but then I forget what I just did.

Im kind of in that stage of my life where that is a thing for me.

So, Im just going to keep at it.

But this is something that has been an issue for me for quite some time.

Its like this...

My main PC ( Windows 10 ) is named MASTER
My Server ( Windows 10 ) is named SERVER ( Shurrup, I know ) - it serves nothing, just a backup of everything really, plus my Music and movie collection ( Yes, all legal ) and a few other bits of blab.

These PCs are both Windows 10 Pro, but they are different versions. The Server is easy to access and I have ZERO issues getting to it, from any PC, be they Windows, Linux, or Mac, or any Desktop or Laptop.

However, the MASTER is a total ****. What I do, is get onto the SERVERS D: and then enter the MASTER folder instead.

So, instead of smb://SERVER/d I change SERVER to MASTER and I get onto it, but I cannot get onto just MASTER?

But when it comes to the Linux PCs... I simply cannot get onto them from Linux or Windows?

I did for a short while use Linux as my Server OS but this issue caused me to go back to Windows. Shame. I never had this issue until a few years back, now I never have anything but this issue.
 
Soldato
OP
Joined
18 Oct 2002
Posts
10,383
Location
Behind you... Naked!
I already do have 4 of them.

2 DLINKS ( both 2x2TB ) and 2 NETGEAR ( Both 4x4TB ) but my server also has 5x8TH and 4x4TB

Yeah, Im a hoarder of files and ISOs and stuff.

But sometimes, I just want oen of my Linux PCs to access the files off another!

To be fair, I also have some issues with my Master Windows PC... The Server has ZERO issues being contacted by any of the PCs, but for some reason the Master does... They are both different Versions of Windows 10.

But I just need one Linux PC to talk to another Linux PC and Its a bitch to sort for some reason?

And they are all connected to a switch, and then on to the Modem/Router.

Also, for what it is worth, I changed my ASUS router for the original VODAFONE one, for a bit, and I found that most computers were simply not seen and they were not accessing the network at all, until I put the ASUS back on! - Yes, everythign was reset and so on, so there should be no reason for that, but it was a thing... Its done this a couple of times over the years.
 
Back
Top Bottom