Host Lookup failed, no DNS entry found?

[rvo_nl]

Hi I am trying to get Genesis setup due to having to re-install everything onto a new hard drive and I keep getting this error whenever ibrowse is trying to load a site and ideas?

For a moment I thought this thread was started by me since the problem you describe is very similar to mine. Not wanting to hijack your thread, I would just like to describe what happens in my situation. It could be useful for you.

For years now I am connecting my Amiga through my pc's internet connection (the pc has 2 network cards) and, after some Windows 10.1 update, I suddenly can no longer forward the DNS entries to my Amiga. I can ping both machines from both sides, but IBrowse keeps giving me that same error as you are describing. I didnt change anything in the configuration.

Again, my set up is a little different, but I am going to keep a close eye on this thread to see how your issue is resolved. To start with I am reinstalling Windows 10 today to see if that makes a difference (before updating).

[rvo_nl]

Thanks, I can confirm that by now. Reinstalling Windows solved the issue with network sharing for me. But then, after running Windows Update, IBrowse can no longer resolve hosts. Ofcourse, I had created a 'System Restore Point' before running Windows Update, so I could easily do a rollback. But it seems Microsoft actually disables System Restore before it installs the problematic update.. :| The patch didnt work either. Sigh.. Will have to wait until someone finds a solution.

[rvo_nl]

For a moment I thought this thread was started by me since the problem you describe is very similar to mine. Not wanting to hijack your thread, I would just like to describe what happens in my situation. It could be useful for you.

For years now I am connecting my Amiga through my pc's internet connection (the pc has 2 network cards) and, after some Windows 10.1 update, I suddenly can no longer forward the DNS entries to my Amiga. I can ping both machines from both sides, but IBrowse keeps giving me that same error as you are describing. I didnt change anything in the configuration.

Again, my set up is a little different, but I am going to keep a close eye on this thread to see how your issue is resolved. To start with I am reinstalling Windows 10 today to see if that makes a difference (before updating).

For anyone encountering this issue, and thanks to the helpful hints by some of you, I was able to solve my own issue simply by doing a Network Reset. This is an option in Windows 10 settings. It seems to resolve the issues caused by the august '16 update.

Now I promise no longer to hijack this thread.

[rvo_nl]

glad you got it sorted! Now I can safely say that my solution only worked until the pc was restarted, then another network reset was needed. Got fed up and bought a new router. Problem solved.