diff --git a/source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown b/source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown
index ca7c643..002cdb3 100644
--- a/source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown
+++ b/source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown
@@ -18,7 +18,11 @@ $ ln -s /bin/bash ~/.local/bin/sh
 ```
 
 Thanks to ole2 for providing this solution in the xilinx forum, which you can find here:
-[forum post](https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2013-2-Launching-jobs-on-a-remote-host)
+[forum post](https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2013-2-Launching-jobs-on-a-remote-host/td-p/396861)
+
+As he points out, this seem to be a bug in Vivado. Vivado seems to call a script with #!/bin/sh and expects a bash to be executed. But for Ubuntu, /bin/sh points to /bin/dash per default. An alternative solution is to re-configure this link using:
+```bash
+$ sudo dpkg-reconfigure dash 
+```
 
-As he points out, this seem to be a bug in Vivado.
 I had this issue in Vivado 2016.4 and Ubuntu 16.04 LTS.