Andrew McMahon

I was having this issue on Windows 10. I'm not sure if this was the actual fix or coincidental, but after clearing the DNS cache (from admin command prompt, "ipconfig /flushdns") and restarting OpenDHCPServer I'm no longer getting the error. Edit: I spoke too soon, the server is running now and assigning IPs but the HTTP interface still doesn't work. 2nd Edit: Eventually got it working. I think the issue is with metrics in the routing table but I could be wrong. I changed HTTPServer to 127.0.0.1...

I was having this issue on Windows 10. I'm not sure if this was the actual fix or coincidental, but after clearing the DNS cache (from admin command prompt, "ipconfig /flushdns") and restarting OpenDHCPServer I'm no longer getting the error. Edit: I spoke too soon, the server is running now and assigning IPs but the HTTP interface still doesn't work.

I was having this issue on Windows 10. I'm not sure if this was the actual fix or coincidental, but after clearing the DNS cache (from admin command prompt, "ipconfig /flushdns") and restarting OpenDHCPServer I'm no longer getting the error.