#QUALCOMM ATHEROS AR8161 8165 DRIVER DRIVERS#
#QUALCOMM ATHEROS AR8161 8165 DRIVER BLUETOOTH#
#QUALCOMM ATHEROS AR8161 8165 DRIVER WINDOWS#

If that takes care of it (meaning you get failure connecting to the storage2 hostname because it doesn't exist), you're ok if you want to test turning back on any desired features in the router, one at a time to see if you start having problems again. Reboot everything after saving all that stuff. Set the DHCP configuration of the router to give out 1.1.1.1 and 1.0.0.1 for DNS servers to your LAN devices. You should first make sure the router is updated with the latest firmware, they might have already fixed this nonsense.Īfter that, disable any 'safe search' stuff in the router and other weird proprietary features. The is probably coming from the DHCP configuration of your router, I would guess it is some kind of default thing they do. I do have IPv6 disabled as some devices (cameras and such) get dorked up with it enabled. I even looked through computer management and showed hidden devices. Stopped the ISATAP service, so now all I have is:

#QUALCOMM ATHEROS AR8161 8165 DRIVER DRIVERS#

I did all I can think of (including google which said dual dns/dhcp could dork it up in this manner) and got to the point ofĭeleting the adapter and drivers and reinstalling.

#QUALCOMM ATHEROS AR8161 8165 DRIVER BLUETOOTH#

: EnabledĮthernet adapter Bluetooth Network Connection 2:

: Tuesday, Decem3:56:29 PMĭefault Gateway. : Qualcomm Atheros AR8161/8165 PCI-E Gigabi Packets: Sent = 1, Received = 0, Lost = 1 (100% loss), Only reason I noticed was my mapped drive to the storage2 machine stopped working.ĭual boot if that was not clear, sorry. It would also be helpful to include the info from the Win 10 box as well.įor the record, it's very easy to fat-finger as Also give us the same info from whatever box you're trying to access that works from Win 10. Make sure to include any search suffixes, DHCP servers, DNS servers, local IP(s), netmasks, etc. Also give us an ipconfig/all from that box. You'll need to be more specific.įrom a command prompt on the Win7 box, try to ping whatever it is you're trying to ping. Either a hosts file, a DNS or other name resolution service, a physical/virtual host, or something like that. The entire 198 block is public, so *something* is resolving to a public address.which means something elsewhere is misconfigured. 192 address for storage2 or 3 goes to wrong address.įocus on the Win7 box, and understand Win10 has improvements. Long, lovely Turkey day and I'm gonna do the simple thing first.or just use one of my lappys to set up the new Thanks for the assist figured the hive would have a suggestion on a fix and got a workaround and alternative. 10 to 20, printers were 30 to 40 and scanners were not networked, so no worries.īut my humble home just has two lappies, 3 desktops, a Ring and a buncha LIFX bulbs.Īnd, it seems my desktop is the only machine being stupid when in Win7. Heh, yes they have and I have to admit when I did the static DHCP assignments.life was awesome with name/IP did not matterĪnd I actually did as you said. So you can be on any site and know that the printer is at x.x.x.5 without having to know the name or anything else about it (if you're trying to hit the printer's built-in web server).

#QUALCOMM ATHEROS AR8161 8165 DRIVER WINDOWS#

Using windows machines names has been broken since it was invented, and the easy, stable solution is to simply ditch these names and start using the IP.Īnd if you get smart with assigning IPs, you will always assign x.x.x.5 as a printer or x.x.x.10 as a scanner, etc across your network and multiple networks if you deal with those.

Going to do the dual boot e if that helps.įrennzy and Paladin have nailed this.

Some additional poking around: no double NAT, only 3 machines on right now.same issue. Unless there is a setting to change on the router or machines, is it 'Factory Reset' time? Week period and during a time of updating all the Win7/10 machines, Steam and Uplay. Strange that internet works w/o issue and this came about in a time frame that had a couple router reboots in a two Rebooted router, unplugged switch, played with DHCP and used the router's. Ping it, and it says it is looking for 198., no, no, no. Fired up Fing on the phone and it is at 192.168.0.108. I turn around and it is on, plugged in and humming along. Mapped drive letter and it could not be found. Ok, somewhere along the way things went pear shaped and I can't get to network resources via UNC paths.ĭon't recall doing anything during that time and just noticed when I tried to get to my Synology Diskstation's

Qualcomm atheros ar8161 8165 driver