Ping returns an IPv6 address

ipv6networkingwindows-server-2008

I have 3 servers, a DC an exchange server and an apps server.
If I ping the DC from any server or ping any server from the DC I get an IPv4 response, as you would expect, however if I ping exchange from apps, or the other way round the result I get is an IPv6 address.

All the NICs have IPv6 unticked so I can't understand why they are responding with these addresses, I also think this is causing problems because the Blackbery Enterprise Server I have just installed on apps cannot communicate with the Exchange server.

Any ideas how to get back to regular old IPv4?

The problem with BES resolving Exchange does seem to be an IP or DNS issue. If I use the IPv4 address of the exchange server in the BES MAPI setup it resolves that name to Exchange, and gets a connection, but then when you start BES it tries to resolve the name, and fails!

Best Answer

are these actually responding on ipv6 or are they resolving ipv6. If they are resolving to IPv6 they might be cached or have ipv6 addresses registered in DNS.

I'd try (at the command prompt) running:

   ipconfig /flushdns
    nbtstat -R

then seeing if you have the same problem

Related Solutions

Sql-server – how does ping resolve to ipv4 on one machine, but ipv6 on another

Looking at your nslookup results, do you have the same domain suffix search list on both machines? Hit the advanced button in the TCP/IP properties page, then go to the DNS tab. Are there any differences there?

Also, why don't you give us the output of ipconfig /all from a command prompt?

--Christopher Karel

Disable IPv6 on Loopback address (Localhost, Computer name, …)

I had initially checked the host file as SilverbackNet suggested, but on a Windows 2008 R2 server this is the default file:

# localhost name resolution is handled within DNS itself.
#   127.0.0.1       localhost
#   ::1             localhost

# indicates a comment in the host file, so all the entries are commented out, and the first line is a bit confusing. I then noticed that there were two entries for localhost that were commented out, so I tried uncommenting the IPv4 one and it worked! I should have tried that first but I was thrown off track by the first line. Using the below host file pinging the computer name or localhost will always return an IPv4 address, which fixes the problem with the 3rd party software!

# localhost name resolution is handled within DNS itself.
#   ::1         localhost
127.0.0.1       localhost
127.0.0.1       VPS-Web

Best Answer

Related Solutions

Sql-server – how does ping resolve to ipv4 on one machine, but ipv6 on another

Disable IPv6 on Loopback address (Localhost, Computer name, …)

Related Topic