Host Lookup failed, no DNS entry found?

[carvedeye]

As long as you cannot even find "ping" in the path on your Amiga, don't spend any money.

Well I have managed to get ping to work in the shell but it only sends 1 packet and then the shell just sits there and doesn't send anymore?

[carvedeye]

Is there a way to get a USB Wireless N adaptor to work with my Amiga?

[duga]

First get it to work via cable before starting playing with wifi on your Amiga.

[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.

[carvedeye]

Well I have finally got my Amiga online, I have did a fresh install on a formatted HDD and I have installed a fresh copy of AmigaOS 3.9 and have installed everything I originally had on it other than Boing bags 3 & 4. Genesis works fine and iBrowse works a treat . I had a feeling it was the Boing bags 3 & 4 but at least I now know what the issue was.

Thanks for all the help guys I really appreciate it.

[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.