[Samba] Win 7 sees Linux, Win 10 doesn't - why?

RBEmerson · 11 March 2017 20:04

The situation is simple. Three machines are tied to a Verizon router by wire. 1) MATE 16.04 LTS (fresh full install - not update), 2) Win7, 3) Win10. All see the Internet.

On the Win10 box, Win7 and Win10 see each other in home group and in the Net.&Share page “Computer” and “Media Devices” sections. The MATE box isn’t present.

On the Win7 box, Win7 and Win 10 see each other. In the Net&Share page, Win7 sees Win10, Win7, and MATE. Win7 can copy files from Win10 to MATE.

I did several google searches. The results involved complex topographies and usually involving “clients who won’t listen”. There was nothing about a simple at-home net. Obviously, this has a 50/50 chance of being a Win 10 OS issue (what isn’t??), it’s a 16.04 issue. I’m baffled.

alpinejohn · 12 March 2017 04:49

Hallo

I’m no expert here, but could this have something to do with drive encryption?

Good luck, and I hope you don’t have to resort to usb-thumb-drives…

RBEmerson · 12 March 2017 14:21

My problem is I can’t even get to that point, except that the Win7 box can
access the Win10 HDD’s and the Linux HDD’s. The Win10 box cannot even “see”
the Linux box, and the Linux box can see the Win10 box but is not permitted
to the Win10 box’s HDD’s. Encryption applies *after *the various boxes can
attempt to read other boxes’ HDD’s. None of the HDD’s are encrypted.

IvCHo · 12 March 2017 17:34

Wait , wait , wait. Be more clear .
How do you share the files from the Linux PC ? (WebDav , Samba , NFS) .
I personaly think you refer to SAMBA .

RBEmerson · 13 March 2017 04:44

Yes, it’s all with Samba. HTH

IvCHo · 13 March 2017 11:35

Can you post your samba config ? ( Should be /etc/samba/smb.conf )
What is the output of :

sudo systemctl status nmbd.service

sudo systemctl  status smbd.service

RBEmerson · 13 March 2017 13:54

nmbd status:

    ● nmbd.service - LSB: start Samba NetBIOS nameserver (nmbd)
       Loaded: loaded (/etc/init.d/nmbd; bad; vendor preset: enabled)
       Active: active (running) since Sat 2017-03-11 14:05:06 EST; 1 day 18h ago
         Docs: man:systemd-sysv-generator(8)
      Process: 1404 ExecStart=/etc/init.d/nmbd start (code=exited,
    status=0/SUCCESS)
       CGroup: /system.slice/nmbd.service
               └─1726 /usr/sbin/nmbd -D

Mar 11 14:04:58 system-p6531p systemd[1]: Starting LSB: start Samba NetBIOS
name
Mar 11 14:05:05 system-p6531p nmbd[1404]:  * Starting NetBIOS name server
nmbd
Mar 11 14:05:06 system-p6531p nmbd[1404]:    ...done.
Mar 11 14:05:06 system-p6531p systemd[1]: Started LSB: start Samba NetBIOS
names
lines 1-12/12 (END)

