I am trying to set up Open Hardware Monitor's web server and am running into an issue.

I can't access the webpage on any other machines on my local network. I am hoping you all might be able to help me out.


  • Win 8.1 x64
  • Open Hardware Monitor version 0.7.1 Beta (The default download on their site)

Steps Taken:

  • Installed OHM
  • Started web server
  • Set an exception for executable in Windows firewall
  • Set an exception for port in Windows firewall (all types of traffic)
  • I have confirmed the port number I am trying to access it from


  • On the local machine I can view the server at 192.169.xx.xx:port (I am not using
  • On remote machines, attempts to access this address time out.

Any suggestions?

(Edited for clarity regarding IP address with regard to Breakthrough's comment.)

  • Do you have Wireshark installed by any chance? It might be worth running to see if the requests are even getting to the computer, otherwise the issue might lie in your router configuration. – Breakthrough Jun 22 '15 at 4:08
  • I do not, though I am somewhat familiar with it. If you were interested in giving me a quick rundown of the steps required I'd be happy to try it. – Ruthalas Jun 22 '15 at 4:39
  • I haven't used it in a while myself, but this tutorial might help. Wireshark captures the packets your NIC receives. Close all programs except your server, start Wireshark, and try to make a request from another machine. You should see some packets received on the server from the IP address of the computer you made the request from (e.g. pay attention to packets where the Source is the IP address of the computer making the request) - if not, I would start looking into your router configuration. – Breakthrough Jun 22 '15 at 4:43
  • Ok, I think I have done this. I opened wireshark and set the filter to 'ip.addr == xx.xx.xx.xx' (where xx is the IP of the secondary machine). I then tried to access the ip address and port of the server. No traffic appeared wireshark. If I did the filtering right, what should I look for in my router to see if it is blocking that traffic? – Ruthalas Jun 24 '15 at 4:55
  • Try capturing packets without any filtering, and then applying the filter after you've left Wireshark running on the server for a bit and made a few attempts to access the server (or just have a look through the packets yourself, closing any other programs to avoid unnecessary traffic from showing up). If that doesn't yield any results, well, admittedly, I'm not too familiar with networking myself, so I might not be the best help with that aspect; however, I would double-check that you setup your subnet masks properly, and gateway address. – Breakthrough Jun 24 '15 at 5:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.