Ask a question

Barnaby  Burman

SBS2008 to Essentials 2016 - "Connection-specific DNS Suffix" Blank and VPN not working

Hi,

I have migrated from SBS2008 to Essentials 2016 and have followed all of the instructions apart from setting the DHCP to run off the Router (Draytek 2830) but the router is now pointing the DNS back to the new 2016 server.

I now have two main problems:

1) The "Connection-specific DNS Suffix" is blank when doing IPconfig /all even when on the server. I have cleaned up the DNS settings as per the instructions but has not made any differences. I have also run the powershell checks and everything tallies up ok.

2) Clients are able to VPN onto the network but are unable to connect to a server, ping them or anything, using an IP address, FQNP or domain address. I have tried to set up the connection properties (IPv4) on the client PC to use the servers DNS but it does not make any difference. Is the problem because it's using the DHCP from the router and is causing confusion with the DNS on the server?

I have looked through the internet to resolve these issues without any success. Below is a copy of "IPCONFIG /ALL" from the server.

If anyone has any ideas, please let me know.

Thanks,

Barney


Windows IP Configuration

   Host Name . . . . . . . . . . . . : WTSCSERVER2016
   Primary Dns Suffix  . . . . . . . : wtsc.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : wtsc.local

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
   Physical Address. . . . . . . . . : 00-15-5D-13-6C-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e0f0:76b5:8107:5e21%9(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.9(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 50337117
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-B6-A4-C2-00-15-5D-13-6C-00
   DNS Servers . . . . . . . . . . . : ::1
                                       127.0.0.1
                                       192.168.0.9
   NetBIOS over Tcpip. . . . . . . . : Enabled

PPP adapter RAS (Dial In) Interface:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : RAS (Dial In) Interface
   Physical Address. . . . . . . . . : 
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.56(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : 
   NetBIOS over Tcpip. . . . . . . . : Enabled

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.{A0430827-2E98-4637-8D71-8674735CF47E}:

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

Tunnel adapter isatap.{6E06F030-7526-11D2-BAF4-00600815A4BD}:

   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
 

 


  • Windows Server Essentials 2016
  • DNS
  • Remote Web Access
asked01/20/2019 18:31
22 views
Add Comment
Barnaby  Burman

I have tried the solution as advised to create the static group, but the problem seems to be that the "Subnet Mask" on the network is 255.255.255.0 and whatever default pool I use it gives the VPN clients a subnet of 255.255.255.255. Is there a solution to this? 

Last Activity 01/25/2019 06:43

2 Answer(s)

Add an Answer