Exchange server ping request using mydomain.int returns ipv6 instead of ipv4

Benard Mwanza 996 Reputation points
2021-12-20T10:09:28.817+00:00

I have the following exchange server issues, (exchange server 2016 CU19)

1 Exchange server ping request returns ipv6 instead of ipv4 as the primary,
on running ping exch1.berniecom.int -4 it returns ipv4

2 On querying exchange organization info, i get the following error.
PS C:\Windows\system32> Get-OrganizationConfig Active Directory server is not available. Error message: Active directory response: The LDAP server is unavailable. At line:1 char:1 + Get-OrganizationConfig + ~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], ADTransientException + FullyQualifiedErrorId : [Server=exch1,RequestId=0005c279-2c50-4581-b520-261bceb2aa5b,TimeStamp=20-Dec-2 1 9:30:52 AM] [FailureCategory=Cmdlet-ADTransientException] B7D333DC

3 Most of exchange services are stuck starting or stopping.
On restarting, i get error failed to restart the "service name"

4 I'm able to ping AD from exchange, able to telnet port 389, 53 from exchange to AD as well.

what could be the issue?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,356 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. KyleXu-MSFT 26,211 Reputation points
    2021-12-21T01:56:26.013+00:00

    @Benard Mwanza

    Exchange server ping request returns ipv6 instead of ipv4 as the primary,

    It is an expected behavior, because windows favors IPv6 global unicast addresses over IPv4 addresses by default. You could use the prefix policies to change it: Guidance for configuring IPv6 in Windows for advanced users

    On querying exchange organization info, i get the following error.

    How do you create this querying? Do you mean run Get-OrganizationConfig command in EMS？I think this issue is related with the service down.

    Most of exchange services are stuck starting or stopping.

    What is the detailed error information about the error? Exchange server has dependencies with other service, try to start pre-service first: Exchange services on Mailbox servers. Such as you need to start the "Net.TCP Port Sharing Service" before stating the "MSExchangeADTopology".

    I also notice that there exists some services "stuck starting", try to check whether there is a shortage of resources on your server from Task Manager.

    If you still cannot start those service, could you provide a screenshot or detailed error information?

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments