Windows server 2019 нет интернета

Hi all.

I have a Windows Server 2019 VM (HyperV) where I setup my first DC. I also setup DNS and DHCP on the server. After deploying these, the yellow warning icon appeared on the network icon in the bottom right corner, and it says «No internet access». Indeed, Internet access seems to be working normally. The only issue is the DNS sometimes unable to resolve certain random domains. It seems that unbinding IPv6 from the NIC almost solved this issue, but the warning icon and the No Internet message remains.

I tried the troubleshooting tool. It is unable to diagnose the issue, and suggests a network reset. I did it twice, but it did not change anything.

I took a dump of the network packets when the diagnostic tool is run, but I see nothing unusual. It finally connects to http://www.microsoft.com:80/ which I think is the normal way to determine if Internet is available. The server responds 200 Ok and some codes.

I don’t know where to look further. 

My ipconfig /all:

Windows IP Configuration

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

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-00-78-03
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.112(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.254
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

I attach one of the diagnostic reports.

Thank to anyone who can help.

Describe the bug

We are currently deploying GCP Windows Server 2019 (specifically this image windows-2019-for-containers). We hit a rather weird issue where when creating a new vm instances sometimes the containers that run on the machine don’t have internet access. The base image that we are using for our containers are mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019.

As part of GCP we are using Managed Instance Groups which allow us to recreate if there is an issue and recreation doesn’t solve this issue.

I have tried to create a new custom nat and this behaves the exact same. Looking at the interface shows the right Ethernet adapter has the higher priority.

The work around is to create a transparent network using docker network create -d transparent test_net and then removing it. Whatever this does (I am guessing to the external nic) fixes the issue. As part of the creation, we don’t connect any containers to it.

This network is created while the other containers are running and are connected to the default nat.

Why would create a temporary transparent network fix the nat connectivity to the internet?

To Reproduce

Steps to reproduce the behavior:

Not reproducible in all instances. Only happened on 3 of the 30 machines.

1. Create a Managed Instance Group using base image windows-2019-for-containers
2. Create 2 VM Instances
3. Using docker-compose to pull and run the docker containers.
4. using docker exec <container_name> powershell ping 8.8.8.8

Expected behavior

Default container nat allows for connecting to the internet.

Configuration:

• Edition: Windows Server 2019 Datacenter
• Base Image being used: aspnet:4.8-windowsservercore-ltsc2019
• Container engine: docker
• Container Engine version 19.03.19

Additional context

When trying to diagnose:

• Unable to ping 8.8.8.8
• Unable to resolve google.com
• You are able to ping Host IP
• You are unable to other MIG VM instances
• HNS Service is Started
• HNS information Get-HNSNetwork and Get-HNSEndpoint looked fine (as far as I could tell)
• Windows Server 2019 doesn’t appear to have a way to look at the virtual switch
• Internal network information has the correct default gateway, also the host DNS server entries to communication with NIC was setup
• Ran debug-container-host.ps1 but nothing stood out other than it couldn’t find Get-VMSwitch as a cmdlet

Подождите!

Ответ нейросети:

⚠️Зарепортить пост!

Всем привет. В организации инет приходит на сервер и раздаётся им по локальной сети. Всего в сети около 50 компьютеров. Подключены через коммутаторы. Раньше всё работало нормально, но у сервера накрылся жёсткий диск. Переустановил ос (Windows Server 2019), настроил подключение сервера к инету. Расшарил его через свойства подключения -> доступ -> разрешить другим использовать подключение к интернету. Создал общую папку на сервере для обмена файлами. DNS, DHCP не настраивал. ip на всех компах прописал вручную. В целом всё работает, но периодически на некоторых компьютерах пропадает инет и теряется доступ к общей папке. Лечится перезагрузкой сервера. Подскажите в чём может быть причина и как исправить?

• 
  Вопрос задан
  
  более двух лет назад
  

• 388 просмотров