chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
Ich verstehe noch nicht ganz, was du mit beidseitigem Zugriff meinst. Du kannst ja mal die Server Rolle auf standalone umstellen und dann für beide Rechner folgende Ausgaben posten:
sudo apt-get install smbclient
smbclient -L localhost
smbclient -L IP-des-anderen-Pc
|
luigi17
(Themenstarter)
Anmeldungsdatum: 9. August 2008
Beiträge: 1798
Wohnort: Weserbergland
|
OK, hab ich gemacht:
rainer@rainer-desktop:~$ smbclient -L localhost
WARNING: The "syslog" option is deprecated
Enter WORKGROUP\rainer's password:
Anonymous login successful
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
IPC$ IPC IPC Service (rainer-desktop server (Samba, Ubuntu))
HP-HP-OfficeJet-Pro-8710 Printer HP HP OfficeJet Pro 8710
Scan-PC Disk
Reconnecting with SMB1 for workgroup listing.
Server requested PLAINTEXT password but 'client plaintext auth = no'
session setup failed: NT_STATUS_INVALID_PARAMETER
Failed to connect with SMB1 -- no workgroup available
rainer@rainer-desktop:~$ smbclient -L 192.168.0.4
WARNING: The "syslog" option is deprecated
Enter WORKGROUP\rainer's password:
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
IPC$ IPC IPC Service (rainer-notebook server (Samba, Ubuntu))
HP_OfficeJet_Pro_8710_F61CCB_ Printer HP_OfficeJet_Pro_8710_F61CCB_
HP-HP-OfficeJet-Pro-8710 Printer HP HP OfficeJet Pro 8710
Scan-NB Disk
Öffentlich Disk
rainer-notebook Disk
Reconnecting with SMB1 for workgroup listing.
Server Comment
--------- -------
Workgroup Master
--------- -------
WORKGROUP RAINER-DESKTOP
rainer@rainer-desktop:~$
|
chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
Ok, und jetzt noch bitte von dem anderen Rechner.
|
luigi17
(Themenstarter)
Anmeldungsdatum: 9. August 2008
Beiträge: 1798
Wohnort: Weserbergland
|
Voilà:
rainer@rainer-notebook:~$ smbclient -L localhost
WARNING: The "syslog" option is deprecated
Enter WORKGROUP\rainer's password:
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
IPC$ IPC IPC Service (rainer-notebook server (Samba, Ubuntu))
HP_OfficeJet_Pro_8710_F61CCB_ Printer HP_OfficeJet_Pro_8710_F61CCB_
HP-HP-OfficeJet-Pro-8710 Printer HP HP OfficeJet Pro 8710
Scan-NB Disk
Öffentlich Disk
rainer-notebook Disk
Reconnecting with SMB1 for workgroup listing.
Server Comment
--------- -------
Workgroup Master
--------- -------
WORKGROUP RAINER-DESKTOP
rainer@rainer-notebook:~$ smbclient -L 102.168.0.3
WARNING: The "syslog" option is deprecated
Connection to 102.168.0.3 failed (Error NT_STATUS_IO_TIMEOUT)
Leider finde ich jetzt auch auf dem PC ein anderes Ergebnis:
rainer@rainer-desktop:~$ smbclient -L localhost
WARNING: The "syslog" option is deprecated
Enter WORKGROUP\rainer's password:
Anonymous login successful
Sharename Type Comment
--------- ---- -------
print$ Disk Printer Drivers
IPC$ IPC IPC Service (rainer-desktop server (Samba, Ubuntu))
HP-HP-OfficeJet-Pro-8710 Printer HP HP OfficeJet Pro 8710
Scan-PC Disk
Reconnecting with SMB1 for workgroup listing.
Server requested PLAINTEXT password but 'client plaintext auth = no'
session setup failed: NT_STATUS_INVALID_PARAMETER
Failed to connect with SMB1 -- no workgroup available
|
chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
Das Ergebnis ist doch identisch zum vorherigen Post. ☺ Mit localhost fragst du nur den lokalen Samba Dienst ab. Du hast einmal übrigens einen Zahlendreher drin. 102 anstelle von 192. Also was mir auffällt: Deine Samba Konfigurationen sind unterschiedlich. Teils nutzt du auch noch smb Version 1. Teils willst du auch noch ein Plaintext Passwort. Dass der Zugriff als DC funktioniert, ist eher Zufall denke ich. Aus meiner Sicht wäre es sinnvoller, eine Konsolidierung beider Samba Dienste durchzuführen. Dazu bräuchte man aber die Ausgaben der smb.conf beider Rechner. Wenn nur 2 Ubuntu Rechner für Samba genutzt werden, würde ich anstelle von Netbios lieber Avahi nehmen.
|
luigi17
(Themenstarter)
Anmeldungsdatum: 9. August 2008
Beiträge: 1798
Wohnort: Weserbergland
|
Dies war bisher alles interessehalber. Mit openssh-server geht es am einfachsten. Das reicht mir vollkommen. Hier ist mein Interesse, ob es zw. 2 Rechnern mit Linux auch per Samba einfach geht. Vielleicht ist das ganze Hin und Her der Einstellungen in der smb.conf dafür verantwortlich, dass es nicht beidseitig geht, das ganze Dateisystem zu sehen, oder zumindest den gesamten Home-Ordner.
|
chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
Also ssh wäre schon sinnvoller, wenn du den kompletten Inhalt deiner Laufwerke sehen willst. Grundsätzlich sollte die Freigabe des homes allerdings auch mit Samba gehen. Wie gesagt du kannst ja mal beide smb.confs posten.
|
luigi17
(Themenstarter)
Anmeldungsdatum: 9. August 2008
Beiträge: 1798
Wohnort: Weserbergland
|
Hier ist die smb.conf vom Notebook:
#
# 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)
# 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
# classic 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
# 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
und hier die vom PC:
#
# 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)
# 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
usershare owner only = False
#### 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 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
# 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
username map = /etc/samba/smbusers
security = user
encrypt passwords = no
; guest ok = no
; guest account = nobody
#======================= 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
|
chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
Ist das jeweils die smb.conf aus /etc/samba/smb.conf? Wenn ja: es fehlen die Shares, d. h. hast die Shares nicht über die smb.conf sondern über net usershare erstellt: net usershare info
|
luigi17
(Themenstarter)
Anmeldungsdatum: 9. August 2008
Beiträge: 1798
Wohnort: Weserbergland
|
OK:
net usershare info
[Scan-PC]
path=/home/rainer/Scan-PC
comment=
usershare_acl=Everyone:F,
guest_ok=y
info_fn: file /var/lib/samba/usershares/öffentlich is not a well formed usershare file.
info_fn: Error was Path is not a directory.
|
chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
Also falls du Lust hast, dann kannst du mal folgendes machen. | sudo mv /etc/samba/smb.conf /etc/samba/smb.conf.backup
|
| sudo cp /usr/share/samba/smb.conf /etc/samba/smb.conf
|
| net usershare delete Scan-PC
net usershare info #sollte jetzt leer sein
|
| echo -e "[share]\npath = /home/rainer/Scan-PC\nguest ok = Yes\nforce user = rainer\nforce group = rainer" | sudo tee -a /etc/samba/smb.conf
|
| chmod o=rwx -R /home/rainer/Scan-PC
|
| sudo apt-get install avahi-daemon avahi-utils
sudo nano /etc/avahi/services/smb.service
|
<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
<name replace-wildcards="yes">%h</name>
<service>
<type>_smb._tcp</type>
<port>445</port>
</service>
</service-group> Alles bezogen auf rainer-desktop.
|
luigi17
(Themenstarter)
Anmeldungsdatum: 9. August 2008
Beiträge: 1798
Wohnort: Weserbergland
|
OK, hab ich gemacht. Was mir als erstes auffällt: Unter Netzwerk ist auf beiden Rechnern der PC doppelt (einmal in Kleinschrift und einmal in Großbuchstaben, siehe Anhang), das Notebook gar nicht verzeichnet.
Insofern ist die Aktion noch nicht nützlich gewesen. 😉 UPDATE:// Hab gemerkt, dass aufgrund der Neuinstallation auf dem Notebook Samba erst wieder installiert werden mußte. Jetzt erscheint auf dem Notebook unter Netzwerk der PC und das Notebook, beides in GROSSBUCHSTABEN, auf dem PC zusätzlich der PC in Kleinbuchstaben...
- Bilder
|
chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
Die doppelte Ausgabe erscheint wg Avahi und Netbios (Rechnername in Großbuchstaben). Ich würde smb Version 1 deaktivieren und den Netbios Port sperren. Siehe hier.
|
luigi17
(Themenstarter)
Anmeldungsdatum: 9. August 2008
Beiträge: 1798
Wohnort: Weserbergland
|
Das ist mir jetzt - ehrlich gesagt - zu weitführend. Siehe Titel dieses Threads. 😉 Herzlichen Dank für deine Vorschläge. Bis hierhin hatte ich sie gern mitgemacht. Unterm Strich hat sich für mich mindestens gezeigt, dass das Einrichten einer Netzwerkverbindung zwischen 2 Linux-PCs sowohl mit Samba als auch mit openssh einfach ist / sein kann. Und das freut mich auch.
|
chr123
Anmeldungsdatum: 19. Juli 2018
Beiträge: 1632
|
luigi17 schrieb: Das ist mir jetzt - ehrlich gesagt - zu weitführend. Siehe Titel dieses Threads. 😉
Also im Prinzip sind das nur 2 Einzeller. Wenn du die Ausgabe von
testparm -vs | egrep 'protocol|port'
liefert, könnte man den entsprechenden Einzeller erstellen.
|