Posts by RodrickW2

That's good to know also. I can set things up the way I want with port XXXX and then edit the dicom.ini file to 50089 and then restart. Cool.

RW

Windows XP Service Pack 2
Conquest DICOM Server 1412c
Administrator rights

Ports up to 9999 NO PROBLEM

Port 10000 and presumably above. Server fails to start on Windows.

This is likely a known limit because the Windows GUI won't let you enter a port higher than 9999. It is useful to know that it works under LINUX because in the end, that will be our target for deployment.

My need to use port 50089 will go away if I can persuade the powers that be to change things to a lower port. They won't consider any PACS changes until after their summer vacations.

Thanks for your input.

RW

There are no limitations with the port that you can forward to. This problem only occurs when the Conquest Server ITSELF is assigned to port 50089 by manually editing DICOM.INI

RW

I need to replace a node on our network with the CONQUEST Server. One of our annoying vendors requires that a service engineer change DICOM nodes, so instead we will replace the machine at that node with a CONQUEST DICOM Server.

I've run into a problem though. The node is on port number 50089. It seems that CONQUEST crashes with ports set higher than 9999.

Is there a work around? I don't mind recompiling the software, I am just not sure where in the code that limitation creeps in.

R Williams, MD