My older PC with Windows 7 worked fine with my wireless airport device using Netgear WINDA3100 wireless stick. My new PC with Windows 10 does not see the airport express at all. I'm using Airport utility 5.6.1. Device manager says the Netgear stick with updated driver is working ok. Unplugging airport to reset it has not helped. Any ideas? Thanks in advance!
AirPort Express 802.11n (1st Gen), Other OS
FWIW, I am running Windows 10 with AirPort Utility v5.6.1 and am not having any issues "seeing" either my 802.11n or 802.11ac base stations in the utility. At this point in time, I am running Windows 10 Pro, version 1607, OS Build: 14393.693. The PC I'm running it on is connected to the network by Ethernet.
The AirPort Utility requires both IPv6 and Bonjour (aka, mDNS) to find the base station before it can appear in the utility. For Windows since Windows 7, Microsoft has make IPv6 Link-local the default address assigned to each of the host's networking interfaces. Bonjour, on the other hand, is not included with the Windows OS as it is an Apple propriety IP protocol. However, Windows does have its own version of Zero Configuration Networking (ZCN), aka, "Plug & Play" ... but the AirPort Utility does not use it directly. One thing to check is to verify that Windows software firewall or any anti-virus program is NOT blocking Bonjour.
Link-local IPv6 address always start with 'fe00.' You can verify that your Win10 computer's network interfaces are assigned these addresses by using either ipconfig, netsh interface ipv6 show address, or route print via the Command Prompt.
Bonjour can be installed in at least three ways (Note: Installing Bonjour does not interfere with Windows native ZCN functionality):
To verify that the AirPort Utility & Bonjour installed properly for Windows 10, there will be two applications listed in the Apps & Features window: 1) AirPort & 2) Bonjour.
Thanks! This was exactly the fix I needed. Took me a minute or two to drill down to the connection preferences, but once I found them and un-checked the IPv6 check and restarted my computer the Airport Utilities automatically popped up a dialogue box saying it had found my TC and asked for the password. Now I can access all of my files on it in File Explorer. You really made my day!
Thanks for your comments, buddy, but I have to admit I have no idea what you mean when you say, "
Note: If running any version of Windows under Parallels to allow the AirPort Utility for Windows to discovery a base station, change the Parallels network setting to a Bridged Network for the virtual machine."
What is "Parallels"? Is that where you've got some 'simulated' version of Mac OS running on Windows? (I'm guessing it doesn't apply to me.....but you got me curious)
What is "Parallels"? Is that where you've got some 'simulated' version of Mac OS running on Windows?
To keep things simple, Imagine having a Mac that can also run Windows. Unless you have this type of setup, things would not apply to you.
Parallels is a Virtual Machine (VM) host application. Another competing product is VMware's Fusion. Either of these applications can support multiple VMs. Each VM is a "computer" in itself running a version of Windows, macOS, Linux, or Google Chrome ... and when any of these VMs are running they perform just like their own separate computer.
For example, I use Parallels and have individual VMs for Windows 7, 8.1, & 10; and multiple versions of OS X going back to OS X Lion. I do so to be able to address questions about AirPort Wi-Fi issues with any of those operating systems without having the need for multiple physical computers.
Thanks for the clarification(s).
I'm starting to think that the real source of MY problem (Airport Express not being seen by EITHER my Macbook or my Win10 laptop) is that I recently updated the firmware on my new(ish) Asus RT-AC66U.
Since doing that, I not only can't see my AE anymore, my 5Ghz network has also disappeared off my "list of available networks". It seems several models of the Asus family of routers have had problems with media, particularly some of this "cross-platform" stuff.
I thought we'd put all this not-playing-nicely-together stuff behind us years ago, but apparently not. (Way to go, Steve; thanks for remaining to be 'special', even from the "other side").
NOTE: I updated the firmware on my Asus router about 2 weeks ago and our Airport Express promptly disappeared from the iTunes taskbar/menubar on her Macbook and could not be detected by Airport Utility on either her Mac OR my Win10 PC.
Just completed doing a "downgrade" to the previous firmware version and, bingo: there's the Airport Express back on iTunes AND discoverable on both computers in Airport Utility.
This may not be the answer to anyone else's situation.........but then again it MAY. Asus routers are getting pretty popular...in spite of the fact that their firmware is know to be buggy in more than just THIS aspect.
That's my $0.02 for the day!
Your problem is likely how you have Windows 10 setup, not with Apple. Here is AirPort Utility on my Win 10 machine. No problems whatsoever with access.
Use ethernet or use an ethernet to wireless bridge. Don't use wireless.
And do the setup on iOS or Mac not a PC.
Windows 10 device drivers can show they are working and be absolutely a total failure.. you do know that??
Also windows X is having issues with apple routers as a whole.
Do a search for win10 and apple routers.. in this lengthy post Apple said they are aware of incompatibility.
dhinfo12, you are the 4th Windows 10 user with problems I've seen here in the past week alone. The problems vary and I am curious what your experiences are, as follows:
In my case, AirPort Utility running on Win 10 is unable to detect and render a graphical display of my network devices. At least reliably, i.e., sometimes it works, sometimes it doesn't. How about you?
Others report not being able to see their Time Capsule (TC) at all as a network device within This PC. You?
Othere report being able to see their TC, can Read from it, but not Write to it. And again, you?
Knowing more about your experience helps to understand the scope of these Windows 10 issues.
Apple has not updated the AirPort Utility software for Windows in over 3 years. The current (and latest version) of AirPort Utility for Windows officially supports Windows 7.....and nothing higher.
If Apple has not bothered to update the Windows software in any way in well over 3 years, my opinion would be that they are not ever going to do this. But, I could be wrong.
The only way that you will know for sure is to contact Apple Support directly and ask them about this.
I have not had positive things to say about Windows since XP. But with this new release of Windows 10, I have to say I am impressed.
Microsoft has gone the extra mile to play with iOS and OS X. For instance, automagically during the upgrade process Win 10 detected, downloaded, and synced my Apple Calendars and Contacts with it's Window's counterparts. And now keeps them in sync. I had iTunes installed on Win 7 before the upgrade...that's all 10 needed. Nice!
Apple should take heed.
Older TC have problems with IPv6.
the easiest way to get your Windows 10 machine to see your TC or Airport Express is to disable IPv6 on windows. You do this by going to: Control Panel -> Netowork and Internet -> Network Connections
Then right click on whatever network adapter you are using to connect to your Airport Network of devices, and click on properties. This will bring up a menu of configuration options for that adapter. Just uncheck the checkmark next to Internet Protocol Version 6 (TCP/IPv6). Hit OK, reboot your machine, and run your airport utility. You should see your TC and ape devices.
(note, if you need tcp/ipv6, then you'll need to do some more research into the 'type' of tcp/ipv6 network you need to run. Note, you may also have to go into your airport router and make sure you don't have any ipv6 servers or domain names specified. Also, your airport devices need to have their ipv6 mode set to Link-local only)
Hope this helps...
if you need tcp/ipv6, then you'll need to do some more research into the 'type' of tcp/ipv6 network you need to run.
Generally it is not a good idea to turn off IPv6 now.. Windows needs it for home group.
And all you really need is to set to link-local only. That is sufficient.
Well, it's a pain in the @$$ but you can select FILE | CONFIGURE OTHER... from the menu in the AirPort Utility and then enter the IP and password for your router. That still works.
I am having the same issue with Win 10 and the AirPort Utility. My AirPort Extreme network is no longer discovered/visible in the left hand pane of the utility. This is an "always" thing too...not a "sometimes" thing as others have reported. I do not have a TC.
I tried disabling IPv6 on my network adapter...no change. Exited HomeGroup, no change. In short none of the solutions have worked. It's just kaput!
Regards,
Windows 10 with aiport utility v 5.6.1 doesn'see my device, Win 7 was ok
