Can't be said enough - great work gentlemen. Thank you.
I recently migrated to new hardware and upgraded to v1.4.14. I simply copied the acrnema.map files from the original servers - three instanances of Conquest - to the new system. This week we installed four new workstations in the department and included the Conquest servers in their node list. Strangely, I am able to query/retrieve data from the Conquest servers even though I have not added these nodes to Conquest acrnemap.map lists. The install team tested query/retrieve before I had a change to add the new nodes to the lists. I have not used wildcards in the acrnema.map lists. This was very unexpected.
Has anyone else witnessed this? Conquest operating in promiscuous mode?
Thanks, Scott
Able to retrieve from nodes not in acrnema.map
-
-
Hi,
conquest indeed always operates in promiscuous mode. You can always query, but obviously not retrieve if you are not known in acrnema.map. You can restrict access using dgatesop.lst if you want.
Marcel
-
Actually, I AM able to retrieve (Conquest is performing a C-Move) without the nodes being in acrnema.map lists.
Thanks,
Scott -
Hi,
I believe the code checks if the move destination is known as hostname. It may be that code that is working.
Marcek
-
Hello,
I don't use hostnames in my acrnema.map files. Here is one of mine:CONQUESTNM 10.101.8.48 5678 un
CONQUESTNC 10.101.8.48 5679 un
CONQUESTQC 10.101.8.48 5680 un
ESOFTNMPR1 10.101.8.42 104 un
ESOFTNMPR2 10.101.8.40 104 un
ESOFTNMPR3 10.101.8.49 104 un
ESOFTNMP 10.101.8.41 104 un
ESOFTPET 10.101.8.54 104 un
ESOFTDEMO 10.101.8.13 104 un
PHYSICS 10.101.8.50 104 un
NCRESEARCH 10.101.8.52 5680 un
ESOFT551 10.101.8.55 104 un
GEPACS 10.7.222.47 4100 un
KPACS15 10.101.8.15 5678 un
NUCMEDPC1 10.101.8.15 104 un
LEONMPR1 10.101.8.66 104 un
LEONMPR2 10.101.8.67 104 un
PETCTACQ 10.101.8.64 104 un
PETCTPROC 10.101.8.65 104 un
ICONP 10.101.8.44 104 un
CONQUESTNMB 10.101.8.59 5678 unHere is an example from the status.log of a C-Move to a node not in the acrnema.map list....
[CONQUESTNM] UPACS THREAD 177: STARTED AT: Fri Dec 19 15:14:16 2008
[CONQUESTNM] Calling Application Title : "TURBONMPR1 "
[CONQUESTNM] Called Application Title : "CONQUESTNM "
[CONQUESTNM] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 32768
[CONQUESTNM] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.2" 1
[CONQUESTNM] C-Move Destination: "TURBONMPR1"
[CONQUESTNM] Number of Images to send: 3
[CONQUESTNM] C-Move (StudyRoot)
[CONQUESTNM] UPACS THREAD 175: ENDED AT: Fri Dec 19 15:14:16 2008
[CONQUESTNM] UPACS THREAD 175: TOTAL RUNNING TIME: 225 SECONDS
[CONQUESTNM] Sending file : F:\conquestnmdcm\0102647537\1.3.12.2.1107.5.6.1.5516.30340108120913342173400000005\1.3.12.2.1107.5.6.1.5516.30340108120916475410900000003\1.3.12.2.1107.5.6.1.5516.30340108120916475410900000005.dcm
[CONQUESTNM] Sending file : F:\conquestnmdcm\0102647537\1.3.12.2.1107.5.6.1.5516.30340108120913342173400000005\1.3.12.2.1107.5.6.1.5516.30340108120916475410900000009\1.3.12.2.1107.5.6.1.5516.30340108120916475410900000011.dcm
[CONQUESTNM] Sending file : F:\conquestnmdcm\0102647537\1.3.12.2.1107.5.6.1.5516.30340108120913342173400000005\1.3.12.2.1107.5.6.1.5516.30340108120916475410900000015\1.3.12.2.1107.5.6.1.5516.30340108120916475410900000017.dcm
[CONQUESTNM] C-Move (StudyRoot)
[CONQUESTNM] UPACS THREAD 177: ENDED AT: Fri Dec 19 15:14:17 2008
[CONQUESTNM] UPACS THREAD 177: TOTAL RUNNING TIME: 1 SECONDSDo you mean, if the hostname of the destination is known to the windows system hosting a conquest server (i.e. in the hosts table) then any AE_Title on that system is a "valid" C-Move destination? Can I disable this? This would seem to indicate that any system that uses the same windows workgroup could retrieve data from the conquest server - correct?
-
Hi,
you can edit dgatesop.lst as follows (example):
This would allow ALLOWEDAE1 and ALLOWEDAE2 to access conquest, and only if they address is as CONQUESTSRV1. All other servers would be locked out as called and calling AE. There is, however, no way to lock out C-MOVE destinations at present. So a trusted server can move data to any AE or hostname. I will by default disable the hostname feature for the upcoming release. It was already present in the original UCDavis code.Note that It is important to also add the server itself as RemoteAE and LocalAE: otherwise the GUI can no longer control aspects of the server.
Marcel
-
Marcek,
Looks like I have been using Conquest (for years now) under a few false assumptions regarding the acrnema.map list. I have allows pictured that the acrnema.map list controlled which nodes could receive data from a Conquest server via a C-Move request. I assumed that Conquest answered any query request (promiscuous mode) but would not "honor" a request for a C-Move operation if the node was not in the acrnema.map list. I think the header of acrnema.map ("Known DICOM providers" tab) is mis-leading in this regard.I was suprised (embarrassed) that I did not understand this aspect of the server. I'm guessing this has not been raised as an issue before now. I guess I'm feeling a little awkward about you changing the code (doing more work) because of my ignorance.
Best regards,
Scott -
Hi Guys!
I'm not sure i'm in same page. Here what I'm try is.
I comment out one viewer station AE Tile from CONQUEST "Known DICOM provider" and save it.
Then I try to retrive images from CONQUEST on that viewer station I got following message, -
Hi,
conquest can be queried by anyone, unless you specify allowed AE's in dgatesop.lst.
conquest will move to any AE in acrnema.map, but if that is not found it will also try to move to a windows hostname. As long as AE and hostnames are different, you expect the listed error.
By the way: finding problems and oversights in the code is what this forum is all about: thanks for your input!
Marcel
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!