up vote 2 down vote favorite
share [g+] share [fb]

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!

link|improve this question
100% accept rate
As a Microsoft technician's reply to a recent windows issue: "Weird!". What steps did you take to disabling IPv6 on these servers? Can you ping localhost with IPv6? (ping -6 localhost) – l0c0b0x Jul 28 '09 at 23:18
feedback

4 Answers

up vote 2 down vote accepted

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

link|improve this answer
In addtition also do nslookup to see what DNS is resolving to. – Saurabh Barjatiya Jul 29 '09 at 9:21
feedback
up vote 3 down vote

If you want to just ping IPv4 (useful for finding the IP of a FQDN) then just tack a -4 onto the end of your ping request. Eg:

ping example.com -4

Doesn't really explain why you're getting IPv6 resolution when it's disabled though...

link|improve this answer
feedback
up vote 0 down vote

Ran into the same issue, resolved by deleting IPv6 entries in DNS server and then flushing dns (restarted clients for good measure).

link|improve this answer
feedback
up vote -1 down vote

See: http://support.microsoft.com/kb/981953

link|improve this answer
1  
Welcome to Serverfault. It's considered bad practice to just post a link as an answer. We would prefer it if you posted a summary of the solution in the answer, with attribution to any links. The aim is to have SF a repository of answers, rather than links to answers. Thanks. – Sam♦ Jan 13 at 15:52
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.