# Connecting to a remote DICOM server through proxy

**URL:** <https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435>\
**Category:** Support\
**Tags:** dicom, networking\
**Created:** [May 6, 2020, 3:44pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435 "2020-05-06T15:44:06Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![kleingeo](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/kleingeo/32/6772_2.png) [@kleingeo](https://discourse.slicer.org/u/kleingeo)\
**Post date:** [May 6, 2020, 3:44pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/1 "2020-05-06T15:44:06Z")

</div>

With the current state of everything I am working from home. I currently have a DICOM server at work that I require to be able to interface with. I am on Windows 10 and I am currently able to connect to the server through WinSCP, but that requires a proxy jump to work. Is it possible to connect Slicer to the DICOM server, or somehow have DICOM read the folders? At work, I have the server set-up as a Samba network drive and have Slicer read that, but I am unsure how to do this from home. Does anyone have an ideas?

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 6, 2020, 4:43pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/2 "2020-05-06T16:43:01Z")

</div>

I suppose some sort of VPN is the most general solution rather than doing something specific for Slicer. When you say DICOM server at work, so you mean you use DICOM networking (CGET, CFIND, etc) or do you mean it’s a file share with DICOM files?

---

<div class="post-metadata">

**Author:** ![kleingeo](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/kleingeo/32/6772_2.png) [@kleingeo](https://discourse.slicer.org/u/kleingeo)\
**Post date:** [May 6, 2020, 5:45pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/4 "2020-05-06T17:45:43Z")

</div>

Either honestly. It is an othanc dicom server, but I could also just access the raw files.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 6, 2020, 7:10pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/5 "2020-05-06T19:10:49Z")

</div>

I’m not familiar with WinSCP, but it you have access to command-line ssh to the machine in question (via a shell) you could tunnel the dicom port, like what’s [described here](https://www.ssh.com/ssh/tunneling/example). You would need to know the IP and port information.

---

<div class="post-metadata">

**Author:** ![kleingeo](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/kleingeo/32/6772_2.png) [@kleingeo](https://discourse.slicer.org/u/kleingeo)\
**Post date:** [May 6, 2020, 7:44pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/6 "2020-05-06T19:44:36Z")

</div>

I do have cmd line ssh and have most of the proxy stuff saved in a OpenSSH config file. Not sure if that makes it easier or not.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 6, 2020, 8:00pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/7 "2020-05-06T20:00:40Z")

</div>

If you access the pacs via dicom networking then you could do something like:

```auto
ssh ${pacshost} -L 104:localhost:104

```

then configure Slicer to do dicom networking to localhost port 104 instead of `pacshost` 104.

---

<div class="post-metadata">

**Author:** ![kleingeo](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/kleingeo/32/6772_2.png) [@kleingeo](https://discourse.slicer.org/u/kleingeo)\
**Post date:** [May 8, 2020, 2:40am UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/8 "2020-05-08T02:40:55Z")

</div>

I’m not entirely sure how to use that information.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 8, 2020, 12:13pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/9 "2020-05-08T12:13:13Z")

</div>

Fair enough, that’s probably not a good approach for you then.

If you have access to the data via a file system on a remote machine, then you really just need to investigate file sharing options. There are many ways to do this these days and the best solution depends on the details of your setup, but dropbox, google drive, and other off the shelf solutions are options to investigate.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 17, 2021, 1:14pm UTC](https://discourse.slicer.org/t/connecting-to-a-remote-dicom-server-through-proxy/11435/10 "2021-05-17T13:14:53Z")

</div>

You may also ask for DICOMweb enabled on the Orthanc server and use DICOMweb extensions to browse the server and download/upload data. DICOMweb can use various standard authentication methods (password, token, etc).