smbd status:
● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd; bad; vendor preset: enabled)
   Active: active (running) since Sat 2017-03-11 14:05:06 EST; 1 day 18h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 10380 ExecReload=/etc/init.d/smbd reload (code=exited,
status=0/SUCCE
  Process: 1727 ExecStart=/etc/init.d/smbd start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/smbd.service
           ├─ 608 /usr/sbin/smbd -D
           ├─1775 /usr/sbin/smbd -D
           ├─1794 /usr/sbin/smbd -D
           └─1894 /usr/sbin/smbd -D

Mar 12 12:35:36 system-p6531p smbd[28873]: pam_unix(samba:session): session
clos
Mar 12 12:39:04 system-p6531p smbd[29075]: pam_unix(samba:session): session
clos
Mar 12 12:39:04 system-p6531p smbd[29076]: pam_unix(samba:session): session
clos
Mar 12 12:46:34 system-p6531p smbd[29530]: pam_unix(samba:session): session
clos
Mar 12 12:46:34 system-p6531p smbd[29531]: pam_unix(samba:session): session
clos
Mar 12 12:53:52 system-p6531p smbd[29994]: pam_unix(samba:session): session
clos
Mar 12 12:53:52 system-p6531p smbd[29995]: pam_unix(samba:session): session
clos
Mar 12 12:58:04 system-p6531p smbd[30259]: pam_unix(samba:session): session
clos
Mar 12 12:58:04 system-p6531p smbd[30260]: pam_unix(samba:session): session
clos
Mar 13 02:23:45 system-p6531p smbd[20876]: pam_unix(samba:session): session
clos

smb.conf
Everything is box stock except for the following:
[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

[Home Share]

comment = Home Public Folder
path = /home/system/
writeable = yes
valid users = system

"system" is my admin account.

Remember the Win7 machibe can copy data between the Win10 machine and the
MATE machine. The MATE machine can reach the Win10 machine but cannot gain
access to shares. The Win10 machine doesn’t even see the MATE machine but
sees and accesses the Win7 machine.

IvCHo · 13 March 2017 14:53

I think that in the [Home Share] section there should be :

browseable = yes

Try to add it , and restart the smbd and nmbd service .

The rest of the config seems legit .

Also is " workgroup " option in the general section the same as the windows workgroup .
I have read on topics that sometimes that couses problems .

Is your Netbios name longer than 15 chars ? ( By default it is set to the Hostname ) ( can be find with " hostname " command ). If it is specify it with netbios name = (Name) in the general section .
That is known to couse problems .

RBEmerson · 13 March 2017 16:30

Adding browseable = yes did not change things. Neither did the
13 character host name netbios = system-p6531p Curiously,
there was no string “netbios =” in the conf file, not even as a
comment/example. Odd…

I used sudo systemctl restart smbd|nmbd Neither restart
produced an error code, so I assume the daemons restarted as they should,
reading the revised smb.conf as they started again.

RBEmerson · 13 March 2017 16:33

BTW is there a gmail equivalent???

IvCHo · 14 March 2017 10:36

Then this might be a problem with Win 10 since you know … It’s Win 10

RBEmerson · 14 March 2017 16:12

The problem reduces to the interface of two different OS’s. If I can be
reasonably sure that at least one of the two is almost certainly setup
correctly, that removes half of the problem.

I did a functioning Samba setup, under SuSE, longer ago than I care to
admit. And it interfaced with Win 7. That’s Samba setup is covered over by
this MATE installation. There’s no way to recover the old .conf. So I asked
for help in this forum.

My sense is the present .conf is essentially correct. which (sigh…)
leaves me to wrestle with (hateful) Win10. For several reasons, I regret
ever installing it. I’d go back to Win 7 if it weren’t going to be far too
traumatic (includes re-installing for too much). OK, I’m whinging and
venting…

I certainly want to hear from anyone who has a working MATE/Win 10 net
going.

RBEmerson · 14 March 2017 18:46

Going back to basics, I looked up the Win10’s IP (properties for the
ethernet port):
192.168.1.5

system@system-p6531p:~/Desktop$ ping 192.168.1.5
PING 192.168.1.5 (192.168.1.5) 56(84) bytes of data.
64 bytes from 192.168.1.5: icmp_seq=1 ttl=128 time=0.473 ms
64 bytes from 192.168.1.5: icmp_seq=2 ttl=128 time=0.598 ms
64 bytes from 192.168.1.5: icmp_seq=3 ttl=128 time=0.475 ms
64 bytes from 192.168.1.5: icmp_seq=4 ttl=128 time=0.443 ms
64 bytes from 192.168.1.5: icmp_seq=5 ttl=128 time=0.449 ms
64 bytes from 192.168.1.5: icmp_seq=6 ttl=128 time=0.478 ms
64 bytes from 192.168.1.5: icmp_seq=7 ttl=128 time=0.365 ms
64 bytes from 192.168.1.5: icmp_seq=8 ttl=128 time=0.405 ms
64 bytes from 192.168.1.5: icmp_seq=9 ttl=128 time=0.394 ms
64 bytes from 192.168.1.5: icmp_seq=10 ttl=128 time=0.406 ms
64 bytes from 192.168.1.5: icmp_seq=11 ttl=128 time=0.443 ms
64 bytes from 192.168.1.5: icmp_seq=12 ttl=128 time=0.409 ms
64 bytes from 192.168.1.5: icmp_seq=13 ttl=128 time=0.453 ms
64 bytes from 192.168.1.5: icmp_seq=14 ttl=128 time=0.415 ms
^C
--- 192.168.1.5 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13309ms
rtt min/avg/max/mdev = 0.365/0.443/0.598/0.056 ms

I used ifconfig to figure out what interface my ethernet connection is on,
and its IP:

system@system-p6531p:~/Desktop$ ifconfig
enp5s0    Link encap:Ethernet  HWaddr 78:e7:d1:d7:37:5e
          inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a3ab:ef69:e86d:5dba/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2349118 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1025969 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3315512347 (3.3 GB)  TX bytes:115228338 (115.2 MB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:47973 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47973 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:4469376 (4.4 MB)  TX bytes:4469376 (4.4 MB)

wlp2s0    Link encap:Ethernet  HWaddr 70:f1:a1:b1:93:be
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Arp-scan gave:

system@system-p6531p:~/Desktop$ sudo arp-scan --interface=enp5s0  --localnet
Interface: enp5s0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.8.1 with 256 hosts (
http://www.nta-monitor.com/tools/arp-scan/)
192.168.1.1 00:7f:28:db:55:08 (Unknown)
192.168.1.4 00:1b:a9:41:2f:9b BROTHER INDUSTRIES, LTD.
192.168.1.5 e8:03:9a:e6:c9:cb (Unknown)
192.168.1.15 28:c6:8e:1b:06:8f (Unknown)
192.168.1.2 78:4b:87:4d:6c:4d (Unknown)
192.168.1.2 78:4b:87:4d:6c:4d (Unknown) (DUP: 2)
192.168.1.8 00:18:de:2c:35:53 Intel Corporation
192.168.1.7 00:8e:f2:4f:ea:60 (Unknown)
192.168.1.13 b0:79:94:4a:9e:ee (Unknown)
192.168.1.100 58:56:e8:76:75:d7 (Unknown)
192.168.1.10 02:0f:b5:a4:6d:7d (Unknown)

11 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.8.1: 256 hosts scanned in 1.351 seconds (189.49
hosts/sec). 11 responded

Brother is my printer. .8 is the Win7 box. Win10 (.5) is unidentified.

I used Wireshark (on Win10) and can see MATE (.12). Unfortunately I’m
almost illiterate about reading what’s going on in the Wireshark display.

Bottom line: there seems to be nothing grossly wrong on the net. The router
doesn’t seem to be filtering or blocking anything, and neither is any
firewall.

Moving on to what an attempt to get to a folder looks like on the MATE
box…

Double-clicking Network opens up and shows “Windows Network”.
Double-clicking it shows “WORKGROUP” and “WXNET” (internat network name).
So far, no surprises.

Double-clicking WORKGROUP shows:

Win7
Printer
MATE

Note that Win10 is missing.

Back up to WXNET, drill down, and there’s the Win10 machine. Double-click
on it and there the shared folders:Music, Pictures, Videos, Users - the
usual suspects (plus C:, etc., listed by choice). Double-click on Music
and…
Unable to mount location - Failed to mount Windows share: Permission denied.

Who is doing the denial? Win10? MATE?

Going the other way is brief. Open Network and Devices.

The printer is listed under Printers.
Network Infrastructure shows the router.
Media Devices shows Win10 and Win7
Computer shows Win10 and Win7 but not MATE

Opening Homegroup shows Win10 and Win7 but not MATE - as expected.

The problem is the interface between two OS’ isn’t working. MATE, as Ive
said, sees Win10 but can’t use the shares. Win10 doesn’t see MATE.

Why?

jake19 · 14 March 2017 22:37

my first look would be the w10 ‘firewall’ and other security features theyve enabled. ive seen that have bearing before.

RBEmerson · 15 March 2017 01:38

I’d buy into that more if the MATE box couldn’t even find the shares or the
Win10 box.

It’s still unclear to me about who’s denying permission to mount a share.
My sense is that’s the MATE box being unhappy about the mount. I ran mount
but couldn’t find any obvious mnt subdir. Does that even exist?

IvCHo · 15 March 2017 11:27

As I searched the internernet I found that your problem is the same as this.
Now that appears to be a protocol issue betwene SAMBA and Windows 10 protocol . So the problem is in deed with Windows 10 . As you can see in the topic provided this can be resolved this way

Run Windows PowerShell as ‘Administrator’

Enter the following commands:

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

reboot

This should do it .
For more info see the topic.

RBEmerson · 15 March 2017 15:36

While PowerShell confirmed both commands executed successfully, following a
restart there was only one observable change. Win10 is no longer reported,
on Win10, as a media device - a "don't care" result.

Since the Win10 PowerShell commands are based This link to lists.samba.org
https://lists.samba.org/archive/samba/2015-September/193886.html and I
wondered what rev. I'm using, I checked the rev. number with this post on
l.s.o. https://lists.samba.org/archive/samba/2002-July/047123.html .That
gives "Version 4.3.11-Ubuntu". The question, then, is "does 4.3.11 handle
what's described here: "Windows 10 will try to negotiate SMB3_11, which
Samba4 doesn't yet support except in the current 4.3 release candidate."?
(emphasis added) Since I'm using 4.3.11, I'm inclined to think the change
suggested is no longer needed/valid. Witness the results, I think that's
the case.

The following may be irrelevant to the "MATE sees Win10, Win10 doesn't see
MATE" issue. NTL please look at the attached screen capture. It shows what
MATE can see what Win10 will share, and what happens when trying to access
one of those shares. Who is unable to mount that share: MATE or Win10?

I'm going to back out the PowerShell mods based on MS' list of what's
broken when the above made is done.

word7_g · 29 March 2017 13:29

Have you tried to use a ssh channel instead of samba?
This could be the solution to your porblem.

RBEmerson · 31 March 2017 13:58

I haven’t tried ssh here, although I’ve used an ssh tunnel for something
completely different. I built a tunnel between a cell phone and SuSE Linux
to get past problems with Bell South. Go figure. Anyway, I’ll give it a
shot.

Thanks for the suggestion.