none
PING, Time, Issues and Clients struggling to find a DC RRS feed

  • Question

  • Hi, i'm hoping someone will be able to help or guide me on the following issue, just struggling to find the issue :(

    I first discovered this issue by performing a Ping for one Server 2012 to another, at which point it failed. This has then extended to Clients not being about to locate a Domain Controller, Time Server etc

    In my testing there are 2x Windows Server 2012 [server-ad & server-rds] and 1x Windows 7 Pro [jason-pc2]

    server-ad is the only Domain Controller

    server-rds is for Remote Desktop Services

    jason-pc2 is a standard desktop with local admin rights, user is a domain admin also

    How my issue was detected;

    On [jason-pc2] ping [server-ad & server-rds] (on IPV4/IPV6) -- OK

    --

    On [server-ad] ping [jason-pc2] (IPV4) -- OK

    On [server-ad] ping [jason-ad] (IPV6) -- FAILED

    On [server-ad] ping [server-rds] (IPV4) -- TIMED-OUT

    On [server-ad] ping [server-rds] (IPV6) -- FAILED

    --

    On [server-rds] ping [jason-pc2] (IPV4) -- OK

    On [server-rds] ping [jason-pc2] (IPV6) -- FAILED

    On [server-rds] ping [server-ad] (IPV4) -- TIMED-OUT

    On [server-rds] ping [server-ad] (IPV6) -- FAILED

    --

    Now if i ping Server to Server with a -t i get a reply (1 in 10 sucessfull), i'm not sure if i'm looking at this from the wrong angle and thats why i'm struggling!!

    Both servers are a Hyper-V instance

    I'll be rebooting the servers tonight and i'll note down any recent event ID's, there were some LDAP events but i can connect with LDP.exe on 389 ok, there is one for ADWS Certificate Events with not findng a certificate (there isn't any) some were outdated and were removed - so not sure if this was an issue.

    Domain used to be a Windows 2003 domain and although the roles were moved, the server has only recently been removed from the domain (it developed a hardware issue), the issues were present before this though, i have since raised AD level to 2012 and ensured the 2003 server isn't listed/present anywhere.

    So if ANYONE can give me some pointers i'd be very happy :)

    Tuesday, March 29, 2016 4:41 PM

