<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Apr 27, 2015, at 2:33 PM, Hika van den Hoven <<a href="mailto:hikavdh@gmail.com" class="">hikavdh@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The </span><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">long blank page suggests it cannot find the address on the network</span></div></blockquote></div><br class=""><div class="">Not true, it suggests his remote client has found the address and is waiting for a reply. Browsing to <a href="http://IPNumber:12345/" class="">http://IPNumber:12345/</a> or any other unused address or port will come back with an immediate error on the browser side.</div><div class=""><br class=""></div><div class="">The earlier comment about the same problem being observed from two different webservers points the way forward.</div><div class=""><br class=""></div><div class="">- George</div><div class=""><br class=""></div></body></html>