Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
David Knudsen

Essentials Connector stays grey - cannot connect to 2016 server

Windows 10 1709 clients and Server 2016 Standard with Essentials Role. DirectAccess is configured on the server, but these clients are directly connected to the network (same subnet as server).

The Connector installed without problems a few days ago and immediately after install, the connector was green and a manual client backup initiated from the Essentials console worked fine. Now it stays grey, indicating the server is unavailable/offline ... even though network shares are accessable.

Laptops connecting through DirectAccess show online in the Essentials console, while all the IPv4 connected workstations are showing as offline. Maybe this is IPv6 related?

Any ideas about where to go from here would be most appreciated ... or just comparison with your setup:  Is ''ping -6 server'' working from your workstations?

Ping results from these workstations;

PS C:\windows\system32> ping w16-ess

Pinging w16-ess.tm.technomedics.no [192.168.50.22] with 32 bytes of data:
Reply from 192.168.50.22: bytes=32 time<1ms TTL=128
Reply from 192.168.50.22: bytes=32 time<1ms TTL=128
Reply from 192.168.50.22: bytes=32 time<1ms TTL=128
Reply from 192.168.50.22: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.50.22:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\windows\system32> ping -6 w16-ess

Pinging w16-ess.tm.technomedics.no [fd9b:b9be:a7e9:1:0:5efe:192.168.50.22] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for fd9b:b9be:a7e9:1:0:5efe:192.168.50.22:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

IPCONFIG workstation: 

Windows IP Configuration

   Host Name . . . . . . . . . . . . : PATRICIA
   Primary Dns Suffix  . . . . . . . : tm.technomedics.no
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : tm.technomedics.no

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : tm.technomedics.no
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-LM
   Physical Address. . . . . . . . . : 4C-CC-6A-19-EC-EE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4076:ac92:8357:bf87%3(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.50.112(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : fredag 9. august 2019 13:51:55
   Lease Expires . . . . . . . . . . : lørdag 17. august 2019 13:51:56
   Default Gateway . . . . . . . . . : 192.168.50.1
   DHCP Server . . . . . . . . . . . : 192.168.50.11
   DHCPv6 IAID . . . . . . . . . . . : 55364714
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-CD-A1-05-4C-CC-6A-19-EC-EE
   DNS Servers . . . . . . . . . . . : 192.168.50.11
                                       192.168.50.12
   NetBIOS over Tcpip. . . . . . . . : Enabled

IPCONFIG server:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : w16-ess
   Primary Dns Suffix  . . . . . . . : tm.technomedics.no
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : tm.technomedics.no

Ethernet adapter Ethernet0:

   Connection-specific DNS Suffix  . : tm.technomedics.no
   Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
   Physical Address. . . . . . . . . : 00-50-56-A2-46-8C
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : fd9b:b9be:a7e9:3333::1(Preferred)
   Link-local IPv6 Address . . . . . : fe80::99aa:bde4:34cb:d5d%5(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.50.22(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.50.1
   DHCPv6 IAID . . . . . . . . . . . : 50352214
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-F2-34-F5-00-50-56-A2-46-8C
   DNS Servers . . . . . . . . . . . : 192.168.50.11
                                       192.168.50.12
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.tm.technomedics.no:

   Connection-specific DNS Suffix  . : tm.technomedics.no
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : fd9b:b9be:a7e9:1:0:5efe:192.168.50.22(Preferred)
   Link-local IPv6 Address . . . . . : fe80::5efe:192.168.50.22%15(Preferred)
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 218103808
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-F2-34-F5-00-50-56-A2-46-8C
   DNS Servers . . . . . . . . . . . : 192.168.50.11
                                       192.168.50.12
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6TO4 Adapter:

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

Tunnel adapter IPHTTPSInterface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : IPHTTPSInterface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : fd9b:b9be:a7e9:1000::1(Preferred)
   IPv6 Address. . . . . . . . . . . : fd9b:b9be:a7e9:1000::2(Preferred)
   IPv6 Address. . . . . . . . . . . : fd9b:b9be:a7e9:1000:477:ac6a:a81a:3263(Preferred)
   Link-local IPv6 Address . . . . . : fe80::477:ac6a:a81a:3263%4(Preferred)
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 419430400
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-F2-34-F5-00-50-56-A2-46-8C
   NetBIOS over Tcpip. . . . . . . . : Disabled

 

asked08/09/2019 12:58
100 views
Add Comment
Last Activity 08/12/2019 06:31

1 Answer(s)

  • Bill Swan

    Hi 

     

    Im slightly confused with your setup as opposed to a normal Essentials setup.

    Server should be DHCP and DNS, yet you seem to have something at .11 doing dhcp, also what is the .22 dns server too?

    Router is .1

    Server is .22

    default configuration for server is normally dns 127.0.0.1

    ????? .11

    ????? .12

    Is this a plain install or migration ?

    From a workstation .. nslookup servername post outcome and tracert servername

     

     

    answered 08/10/2019 08:10
    Add Comment
    David Knudsen

    Thank you for responding!  Yesterday I resolved the issue by restoring a backup of the server, but this is my setup:

    .11 = AD/DNS/DHCP on a separate server.
    .22 = Windows Server 2016 with Essentials Role

    PS C:\Users\admin-dmk> nslookup w16-ess
Server:  w16-ctrl1.tm.technomedics.no
Address:  192.168.50.11

Name:    w16-ess.tm.technomedics.no
Addresses:  fd9b:b9be:a7e9:1:0:5efe:192.168.50.22
          192.168.50.22

PS C:\Users\admin-dmk> tracert w16-ess

Tracing route to w16-ess.tm.technomedics.no [192.168.50.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  w16-ess.tm.technomedics.no [192.168.50.22]

    Turns out the IPv6 connectivity was a red herring. After restoring the server to an earlier state, the Essentials Connector turned green on all clients ... even though ping -6 still shows the same results as my original post.

    I'm not thrilled that I still don't know exactly what caused the Connector to stop functioning. The most recent change was installing the 'Print and Document Services'-role, but I'm sure plenty of people have added that to their Essentials server without any issues.

    Reply
    replied 08/12/2019 06:31
Add an Answer