All replies

  • Hi Clive,

    To narrow the range of the issue,you could try follow steps:

    1.Please post the text of an unedited ipconfig /all of the 3 devices.

    2.Please check 3rd-party software,switch/router,firewall, make sure there is no filter or blocking.

    3.Please run 'dcdiag' on the server.

    4.You could perform a network captuer .Determine where is breaking down between two servers.
    Here is the link of Windows network monitor:
    https://www.microsoft.com/en-us/download/details.aspx?id=4865

      Best Regards,

    Cartman

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, March 30, 2016 2:45 AM
  • ipconfig /all results below;

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : SERVER-AD
       Primary Dns Suffix  . . . . . . . : Rooke.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Rooke.local

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
       Physical Address. . . . . . . . . : 00-15-5D-01-87-00
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::8179:4a9c:7c4e:2666%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.21(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{0BA825CE-1361-4512-BE68-1B4BD101C930}:

       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 Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    ----------

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : SERVER-RDS
       Primary Dns Suffix  . . . . . . . : Rooke.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Rooke.local

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
       Physical Address. . . . . . . . . : 00-15-5D-01-87-04
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::a82d:e55b:280b:25bc%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.21
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{39F2512E-761F-482C-9038-42271EE05D29}:

       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 Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    ----------

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : JASON-PC2
       Primary Dns Suffix  . . . . . . . : Rooke.local
       Node Type . . . . . . . . . . . . : Mixed
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Rooke.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : D4-3D-7E-EE-7D-AC
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::a5c8:b052:2ee6:5d30%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 31 March 2016 10:59:01
       Lease Expires . . . . . . . . . . : 08 April 2016 10:59:01
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.21
       DNS Servers . . . . . . . . . . . : 192.168.1.21
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter VirtualBox Host-Only Network:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
       Physical Address. . . . . . . . . : 08-00-27-00-1C-83
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::ace0:766b:c360:c426%18(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.196.38(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 302514215
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-24-E7-51-D4-3D-7E-EE-7D-AC
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{14876174-28E4-43EB-A562-16926B22FA97}:

       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 Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{32FC2AA5-1D47-448D-9051-AB408ADA4349}:

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

    ----------

    Thursday, March 31, 2016 8:50 PM
  • DCDIAG results;

    Directory Server Diagnosis


    Performing initial setup:

       Trying to find home server...

       Home Server = SERVER-AD

       * Identified AD Forest.
       Done gathering initial info.


    Doing initial required tests

       
       Testing server: Default-First-Site-Name\SERVER-AD

          Starting test: Connectivity

             ......................... SERVER-AD passed test Connectivity



    Doing primary tests

       
       Testing server: Default-First-Site-Name\SERVER-AD

          Starting test: Advertising

             ......................... SERVER-AD passed test Advertising

          Starting test: FrsEvent

             ......................... SERVER-AD passed test FrsEvent

          Starting test: DFSREvent

             ......................... SERVER-AD passed test DFSREvent

          Starting test: SysVolCheck

             ......................... SERVER-AD passed test SysVolCheck

          Starting test: KccEvent

             ......................... SERVER-AD passed test KccEvent

          Starting test: KnowsOfRoleHolders

             ......................... SERVER-AD passed test KnowsOfRoleHolders

          Starting test: MachineAccount

             ......................... SERVER-AD passed test MachineAccount

          Starting test: NCSecDesc

             ......................... SERVER-AD passed test NCSecDesc

          Starting test: NetLogons

             ......................... SERVER-AD passed test NetLogons

          Starting test: ObjectsReplicated

             ......................... SERVER-AD passed test ObjectsReplicated

          Starting test: Replications

             ......................... SERVER-AD passed test Replications

          Starting test: RidManager

             ......................... SERVER-AD passed test RidManager

          Starting test: Services

             ......................... SERVER-AD passed test Services

          Starting test: SystemLog

             ......................... SERVER-AD passed test SystemLog

          Starting test: VerifyReferences

             ......................... SERVER-AD passed test VerifyReferences

       
       
       Running partition tests on : DomainDnsZones

          Starting test: CheckSDRefDom

             ......................... DomainDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... DomainDnsZones passed test

             CrossRefValidation

       
       Running partition tests on : ForestDnsZones

          Starting test: CheckSDRefDom

             ......................... ForestDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... ForestDnsZones passed test

             CrossRefValidation

       
       Running partition tests on : Schema

          Starting test: CheckSDRefDom

             ......................... Schema passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Schema passed test CrossRefValidation

       
       Running partition tests on : Configuration

          Starting test: CheckSDRefDom

             ......................... Configuration passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Configuration passed test CrossRefValidation

       
       Running partition tests on : Rooke

          Starting test: CheckSDRefDom

             ......................... Rooke passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Rooke passed test CrossRefValidation

       
       Running enterprise tests on : Rooke.local

          Starting test: LocatorCheck

             ......................... Rooke.local passed test LocatorCheck

          Starting test: Intersite

             ......................... Rooke.local passed test Intersite

    Thursday, March 31, 2016 8:52 PM
  • Network monitoring, run whilst a Ping was performed;

    https://themanagedcloud.sharepoint.com/_layouts/15/guestaccess.aspx?guestaccesstoken=wBfgribuT4oGlzFbXh7sxzbUlCptXUWITfGT1%2b8SB8s%3d&docid=068675da4ef0343e38cd48dd8c9c16f4a

    https://themanagedcloud.sharepoint.com/_layouts/15/guestaccess.aspx?guestaccesstoken=TnRXE0xYUKHEsRJGAa8r1KgD%2fHDzJxG8UTrDN7JOmOo%3d&docid=0f9eb00f2b44744c898f8d0c1d429c33b

    Thursday, March 31, 2016 9:39 PM
  • Hi Clive,

    I have checked the network capture,both of AD and RDS have sent the ICMP requests,but intermittent repies.

    1.Please check the firewall between them.

    2.Please try to reset the TCP/IP protocol stack of AD and RDS.

    Best Regards,

    Cartman

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, April 1, 2016 8:16 AM
  • Hi

    Windows Firewall is off on both servers

    Router is a DrayTek V2860 but don't see why this would affect internal ping

    How do i do "2.Please try to reset the TCP/IP protocol stack of AD and RDS."

    Saturday, April 2, 2016 8:06 PM
  • Hi

    I have reset the 'stack' with direction from https://support.microsoft.com/en-us/kb/299357

    Ping is still either not working or random :(

    As a note this doesn't work on Name nor IP

    Monday, April 4, 2016 8:00 PM
  • Hi Clive,

    There is something else we can do.

    1.Update the driver of the NIC for both 2 servers.

    2.Recreate the virtual switch for Hyper-V.

    Best Regards,

    Cartman

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, April 5, 2016 1:39 AM
  • Hi

    There are no new drivers for the NIC's through updates/device manager.

    How do i recreate the switch? just a case of delete and create a new one?

    Thanks

    Tuesday, April 5, 2016 11:06 AM
  • Hi Clive,

    >>How do i recreate the switch? just a case of delete and create a new one?

    YES.

    Best Regards,

    Cartman

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, April 6, 2016 1:02 AM
  • Hi

    I'm trying to schedule this in, got to be an evening and ideally whilst the client can get to site if required (he lives near by!)

    Reading a little about creating etc and the article said the NIC gets disabled and re-enabled (hence the above)

    Not sure how much you know about the vSwitch?

    There are 4x NIC's (HP Proliant ML350p Gen8), the Host is using one (manual IP) NIC, i've created (when the server was built several years ago) one vSwitch per VM (server-ad / server-rds) for these two i have de-selected 'Allow management OS to share this NIC' -- i'm persuming this is correct? both VM's IP is manual within the VM and not on the host adaptor.

    The Host NIC is manual and doesn't reference the DNS of server-ad (as that server wouldn't be up on boot up), again persumming this is correct?

    Wednesday, April 13, 2016 7:49 PM
  • sorry didnt read everything but can you ping the ip address and vice versa? Just to isolate DNS issues..
    Wednesday, April 13, 2016 10:25 PM
  • Hi, i'll just briefly tell you what i've got and how IP etc is configured

    SERVER-2012 - Workgroup / Hyper-V Host

    SERVER-AD - Domain / VM

    SERVER-AD - Domain / VM

    ----

    SERVER-2012 IP

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : server2012
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter SERVER2012-Local:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331i Adapter #2
       Physical Address. . . . . . . . . : 9C-8E-99-58-CF-55
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::b09c:9a6f:b1b7:a5b6%13(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.20(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.21
                                           192.168.1.1
                                           8.8.8.8
       NetBIOS over Tcpip. . . . . . . . : Enabled

    SERVER-AD IP


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : SERVER-AD
       Primary Dns Suffix  . . . . . . . : Rooke.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Rooke.local

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
       Physical Address. . . . . . . . . : 00-15-5D-01-87-00
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::8179:4a9c:7c4e:2666%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.21(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    SERVER-RDS IP

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : SERVER-RDS
       Primary Dns Suffix  . . . . . . . : Rooke.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Rooke.local

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
       Physical Address. . . . . . . . . : 00-15-5D-01-87-04
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::a82d:e55b:280b:25bc%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.21
       NetBIOS over Tcpip. . . . . . . . : Enabled

    PING's - From SERVER-2012

    ping server-ad -6

    Pinging SERVER-AD [fe80::8179:4a9c:7c4e:2666%13] with 32 bytes of data:
    Reply from fe80::8179:4a9c:7c4e:2666%13: time=1ms

    ping server-ad -4

    Pinging SERVER-AD [192.168.1.21] with 32 bytes of data:
    Request timed out.

    ping server-rds -6

    Pinging SERVER-RDS [fe80::a82d:e55b:280b:25bc%13] with 32 bytes of data:
    Reply from fe80::a82d:e55b:280b:25bc%13: time<1ms

    ping server-rds -4

    Pinging server-rds [192.168.1.22] with 32 bytes of data:
    Reply from 192.168.1.20: Destination host unreachable.

    This is copied from above - ping tests from within the VM's

    On [jason-pc2] ping [server-ad & server-rds] (on IPV4/IPV6) -- OK

    --

    On [server-ad] ping [jason-pc2] (IPV4) -- OK

    On [server-ad] ping [jason-ad] (IPV6) -- FAILED

    On [server-ad] ping [server-rds] (IPV4) -- TIMED-OUT

    On [server-ad] ping [server-rds] (IPV6) -- FAILED

    --

    On [server-rds] ping [jason-pc2] (IPV4) -- OK

    On [server-rds] ping [jason-pc2] (IPV6) -- FAILED

    On [server-rds] ping [server-ad] (IPV4) -- TIMED-OUT

    On [server-rds] ping [server-ad] (IPV6) -- FAILED

    --

    JASON-PC2 - IP

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : JASON-PC2
       Primary Dns Suffix  . . . . . . . : Rooke.local
       Node Type . . . . . . . . . . . . : Mixed
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Rooke.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : D4-3D-7E-EE-7D-AC
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::a5c8:b052:2ee6:5d30%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.21
                                           192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    NOTE: Strangely enough SERVER-2012 can ping JASON-PC2 OK !!

    SERVER-2012 - CAN'T ping 192.168.1.21/22 which leads me to think this is a Host issue? rather than SERVER-AD DNS? As mentioned in a previous reply the vSwitch is NOT sharing with OS (read this is for teaming NIC's) - Hyper-V is not my area, not local servers anyhow.

    Any help/suggestions welcome :)



    Thursday, April 14, 2016 8:32 AM
  • Hi Clive,

    I did some research,and they tell me if you could send ICMP request,and random reply,it could be a VM-level issue,and add a new VM server to test if you could.If this issues is a state of emergency for you ,I suggest you open a case with Microsoft, more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
    Here is the link:
    https://support.microsoft.com/en-us/gp/support-options-for-business

    Best Regards,

    Cartman

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, April 15, 2016 6:20 AM