Failed to establish association

[Anonimniy Anonim]

Hello. I switched my VPN server from L2TP to OpenVPN. Now, after connecting, I get the following error when trying to download the research. What could it be? The only thing that has changed is the IP addressing. I updated the orthanc.json file to reflect the new IP addresses.

W0325 14:17:57.787523 OrthancMoveRequestHandler.cpp:289] Move-SCU request received for AET "ITPC"
E0325 14:18:07.891766 OrthancException.h:85] Error in the network protocol: DicomUserConnection - connecting to AET "ITPC": Failed to establish association (0006>
E0325 14:18:07.891918 MoveScp.cpp:237] IMoveRequestHandler Failed: Error in the network protocol

[Stephen Douglas Scotti]

Just for a follow up.

The problem was apparently related to 'NAT masquerading'. Deactivating that fixed the connectivity problem.

For reference, these also useful just generally for troubleshooting: https://book.orthanc-server.com/faq/dicom.html

and these:

  // Whether Orthanc checks the IP/hostname address of the remote
  // modality initiating a DICOM connection (as listed in the
  // "DicomModalities" option above). If this option is set to
  // "false", Orthanc only checks the AET of the remote modality.
  "DicomCheckModalityHost" : false,

  // Check whether the called AET corresponds to the AET of Orthanc
  // during an incoming DICOM SCU request
  "DicomCheckCalledAet" : false,

You probably don't want to do that, but it helps for debugging.    There is a long form for modality configuration also:

//"untrusted" : {
    //  "AET" : "ORTHANC",
    //  "Port" : 104,
    //  "Host" : "127.0.0.1",
    //  "Manufacturer" : "Generic",
    //  "AllowEcho" : false,
    //  "AllowFind" : false,
    //  "AllowFindWorklist" : false,       // new in 1.10.0
    //  "AllowGet"  : false,
    //  "AllowMove" : false,
    //  "AllowStore" : true,
    //  "AllowStorageCommitment" : false,  // new in 1.6.0
    //  "AllowTranscoding" : true,         // new in 1.7.0
    //  "UseDicomTls" : false              // new in 1.9.0
    //  "LocalAet" : "HELLO"               // new in 1.9.0
    //  "Timeout" : 60                     // new in 1.9.1
    //}
  },

Stephen D. Scotti, MD

[Anonimniy Anonim]

here is my network diagram. I am pinging the client from the server and both ways.

воскресенье, 26 марта 2023 г. в 13:31:03 UTC+3, Stephen Douglas Scotti:

[Anonimniy Anonim]

I turn on the nat masquerade and it worked great. Everything is downloading.
Now I can't understand. If my nat works, then the request to orthanc server does not come from vpn ip 10.20.30.11, but from ip 192.168.51.253.
In this case, in the list of dicommodalities, should I specify the ip address 192.168.51.253 of the client?

понедельник, 27 марта 2023 г. в 14:25:03 UTC+3, Anonimniy Anonim:

[Phil Smith]

You really should look at a Zero Trust SDP like NVIS. It works great with DICOM. check out https://nvis.cc .

--
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/9d3346aa-8ca9-4bc0-bac7-a724cf898b3bn%40googlegroups.com.