The Op should disable the Juniper Virtual adaptor by going into Device Manager and disable it, as a secondary network interface can sometimes confuse Windows on which connection is supposed to be the active one.
I would definitely go into the IPv4 properties of the wireless connection and type in two usable DNS servers like Google's DNS > 8.8.8.8 and 8.8.4.4
The IP shown for the wired connection is what you get where there is no internet "Auto Configuration".
Thanks chev,
This leads me back to believing the HG8247 ONT needs refreshing. After you sort through the changes made in attempt to fix the issue - everything else looks fairly straight forward.
jmhc33 is reluctant to reset it - thinks it might serve other residents, would check with the landlady.
Suggest OP follows your advice and try connecting at a public hotspot. If successful, it's more than likely the ONT or ISP.
Static IP for DNS is a good suggestion.
jmhc33,
Try giving your ethernet controller a hard coded address.
Go to Control Panel -> Device Manager
Dbl click on your etherent controller to open properties
Go to the Advanced tab
Select Network Address
try the following values one at a time. since it's hardware you might have to restart the machine, but try just changing the address.
004854537D1D
00E04C537D1D
525405537D1D
I'm still looking for a wireless fix.
Please update where the issue stands and post a current ipconfig /all - thanks
It was quite a chore, but Wireless on my machine is working again. Still using the hardcoded workaround for ehternet.
What didn't work for me:
unticking IPv6 on the controller
netsh int ip reset %userprofile%\downloads\Rest_ip.txt
netsh int ipv4 reset %userprofile%\downloads\Rest_ipv4.txt
netsh int ipv6 reset %userprofile%\downloads\Rest_ipv6.txt
netsh winsock reset
You might want to try the above (run netsh commands in an elevated command prompt ...right click - run as administrator)
Stopped and disabled IP Helper service
What finally "solved" my issue was uninstalling the wireless adapter in device manager, removing software as well. Finding an updated driver (neither Windows or HP made this easy), selected the best match from HP (Atheros 5007, x64) and installing it. third time was the charm - that's when i realized the install package used the incorrect inf file (x86 intstead of x64).
anyway, check your dirver version, if you recently updated, try rolling it back. Otherwise try updating the driver.
Something i should have asked: were there any upates to your machine that might have caused this problem? you originally said that connectivity and then stopped working.
One last note: in post# 6, the subnet mask reads
255.255.0.0 - I don't think your running a class B network
255.255.255.0 - correct mask for a class C network.
Quote