Airport Extreme reserves ip but ping fails

Great job posting all the details.

(4) I am not running any security software that would block ping. In fact, with my current Optimum router (which I am trying to replace with the AEX) I can ping all machines from any other machine.

This is the key bit of info. I presume you deliberately moved the IP of the Airport Extreme to match Optimum router.

That may not be a great idea. The airport is definitely happier on its default.

I think the problem is a mix of domain issues.. and DNS.

In the airport Extreme.. I want you to swap the DNS values.

So open the edit in the airport utility.. go to the Extreme's Internet tab and set the DNS values manually.

The first DNS server should be the Airport Extreme itself. As per the screenshot below.

The second DNS server should be your first verizon DNS.. 68.237.161.12 (my screenshot shows my own).

If you are not using IPv6 then change the configure IPv6 to link-local only in the Internet options.

Save that and apply it.

Shut down all the clients after you change the values and restart them all. You should include the Time Capsule and switch in that as well. Every device on the network should be restarted. That is to force the DNS change in all the clients.. but I would also like you to check that the clients have actually changed.

First ping check then if the computer is able to ping the router .. ie 192.168.1.1

Then ping it by name, which is going to change to airport_extreme (the name with the space is not a valid name.. your TC name is also much too long and apostrophe is not legal character.. apple changes it.. but it is much better to use short names, no spaces and pure alphanumerics).

If the ping to the router fails by name try it with domain.. ie ping airport_extreme.verizon.net and if that doesn't work try airport_extreme.local

Once we determine why it cannot ping by IP which should always work.. and I think is due to no local DNS.. then you need to fix the domain.

Post back and I will attempt to replicate any issues if it still fails.

I am in Australia.. so our Time difference can be a pain.

What type of broadband service do you have? Are you on cable with a pure modem or some fiber service or VDSL etc.??

I am starting to remember why I bailed out of windows and switched to Mac.

When you setup the network in the win10 computer did you select public or private.. I am not up to date with windows latest vexacious issues. But windows will allow home network using ipv6 (home group). And I think it now defaults to public for IPv4. Since all the latest security scares prove windows still is very poor.

Go into your windows control panel, Network and Sharing Centre/ Advanced sharing settings.

Make sure your current profile is Private

NOT Guest or PUBLIC.

Under private make sure you have checked.

Turn on network discovery.

Turn on file and print sharing (this is important to get two way connections)

Allow Windows to manage homegroup connections.

I have done a partial network rearrange.

I have windows computer on same IP range but different router to the Mac.

I can ping from windows to Mac but not visa versa..

I switched the Mac over the same router as the PC. (both on Asus not apple)

Now I can ping the PC although the ping shows this is not a great connection.

ping 192.168.2.133

PING 192.168.2.133 (192.168.2.133): 56 data bytes

64 bytes from 192.168.2.133: icmp_seq=0 ttl=128 time=53.290 ms

64 bytes from 192.168.2.133: icmp_seq=1 ttl=128 time=3.537 ms

64 bytes from 192.168.2.133: icmp_seq=2 ttl=128 time=92.313 ms

64 bytes from 192.168.2.133: icmp_seq=3 ttl=128 time=116.229 ms

64 bytes from 192.168.2.133: icmp_seq=4 ttl=128 time=341.240 ms

64 bytes from 192.168.2.133: icmp_seq=5 ttl=128 time=2.149 ms

64 bytes from 192.168.2.133: icmp_seq=6 ttl=128 time=178.386 ms

64 bytes from 192.168.2.133: icmp_seq=7 ttl=128 time=711.911 ms

64 bytes from 192.168.2.133: icmp_seq=8 ttl=128 time=2.134 ms

64 bytes from 192.168.2.133: icmp_seq=9 ttl=128 time=243.492 ms

Would adding a translation from the v4 to the v6 style addresses in this file help?

No I think you have some setting wrong.. and you need to fix it.

I plugged the windows PC in via ethernet with wireless off.. and now the ping looks much better.

Mac is still on wireless..

ping 192.168.2.207

PING 192.168.2.207 (192.168.2.207): 56 data bytes

64 bytes from 192.168.2.207: icmp_seq=0 ttl=128 time=7.036 ms

Ok.. so Verizon has you on fiber connection or some such??

That is not a major issue.. as long as I know you have ethernet from a black box which does connection to internet.

The rule here is to simplify.

This might be a nuisance but you will get nowhere easily now without doing a major reconfig of the network to its simplest and see how you go.

So

