NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

bubu's avatar
bubu
Aspirant
Oct 02, 2022
Solved

Can't turn on SMB

Hi   I have RND516 with 6.10.8 firmware. Since today I had issue with my MAC and TimeMachine through AFP on RND. I tried trough SMB but since SMB start and stop. Impossible now to turn on SMB in...
  • StephenB's avatar
    StephenB
    Oct 05, 2022
    bubu wrote:

    It did it right away and also manual reboot

    same issue after reboot

     

    Ok.  Then the script didn't run.  I think the issue is that the certificate has expired.

     

    Try these commands instead

     

    cd //
wget --no-check-certificate https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh
chmod +x ./share_lun_ui_fix.sh
./share_lun_ui_fix.sh

     

     

     

StephenB's avatar
StephenB
Guru - Experienced User
Oct 02, 2022
bubu wrote:

 

Impossible now to turn on SMB in NAS services setup.

 

Are you getting an error when you try?

 

FWIW, I am not yet running 10.6.8 on my x86 NAS, but I am able to enable/disable SMB on an RN102.

bubu's avatar
bubu
Aspirant
Oct 02, 2022
No error message
I turn it on but it turn off automatically after few seconds
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    Oct 03, 2022
    bubu wrote:
    No error message
    I turn it on but it turn off automatically after few seconds

    Have you tried downloading the log zip file and looking for errors in there?

    • bubu's avatar
      bubu
      Aspirant
      Oct 03, 2022

      Which log because there are a lot :

      • in system.log
      Oct 03 07:17:01 serveur CRON[16951]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 07:17:01 serveur CRON[16952]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 03 07:17:01 serveur CRON[16951]: pam_unix(cron:session): session closed for user root
Oct 03 07:22:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 07:23:59 serveur ng-csd[6721]: Failed to parse Amazon error response. body: {"message":"Token has expired"}
Oct 03 07:31:30 serveur connmand[3500]: ntp: adjust (slew): -0.000126 sec
Oct 03 07:32:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 07:39:01 serveur CRON[17142]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 07:39:01 serveur CRON[17143]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 03 07:39:01 serveur CRON[17142]: pam_unix(cron:session): session closed for user root
Oct 03 07:42:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 07:48:34 serveur connmand[3500]: ntp: adjust (slew): +0.001058 sec
Oct 03 07:52:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:02:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:05:38 serveur connmand[3500]: ntp: adjust (slew): -0.051464 sec
Oct 03 08:09:01 serveur CRON[17416]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 08:09:01 serveur CRON[17417]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 03 08:09:01 serveur CRON[17416]: pam_unix(cron:session): session closed for user root
Oct 03 08:12:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:17:01 serveur CRON[17529]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 08:17:01 serveur CRON[17530]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 03 08:17:01 serveur CRON[17529]: pam_unix(cron:session): session closed for user root
Oct 03 08:22:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:22:43 serveur connmand[3500]: ntp: adjust (slew): +0.065669 sec
Oct 03 08:24:15 serveur ng-csd[6721]: Failed to parse Amazon error response. body: {"message":"Token has expired"}
Oct 03 08:32:21 serveur clamd[10097]: SelfCheck: Database status OK.
Oct 03 08:35:46 serveur apache_access[4708]: 192.168.111.112 "GET / HTTP/1.1" 302
Oct 03 08:35:46 serveur apache_access[4708]: 192.168.111.112 "GET /admin HTTP/1.1" 401
Oct 03 08:35:52 serveur apache_access[4708]: Admin session started from 192.168.111.112
Oct 03 08:36:12 serveur apache_access[4708]: 192.168.111.112 "GET /ispdb.xml?_dc=1664778972036 HTTP/1.1" 200
Oct 03 08:36:18 serveur wsdd2[17976]: starting.
Oct 03 08:36:19 serveur wsdd2[17976]: cannot read workgroup from testparm
Oct 03 08:36:19 serveur wsdd2[17976]: cannot read netbios name from testparm
Oct 03 08:36:19 serveur wsdd2[17976]: Terminated received.
Oct 03 08:36:19 serveur wsdd2[17976]: terminating.
Oct 03 08:36:39 serveur apache_access[4709]: Suppressed 4 duplicate messages
Oct 03 08:36:39 serveur apache_access[4709]: ::1 "OPTIONS * HTTP/1.0" 200
Oct 03 08:38:20 serveur apache_access[4708]: 192.168.111.112 "POST /dbbroker HTTP/1.1" 401
Oct 03 08:38:55 serveur dbus[3362]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Oct 03 08:38:55 serveur dbus[3362]: [system] Successfully activated service 'org.opensuse.Snapper'
Oct 03 08:38:55 serveur snapperd[18114]: loading 3958 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4043 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4057 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 3950 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4035 failed
Oct 03 08:38:55 serveur snapperd[18114]: loading 4049 failed
      •  in smbstatus.log
      using configfile = /etc/samba/smb.conf
      • in status.log
      [22/10/03 00:00:22 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN AmazonCloudDrive.
[22/10/03 00:00:23 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN AmazonPhotos.
[22/10/03 00:00:25 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Immersion.
[22/10/03 00:00:26 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Photos.
[22/10/03 00:00:27 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Prive.
[22/10/03 00:00:28 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Prophecy.
[22/10/03 00:00:29 CEST] info:snapshot:LOGMSG_SNAPSHOT_CREATE_INFO Snapshot c_1664748020 was successfully created for share or LUN Prophezine.
[22/10/03 00:05:21 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Immersion.
[22/10/03 00:05:40 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Prophecy.
[22/10/03 00:06:40 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Prive.
[22/10/03 00:06:54 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Prophezine.
[22/10/03 00:14:36 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job NAS.
[22/10/03 00:21:28 CEST] notice:backup:LOGMSG_SUCCESS_BACKUP Successfully completed backup job Photos.
[22/10/03 02:20:37 CEST] notice:volume:LOGMSG_DISKTEST_COMPLETED_VOLUME Disk test completed for volume data.
[22/10/03 08:36:18 CEST] info:system:LOGMSG_PROTOCOL_ENABLED Service protocol SMB is enabled.

      but still SMB button not green and can't see NAS in network only access by http

       

       

       

      • StephenB's avatar
        StephenB
        Guru - Experienced User
        Oct 03, 2022
        bubu wrote:

        Which log because there are a lot :

        Normally I'd look in kernel.log, system.log, and systemd-journal.log, and see if there are any SMB related errors or crashes.  dmesg.log also sometimes has useful information.

         

        You are showing some other errors (likely unrelated) with snapshots that might need to be sorted out at some point.

         

        Did this problem happen as soon as you upgraded to 6.10.8?

         

        Have you tried an OS reinstall?

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More