Share via

Windows Server 2019 Internet Issues DNS

DillonB 96 Reputation points
2020-08-12T17:52:38.103+00:00

I have been running Server 2019 for quite some time. Some how recently we've been having issues with accessing the Internet.
Webites will not load and sometimes clicking refresh they will load again after a few minuets. (Happens with all)

I replaced the router, which seemed to notibly make a difference but now its back to square one, and I am thinking replacing the router may not have been the issue if we came back to it again.

On any device on the network if I point the DNS (Statically) to the Router it will browse any website on the Internet. No issue.

Leaving it to the DNS of Server 2019 and we got issues.
ERR_CONNECTION_TIMED_OUT
DNS_PROBE_FINISHED_NXDOMAIN
DNS_PROBE_FINISHED_BAD_CONFIG

In command prompt I have ran ipconfig /flushdns and no change

In DNS Settings Server Name>(Right Click) Properties>Forwarders>192.168.1.1 <Unable to resolve>
Some other times, I check it, it will resolve, at it's discretion.

Control Panel\Network and Internet\Network Connections
Ethernet>Properties>IPv4
IP: 192.168.1.2
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1

DNS: 127.0.0.1
Pinging stuff goes as follows:

C:\Users\Administrator>ping google.com

Pinging google.com [172.217.5.14] with 32 bytes of data:
Reply from 172.217.5.14: bytes=32 time=43ms TTL=117
Reply from 172.217.5.14: bytes=32 time=37ms TTL=117
Request timed out.
Request timed out.

Ping statistics for 172.217.5.14:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 43ms, Average = 40ms

C:\Users\Administrator>ping google.com

Pinging google.com [172.217.5.14] with 32 bytes of data:
Reply from 172.217.5.14: bytes=32 time=35ms TTL=117
Reply from 172.217.5.14: bytes=32 time=41ms TTL=117
Reply from 172.217.5.14: bytes=32 time=37ms TTL=117
Reply from 172.217.5.14: bytes=32 time=38ms TTL=117

Ping statistics for 172.217.5.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 41ms, Average = 37ms

C:\Users\Administrator>ping microsoft.com

Pinging microsoft.com [104.215.148.63] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 104.215.148.63:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I don't understand how it can be a router problem if it works fine using the DNS as the router manually.

I don't know what settings in Server 2019 to look at as it looks fine to me. Definetely the issue is within Server 2019, where I have no clue.

Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,026 questions
0 comments
Accepted answer
  1. DillonB 96 Reputation points
    2020-08-15T16:20:20.057+00:00

    I received a new PCI Express Ethernet Card and installed it.
    In the boot area I disabled the internal NIC and left it to the PCI Express one.

    I put the same values in for IP and all that. No issues for 24 hours now.

    Everything appears to be normal at this point and any computers on the network using WPA2 Enterprise authenticate immediately.

    Remote desktop connection holds steady. File transfers function faster. Internet loads webpages normally on the DC part and on the client side.

    It turns out the NIC built into the server has failed. And replacing it with an external PCIE resolved the issue.

6 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.2K Reputation points MVP
    2020-08-12T18:00:31.803+00:00

    Assuming a domain environment I'd check that the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS

    --please don't forget to Accept as answer if the reply is helpful--

  2. Dave Patrick 426.2K Reputation points MVP
    2020-08-12T19:14:19.303+00:00

    Could be something is broken. Please run;

    • Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
    • repadmin /showrepl >C:\repl.txt
    • ipconfig /all > C:\dc1.txt
    • ipconfig /all > C:\dc2.txt
    • (etc. as other DC's exist)
    • ipconfig /all > C:\problemworkstation.txt

    then put unzipped text files up on OneDrive and share a link.

  3. Dave Patrick 426.2K Reputation points MVP
    2020-08-12T20:10:04.377+00:00

    If problems persist after fixing these above issues then put up a new set of files to look at.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  4. Sunny Qi 10,906 Reputation points Microsoft Vendor
    2020-08-13T05:32:46.933+00:00

    Hi,

    Just to check if the above reply from DCPatrick was helpful, if yes, you may accept useful reply as answer, if not, welcome to feedback.

    Best Regards,
    Sunny

    0 comments