Windows 10 Ping IPV6 fails

Windows 10 Pro on Windows 2012 Domain

All computers have IPV4 and IPV6 addresses.
Windows 2008
Windows 2012
Windows 7
Windows 8
Windows Vista

All the above can ping using ping -4 xxxxxxxx   and ping -6 xxxxxxxx

My Windows 10 can ping -4 xxxxxxx   not problem  fails doing same device ping -6 xxxxxxx
ping -6 serv011
Ping request could not find host serv011. Please check the name and try again.

ping -4 tgcs011

Pinging serv011.fqdn.com [10.2.8.30] with 32 bytes of data:
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128

Ping statistics for 10.2.8.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Checked the firewall on my Windows 10 Pro

File and Printer Sharing (Echo Request - ICMPv6-In)
File and Printer Sharing (Echo Request - ICMPv6-In)

Both enabled  same settings as the ICMPV4-in

my ipconfig /all


Windows IP Configuration

   Host Name . . . . . . . . . . . . : COMP001
   Primary Dns Suffix  . . . . . . . : FQDN.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : FQDN.com
                                       DOMAIN.COM

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : FQDM.com
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 00-25-64-87-18-E3
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : fd99:aa4e:8286:a08d:0:ffff:a02:845(Preferred)
   Lease Obtained. . . . . . . . . . : Thursday, October 08, 2015 10:36:26 PM
   Lease Expires . . . . . . . . . . : Tuesday, October 20, 2015 10:36:26 PM
   Link-local IPv6 Address . . . . . : fe80::54f4:ac78:7c84:ab4a%8(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.2.8.69(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Lease Obtained. . . . . . . . . . : Thursday, October 08, 2015 10:07:53 PM
   Lease Expires . . . . . . . . . . : Friday, October 16, 2015 10:07:53 PM
   Default Gateway . . . . . . . . . : 10.2.8.1
   DHCP Server . . . . . . . . . . . : 10.2.8.30
   DHCPv6 IAID . . . . . . . . . . . : 234890596
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-28-0E-FC-00-25-64-87-18-E3
   DNS Servers . . . . . . . . . . . : fd99:aa4e:8286:a08d:0:ffff:a02:818
                                       fd99:aa4e:8286:a08d:0:ffff:a02:81e
                                       10.2.8.30
                                       10.2.8.24
   NetBIOS over Tcpip. . . . . . . . : Enabled
   Connection-specific DNS Suffix Search List :
                                       DOMAIN.COM

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b145:ad4:f9a7:fabf%4(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.184.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, October 08, 2015 10:08:31 PM
   Lease Expires . . . . . . . . . . : Friday, October 09, 2015 10:38:27 PM
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 192.168.184.254
   DHCPv6 IAID . . . . . . . . . . . : 50352214
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-28-0E-FC-00-25-64-87-18-E3
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d54d:cdde:726a:bc21%3(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.163.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, October 08, 2015 10:08:31 PM
   Lease Expires . . . . . . . . . . : Friday, October 09, 2015 10:38:27 PM
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 192.168.163.254
   DHCPv6 IAID . . . . . . . . . . . : 33574998
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-28-0E-FC-00-25-64-87-18-E3
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   Primary WINS Server . . . . . . . : 192.168.163.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{2B8D8CF4-FC5E-4556-8015-F62B29580C0F}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{16E43945-87D5-4A85-B03B-54CB7978E3D1}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.FQDN.com:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : FQDN.com
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


All other machine can ping each other

My windows 10 computer does not ping ipv6 or reply to ping from other computer using ipv6

Only IPV4 works on the Windows 10 Computer

I thought it was the Firewall but all I know is to enable the above settings same as I did for IPV4 to allow ping


What am I missing here?


Thanks

Tom
LVL 23
Thomas GrassiSystems AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Why so many adapters on so many subnets? With such a convoluted setup, even minor misconfigurations like adapter order can matter. Packets may be going out the wrong adapter and thus off to the void.
0
Thomas GrassiSystems AdministratorAuthor Commented:
I have VMWare on my Windows 10 computer


I just disabled the VMware adapters and the problem still happens

Thoughts
0
Cliff GaliherCommented:
Start with nslookup. Ping is good to test connectivity, but if DNS is broken, you'll have issues. Older OSes may he using fallback methods to map a machine name to its IP address, but as each iteration of windows further secures the OS and blocks and disables unnecessary services, those fallback methods may be getting blocked. A proper DNS structure has always been recommended, but increasingly is required. One small typo in your AAAA record and your lookups will cause ping to fail.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Thomas GrassiSystems AdministratorAuthor Commented:
All AAAA records where dynamically defined

NSLOOKUP fails

nslookup serv011
Server:  UnKnown
Address:  fd99:aa4e:8286:a08d:0:ffff:a02:818


ping fd99:aa4e:8286:a08d:0:ffff:a02:818

Pinging fd99:aa4e:8286:a08d:0:ffff:a02:818 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for fd99:aa4e:8286:a08d:0:ffff:a02:818:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


the AAAA frecord of SERV011

serv011
serv011.fqdn.com
fd99:aa4e:8286:a08d:f399:8ff7:390d:1ff


Pinging by FQDN
ping serv011.fqdn.com
Pinging SERVS011.FQDN.com [10.2.8.30] with 32 bytes of data:
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128
Reply from 10.2.8.30: bytes=32 time<1ms TTL=128

Ping statistics for 10.2.8.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

So DNS is working
0
Cliff GaliherCommented:
I don't know why you think DNS is working. The address you tried to ping ends in 818. Your AAAA record ends in 1ff, and none of those correlate with your ipconfig posted earlier.
0
Thomas GrassiSystems AdministratorAuthor Commented:
The network adapters using ipv6 get two ipv6 addresses

DNS is working for ipv4 address

I can ping by server name
I can ping by FQDN

Does that mean DNS is working?
0
Thomas GrassiSystems AdministratorAuthor Commented:
Log Name:      System
Source:        Microsoft-Windows-DNS-Client
Date:          10/9/2015 10:35:33 PM
Event ID:      8010
Task Category: (1028)
Level:         Information
Keywords:      
User:          NETWORK SERVICE
Computer:      comp001.fqdn.com
Description:
The system failed to register pointer (PTR) resource records (RRs) for network adapter
with settings:

           Adapter Name : {D92E17F3-051D-4CFA-8EC1-18FC47F81037}
           Host Name : COMP001
           Adapter-specific Domain Suffix : our.network.tgcsnet.com
           DNS server list :
                   fd99:aa4e:8286:a08d:0:ffff:a02:818, fd99:aa4e:8286:a08d:0:ffff:a02:81e, 10.2.8.30, 10.2.8.24
           Sent update to server : <?>
           IP Address :
             fd99:aa4e:8286:a08d:0:ffff:a02:845

The cause was DNS server failure. This may be because the reverse lookup zone is busy or missing on the DNS server that your computer needs to update. In most cases, this is a minor problem because it does not affect normal (forward) name resolution.

If reverse (address-to-name) resolution is required for your computer, you can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
    <EventID>8010</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1028</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2015-10-10T02:35:33.894689900Z" />
    <EventRecordID>5867</EventRecordID>
    <Correlation />
    <Execution ProcessID="1064" ThreadID="1408" />
    <Channel>System</Channel>
    <Computer>COMP001.FQDN.com</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="AdapterName">{D92E17F3-051D-4CFA-8EC1-18FC47F81037}</Data>
    <Data Name="HostName">COMP001</Data>
    <Data Name="AdapterSuffixName">FQDN.com</Data>
    <Data Name="DnsServerList">      fd99:aa4e:8286:a08d:0:ffff:a02:818, fd99:aa4e:8286:a08d:0:ffff:a02:81e, 10.2.8.30, 10.2.8.24</Data>
    <Data Name="Sent UpdateServer">&lt;?&gt;</Data>
    <Data Name="Ipaddress">fd99:aa4e:8286:a08d:0:ffff:a02:845</Data>
    <Data Name="ErrorCode">9002</Data>
  </EventData>
</Event>


I just ran an ipconfig /registerdns

Have to wait for DNS to populate up to 15 minutes
0
Thomas GrassiSystems AdministratorAuthor Commented:
Do I need an IPV6 Reverse Lookup Zone?
0
Cliff GaliherCommented:
Windows runs a full dual stack. DNS can work for IPv4 and fail for IPv6. The two can be almost unrelated in reliability functionality, and configuration. Since your addresses are fd99:, I can only assume someone at some point actively set up unique local addresses, so this is just a matter of improper configuration. Walk through each step. Wireshark it if need be. Follow the packet from client to server. Look for server misconfigurations and that it responds. Then follow the response back to the client.

While it is common to have multiple IPv6 addresses on a machine, it is very UNCOMMON to have multiple unique-local addresses. You'd usually see a link-local, maybe a unique-local, and one or more unique-global addresses. But multiple unique-local addresses usually don't server a purpose. That alone is cause for concern.
0
Cliff GaliherCommented:
Only if you want/need reverse lookups. Not having a zone or PTR records will bot impact forward lookups, which is your current issue you've asked about.
0
Thomas GrassiSystems AdministratorAuthor Commented:
ok

Then why do my Windows 2012 Server work fine?

It is a Windows 10 issue not how the network is setup
0
Thomas GrassiSystems AdministratorAuthor Commented:
Note:

My Current Reverse Lookup Zone has only IPV4 Addesses with a Pointer Type all with current Timestamp dates,

No IPV6 addesses listed.

so whats up with the Event id 8010 error?
0
Cliff GaliherCommented:
"It is a Windows 10 issue not how the network is setup"

You are the one asking for help, but hey, apparently you know best. Good luck.
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
For test, remove the IPv6 DNS Server IPs from your W10 NIC, and let it ask DNSv4 for v6 addresses. Of course you will need to have AAAA entries in DNSv4 for that to work.
0
Thomas GrassiSystems AdministratorAuthor Commented:
Thanks for the reply

my nic obtains its settings from my DHCP servers.

Should I just change the DNS section to
 use the following DNs server addresses
 instead of
Obtain DNS server address automatically

Is that what you mean?
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Yes, please switch to static DNS, and only provide an IPv4 DNS server (10.2.8.30).
0
Thomas GrassiSystems AdministratorAuthor Commented:
Qlwmo

Sorry but it will not allow me to make that change.

it displays 10.2.8.30 is not a valid ip address.

This is a IPV6 configuration so it will not allow and ipv4 address

Thoughts
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Nonsense. The NIC has 10.2.8.69 as IPv4, so of course you can set up a DNSv4 address.
0
Thomas GrassiSystems AdministratorAuthor Commented:
Qlemo

sorry for the confusion

My nic does have IPV4 address which comes from DHCP and have the DNSv4 addresses which comes from the scope.

My Nic also gets the IPV6 address from the same DHCP server.

The ipconfig /all shows this.

I can not change the ipv6 info to a dnsv4 address not valid.

Are you suggesting that I made both the IPV4 and IPV4 static addresses and DNS info?

I can try that as a test if you think so.
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Ok, now we are getting somewhere. Yes, I want you to not set DNSv6 in IPv6 config (static and empty), and static DNSv4 in IPv4.
0
Thomas GrassiSystems AdministratorAuthor Commented:
no good did not work

What is wrong with Windows 10 and IPV6
0
Thomas GrassiSystems AdministratorAuthor Commented:
Thanks guys your suggestions leads me to fix this but I still have an issue with Windows 10 or DHCP

I fixed this by making the IPV6 settings address and DNS servers static on my nic

I was trying to get the info from my DHCP servers but I think there is something wrong with the DHCP config or it is a Windows 10 issue with IPV6

Thanks again
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.