WAN connection on AE to blackbox.

Two windows computers.. plugged by ethernet into the AE LAN ports.

No other connections. You will of course be using ipad via wireless to configure the AE.. that is fine.

Reset the AE to factory. (unplug or shutdown power.. hold in reset button and power up the AE again.. holding in reset the whole time.. and keep holding in another 10sec.. you should see the front LED flash rapidly).

Reconfigure the AE from your iPad. DO NOT USE APPLE RECOMMENDED NAMES. change it to AEgen6 for both base station name and wifi. Change nothing outside of the setup wizard.

Boot the two windows computers.. now attempt to ping from one to the other by name and IP address.

If by name fails try it with the full domain.. as you did previously.. both verizon.net and local but this time lets add in WORKGROUP (in caps).

No luck change the first DNS again to match the IP of the AE.. which should be 10.0.1.1

And change the second DNS to google.. 8.8.8.8

Tell me if that gets you anywhere.

I don't see how it will help but please install the airport utility for windows into the windows machines.

Download AirPort Utility 5.6.1 for Windows

It is latest update.. 2012 .. win7 but it will install on win10.. if you hold your tongue on the right cheek and keep your computers to windward of prevailing breezes.. and the moon is waxing crescent.. (sarcasm is the lowest form of wit.. but necessary for sanity in dealing with computers).

It will say it is not within spec to configure an AC airport.. but ignore the message and continue.. it does install bonjour for windows which maybe vital missing key.

If none of that works.. (warning.. it may well not work).

Then the AE is somehow incompatible.. but it is not a problem I have seen. I will try to reproduce it in a setup here.. but my home is undergoing renovation and it might take me a while to get enough components together.

The problem you run into here is that Apple routers are designed for Apple networks.. with a feint nod to windows (yes.. it does exist.. outside the Apple walled garden and is therefore to Apple virtually non-existent).

For my own network I have an Asus router as the main unit.. Apple routers do not work with my ISP. There is no choice but use alternative brand. What is worse is that Apple provide no advanced menu controls for when their limited range of setups go wrong. They know it will work with Apple clients.. to them.. end of story.

Most unusual in a flat single IP range setup for ping failure.

From the PC can you ping Internet addresses?

Is the FIOS bridged or are you using a double NAT setup?

To understand what is going on I really need you to post some screenshots.

I need to see WAN and LAN IP of the airport in the summary page .. you can take screenshot on the ipad and post to site.. albeit not as conveniently as from a Mac.

At least tell me how the FIOS is configured.. What is the WAN and LAN IP of the airport and its configuration.

I am reserving two addresses (192.168.1.180 and 192.168.1.190) for the two PCs and naming them in the description field.

Does your name in the AE, exactly match the computer share name?

when I try to ping one machine from the other using the ip address the ping times out

If ping by IP fails then ping by name will certainly fail as well.

P.S. When reserving another address (192.168.1.170) for a PC running Ubuntu and naming it, I can ping it from a Win machine using the IP address but not the name. I cannot ping the Win machine from the Ubuntu one though.

Are you running extra security software on the win10 machine which is set to not respond to ping. It is interesting that win machine can ping ubuntu.. but not visa versa. Perhaps you are blocking ping which would be a simple answer.

Failure to ping by name when IP does work to Ubuntu indicates you also have a domain issue.

Look at your settings and find what is the default domain in the windows machines...

https://www.windows-commandline.com/find-domain-name-command-line/

By default the AE should be set to local

But it will depend on the FIOS and over all setup.. so I need to see the whole lot.

Ignore the last bit..

What type of broadband service do you have? Are you on cable with a pure modem or some fiber service or VDSL etc.??

I ran out of edit time and I am getting too old to keep all the info in a thread in my head.

I think your solution of using a different router is the best one in the end. Particularly if you are not using Mac in the network. PC should work fine to airport.. but I think the domain stuff is what is wrong.

So it seems that the router does not know IPv4 style addresses. Must be a setting somewhere... Any idea?

The windows computers are still picking up the verizon.net as well as the native WORKGROUP.. and the airport is doggedly sticking to its default local. Apple removed any ability to change domain long long ago.

One thing I recommend to people with network issues between different OS is use a single domain.. that means you MUST force the main router and clients to use local. Since the Airport cannot be altered.

Still, something more than just domain has failed if it cannot ping by IP.

I cannot reproduce the problem. I still need to build a whole new network using an airport as main router to test it fully. Bypassing the issue using a normal router is best fix IMHO.