SUSE access to Server (NAS)

following setup:
3 computer with SUSE SLED 15.2
2 Laptop with Windows 10
NAS Sever Sznology with DSM. DSM is Linux, but an special and in fact very comfortable version of Linux
The server runs NFS, but not NIS. We use AD network that is supported by Windows and Linux as well.
DHCP server comes from a Cisco Firewall
Problem:
Windows can see the see the server.
Linux, wen you klick on windows network - Unable to access location, Failed to retrieve share listr from Server: No such file or directory.
SAMBA has been setup
UserLogon setup
But Computer name is not resolvable.
I can add network drives - but only via IP adress (same for printer), but both via SMB or NFS.

SUSE Service had checked it, tried a lot, we made a complete fresh and virgin installation - couldn't find a solution. It has been reported as bug - but SUSE can't find a bug, closed the case

Question: What goes wrong here.

Comments

  • malcolmlewismalcolmlewis Knowledge Partner
    edited April 8

    @HANS-CHRISTOPH Hi, likely the SMB version on the NAS, which is?
    If you try logging in from the command line on the linux guest and run smbclient -d 3 -L //<host_ip>/ does it show errors?

  • edited April 12

    Hi Malcom,
    sorry for late reply - was somehow busy. You are really good - always answering. However, i talked with SUSE developer - are German as well :-) - and told them only those responses for failure make the system better. Microsoft do that by pulling Metadata - we need to do in different ways. But, SUSE got better - much better - compared to version 11.

    The NAS runs both SMB 2 and 3 and large MTU. The detailed version I couldn't find.
    SLED15Desktop:/home/hans-christoph # smbclient -d 3 -L //10.0.25.3/
    Enter HCPIN\hans-christoph's password:
    GENSEC backend 'gssapi_spnego' registered
    GENSEC backend 'gssapi_krb5' registered
    GENSEC backend 'gssapi_krb5_sasl' registered
    GENSEC backend 'spnego' registered
    GENSEC backend 'schannel' registered
    GENSEC backend 'naclrpc_as_system' registered
    GENSEC backend 'sasl-EXTERNAL' registered
    GENSEC backend 'ntlmssp' registered
    GENSEC backend 'ntlmssp_resume_ccache' registered
    GENSEC backend 'http_basic' registered
    GENSEC backend 'http_ntlm' registered
    GENSEC backend 'http_negotiate' registered
    Cannot do GSE to an IP address
    Got challenge flags:
    Got NTLMSSP neg_flags=0x62898215
    NTLMSSP: Set final flags:
    Got NTLMSSP neg_flags=0x62088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x62088215
    NTLMSSP Sign/Seal - Initialising with flags:
    Got NTLMSSP neg_flags=0x62088215

        Sharename       Type      Comment
        ---------       ----      -------
        netlogon        Disk      
        sysvol          Disk      
        ActiveBackupforBusiness Disk      
        drive_h         Disk      
        drive_i         Disk      
        drive_p         Disk      
        drive_x         Disk      
        homes           Disk      user home
        music           Disk      System default shared folder
        photo           Disk      System default shared folder
        usbshare1       Disk      Western Digital Technologies, Inc.
        Users           Disk      
        video           Disk      System default shared folder
        IPC$            IPC       IPC Service ()
        dell_3100cn     Printer   Dell Laser Printer 3100cn
        hp_laserjet_700 Printer   Hewlett-Packard HP LaserJet 700 color MFP M775
    SMB1 disabled -- no workgroup available
    We do not use SMB1 since 2 and 3 are more safe. 
    
  • malcolmlewismalcolmlewis Knowledge Partner

    @HANS-CHRISTOPH Hi, so looks like just a netbios naming issue, I'm not a samba user, just use sftp/scp etc ;)
    Have a read here: https://documentation.suse.com/sles/15-SP2/html/SLES-all/cha-samba.html and suggest a google of samba+Troubleshooting NetBIOS names

  • ok, thanks. I'll check up. But is netbios not an very old protocol?

  • I get this result:
    SLED15Desktop:/etc/samba # net ads join -U Administrator -S HCPIN
    Enter Administrator's password:
    Failed to join domain: failed to lookup DC info for domain 'HCPI.HQ' over rpc: {Operation Failed} The requested operation was unsuccessful.

  • I placed many screenshots here - not sure they are visible?

  • malcolmlewismalcolmlewis Knowledge Partner

    @HANS-CHRISTOPH Hi is the firewall running, if so stop temporarily and test.

Sign In or Register to comment.