Announcement

Collapse
No announcement yet.

SMB 3.x

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SMB 3.x

    Hi,


    Our production Mirth instance is unfortunately still on v.3.4. We are trying to connect to a SMB share, using credentials, with a File Write destination and it is failing. Our of curiosity, I went to our DEV Mirth box, which is on version 3.10 and has SMB 3.x capabilities and I was able to connect without issues. It looks like Mirth v.3.4 doesn't support this newer SMB standard.

    I do not think they are ready to upgrade our production Mirth instance at this time, but is there anyway to use Java/Javascript to move the files to the SMB share using authentication and most importantly SMB v.3.x?

    If not, I will make the push to have them try and update Mirth sooner rather than later.


  • #2
    Why not mount the file system local to the server? I never use the SMB reader/writer, rather let the operating system do what it always has done... mount file systems.

    In Linux that is trivial, in windows more of a pain (when logged out), but possible also.
    Diridium Technologies, Inc.
    https://diridium.com

    Comment


    • #3
      Hi,

      I was able to mount the SMB share on my Windows 2012 server box, but I am having trouble accessing it with a Mirth File Writer as a file or SMB share? Is there something special I have to do?

      I have it mounted to my z:/ and it has one folder I am trying to write to, which is 'Test'

      Comment


      • #4
        That is one of three things:
        1. Share permission
        2. File permission (that is different than bullet 1)
        3. The user that the mirth server process runs as does not have appropriate permissions.
        Diridium Technologies, Inc.
        https://diridium.com

        Comment


        • #5
          Windows mapped drives are per user. Each user can have a different Z: drive.

          When I do this on Windows, I call the NET USE command from the deploy script in mirth so that user running the mirth service is the one mapping the drive.

          Comment


          • #6
            Thanks for the info. I was able to mount the drive successfully using the replies here. Was a good solution, but I ended up updating Mirth and I am now able to use SMB3 via the normal Destination connector . Does anyone know how Mirth is accomplishing this if JCIFS doesnt support SMB 3. Unless they are not using JCIFS anymore?

            Comment


            • #7
              According to this issue, they are now using jcifs-ng

              https://github.com/nextgenhealthcare...ment-626973540

              https://github.com/AgNO3/jcifs-ng

              Comment

              Working...
              X