Jump to content
SNS Users' Forums
  • Announcements

    • Eric Newbauer

      Forum closed   06/30/2018

      PLEASE NOTE: This forum is closed and no longer moderated. Please visit https://www.studionetworksolutions.com/support/ for assistance with your SNS products. Follow Studio Network Solutions on Twitter. Thank you!

SNS Hal

Members
  • Content count

    182
  • Joined

  • Last visited

Posts posted by SNS Hal


  1. It sounds like this Windows machine may be using an older authentication method (NTLM, rather than NTLMv2).

    To change this, click the Windows button and type secpol.msc to access the Local Security Policy settings.

    Navigate to Local Policies > Security Options > Network security: LAN Manager authentication level

    Choose Send NTLMv2 response only from the drop-down menu, and click Apply.

    If that doesn't help, feel free to open a support case, and we can take a closer look at this.


  2. Hi Jeffrey,

    Either ShareBrowser or Finder can be used to eject volumes. The best practice is to unlock the project locks from within the ShareBrowser Client or Finder before ejecting, but if all NAS shares are unmounted, the locks should also eventually expire on their own (once the EVO has determined the NAS sessions truly are closed and not just briefly interrupted).


  3. Thanks for asking. While it’s technically better to shut down workstations from a security (see this article) and energy-saving standpoint, leaving the machines running indefinitely is not expected to pose a problem with the EVO. It is best to unmount network shares when not in use (especially if using SAN volumes). Also, here’s an article that covers the best practice for EVO shutdowns. Feel free to open a support case if you have any more questions or concerns!


  4. Hello,

    The initiator is strictly a connection mechanism, with no concept of the file system. The workstation operating system handles all file operations, but it does need reliable communication with the target disk. From what we've seen, the initiator maintains the connection to the storage without issue, but as noted in a previous reply, the storage system doesn't seem to support the error detection policy that is set by default in globalSAN, so this protective policy gets disabled. Error 36 is often indicative of trouble with the file system. If you're still able to read from the disk(s), backing up the data (and maintaining current backups) would be a good first step.

    Most storage systems (including our own!) do include the error detection policy as added protection for block level communication.

×