On 01/08/2019 17:42, Helmut Harnisch wrote:
> Am 01.08.2019 um 16:43 schrieb Fokke Nauta:
>> pi@raspberrypi:~ $ netstat -tapn | grep smbd
>> (Not all processes could be identified, non-owned process info
>>   will not be shown, you would have to be root to see it all.)
>>
>> pi@raspberrypi:~ $ sudo netstat -tapn | grep smbd
>> tcp        0      0 0.0.0.0:445            
0.0.0.0:* LISTEN
>> 11978/smbd
>> tcp        0      0 0.0.0.0:139            
0.0.0.0:* LISTEN
>> 11978/smbd
>> tcp6       0      0 :::445                  :::*
LISTEN      11978/smbd
>> tcp6       0      0 :::139                  :::*
LISTEN      11978/smbd
>>
>> Does this mean anything to you?
>
> the first two lines say that your machine listens on port 445 and 139
> (new and old samba over tcpip ports) on ALL interfaces that it founds
> (0.0.0.0 is for all interfaces not for a specific one.)
>>
>>>
>>> netstat -apn | grep nmbd
>>
>> pi@raspberrypi:~ $ sudo netstat -apn | grep nmbd
>> udp        0      0 192.168.1.255:137       0.0.0.0:*
       11947/nmbd
>> udp        0      0 192.168.1.2:137         0.0.0.0:*
       11947/nmbd
>> udp        0      0 0.0.0.0:137            
0.0.0.0:*        11947/nmbd
>> udp        0      0 192.168.1.255:138       0.0.0.0:*
       11947/nmbd
>> udp        0      0 192.168.1.2:138         0.0.0.0:*
       11947/nmbd
>> udp        0      0 0.0.0.0:138            
0.0.0.0:*        11947/nmbd
>> unix  2      [ ]        
DGRAM                    534571   11947/nmbd
>>         /var/lib/samba/private/msg.sock/11947
>> unix  2      [ ACC ]     STREAM     LISTENING    
534589   11947/nmbd
>>         /var/run/samba/nmbd/unexpected
>>
>>> You should see the ip of the raspberry (192.168.1.2)
>>
>> The IP address is visable.
>
> the name server service for samba/cifs requests is bound to various
> ports on different ip addresses. x.255 is the broadcast, .1.2 is your
> raspberry and 0.0.0.0 is for all internet adresses/interfaces.
>>
>>> if not, your interface does not listen to smb
>>>
>>>
>>> Did you explain the content of your user mapping file?
>>> please cat /home/pi/samba/usermap.txt
>>
>> pi@raspberrypi:~ $ cat /home/pi/samba/usermap.txt
>> pi = "Fokke Nauta"
>
> that means that your user "Fokke Nauta" on your windows machine matches
> the user pi on your raspberry. Make sure your windows password is the
> same that you set with password pi on your raspberry.
>
> I dont know at the moment why and how your smbpasswd reacts in this
> situation... maybe never if you want to connect with your username
> "Fokke Nauta" from Windows to your raspberry.
>
> Maybe this helps to connect to
>
> net use X: \\raspberry\pishare /user:"Fokke Nauta" password

[C:\Program Files\JPSoft\TCCLE14x64]net use s: \\raspberrypi\pishare
/user:"Fokke Nauta"
The password or user name is invalid for \\raspberrypi\pishare.

Enter the password for 'Fokke Nauta' to connect to 'raspberrypi':
System error 1326 has occurred.

The user name or password is incorrect.

>
> but strange that you cant get the shares by typing
>
> net view raspberry
> or
> net view \\raspberry

[C:\Program Files\JPSoft\TCCLE14x64]net view \\raspberrypi
System error 53 has occurred.

The network path was not found.

> or
> net view \\192.168.1.2
>

[C:\Program Files\JPSoft\TCCLE14x64]net view \\192.168.1.2
System error 53 has occurred.

The network path was not found.

What is really weird, is that I see the pi in my network (This pc -
Network). It is there between the other pc's, but it remains unaccessable.

Never thought it would be so difficult to create a share in the pi. To
be honest, I'm about to give up ...

--- SoupGate-Win32 v1.05