Orthanc for Windows - requires SMB / CIFS 1.0?

[wardy...@hotmail.com]

hi,

We are setting up an Orthanc test server. We could not get the Ultra Sound Scanner to send DICOM images to the Orthanc server until we turned on CIFS / SMB 1.0 (this is on a Windows 2019 Server).

Is CIFS / SMB 1.0 a requirement of Orthanc on Windows Server? This is a very old, insecure portocol. We'd really like to use Orthanc, but our Security team will not allow the use of CIFS / SMB 1.0.

Thank you in advance for your help with this.

Regards,

Adam

[James Manners]

Hi Adam,

No SMB 1.0 is not a requirement of Orthanc.  It may be required depending on the configuration of your Ultra Sound. We do work with some diagnostic machines that require SMBv1in order to map a network drive. In this case, the device is typically saving exports to the shared network drive rather than transmitting over DICOM.

However, in order for Orthanc to receive scans from your Ultra Sound, you will need to configure the US to send via DICOM to your Orthanc server.  We have several GE US machines sending to Orthanc.

Hope that helps.

Cheers,

James

[wardy...@hotmail.com]

hi,

OK thanks - thats interesting, and strange. The Ultrasound scanner we were using is a SonoScape X5 (from 2014). We cannot see anywhere that it requires SMB 1.0 to send DICOM images, but as I say, on Windows 2019 Server the machine will not send data to the server unless we turn on SMB / CIFS 1.0

Has anyone else experienced this and know how I can get DICOM images to transfer without turning on SMB / CIFS 1.0?

Regards,

Adam

[wardy...@hotmail.com]

I should add we ARE sending images via DICOM. I've setup "Storage" as the DICOM method. We would really much rather use Windows than Linux (due to the support we have and that we're a Windows house).

Is there anyone within Orthanc I can approach to assist with this?

Regards,

Adam

[jtwei...@gmail.com]

What you are experiencing likely is more a windows thing than an orthanc thing.  Some things to try.

If your ultrasound has a windows username and password that you can find in the setup, or even better set to your own taste, then on the server, create an account in that username with that password.

Depending on the version of windows or linux underlying your ultrasound, on the server you will most likely have to explicitly turn on file and printer sharing,  probably set to password protected sharing, and make sure that you explicitly share the folder where the database and orthanc stuff lives specifically with your ultrasound's user/pw combo.  You may even need to share the base drive C: or D:  (sometimes it will let you sometimes not)  Safer to stay more specific for the folder you want to hit.

I have had various combinations of windows machines (10, 19server, 7) that will not allow logins and traffic with password protected sharing off.   Password protected on with explicit permission for the calling machine seems to get me there.

Finally I have had to on occasion specifically allow a machine and or a program through my server windows firewall..  So trying all the steps first with the firewall down is good to try.. then bring the firewall up, and if you are blocked again, you need to set some explicit permissions there as well.   

Also on your ultrasound make sure that you are finding the server by number.. ie 192.168.1.xxx rather than by name ie  \\myserver 

In other words skip the name resolution step..   The different flavors of windows networking have different schemes for name resolution, and your ultrasound may be attempting name resolution with nothing on the network doing that in the flavor it needs until you turn on smb1.   Smb1 used a "master browser election"  where the machines all "voted" as to who handled local name resolution.  That is gone in the newer version..  If your ultrasound is seeking the master browser, then direct address may be the answer. 

So many possible points of failure.. thank you mr Gates..

John

[wardy...@hotmail.com]

hi,

Thanks for this - will give the suggestions a try. On the DICOM settings on the Ultrasound - We're setting the Orthanc Server by IP address and port number. We can Ping the server and verify on the advertised port 4242 succeeds too. We've only setup the DICOM "Storage" option on the Ultrasound Scanner. With CIFS / SMB 1.0 off Orthanc doesn't receive anything from the Ultrasound Scanner (no data - nothing in the logs). As soon as we turn ON CIFS / SMB 1.0 Orthanc is able to recieve the Ultrasound DICOM images.

File and Print sharing is turned ON, the Server firewall is turned OFF and I've installed the "File Server" role in Windows.

Its difficult to test as I have to go to a live environment where the Ultrasound scanner is in use and take over it whilst we try and make it talk to the server without needing CIFS / SMB 1.0 - so troubleshooting is time consuming and difficult to arrange without impacting live services.

I'll try and go again next week now I've turned on these additional services - but anything else I could try would be really helpful as I can create a list of things and do it all in one visit!

Regards,

Adam

[Alain Mazy]

Hi Adam,

To detect if it's an Orthanc issue or an US issue, just upload a file in Orthanc through the web interface.  If Orthanc can store this file, there's no reason why it would not store a file received through DICOM protocol.

Note that, Orthanc, in no way, requires SMB or CIFS to store files; Orthanc just needs a file system.  If it can not store the file uploaded through the web interface, then it probably means it's a permission issue or whatever (never ran a Windows Server by myself).

HTH

Alain.

--
You received this message because you are subscribed to the Google Groups "Orthanc Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orthanc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orthanc-users/fed54f1c-329b-4a7c-be68-e9f6aaf49cc4n%40googlegroups.com.