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.
Всем привет. В организации инет приходит на сервер и раздаётся им по локальной сети. Всего в сети около 50 компьютеров. Подключены через коммутаторы. Раньше всё работало нормально, но у сервера накрылся жёсткий диск. Переустановил ос (Windows Server 2019), настроил подключение сервера к инету. Расшарил его через свойства подключения -> доступ -> разрешить другим использовать подключение к интернету. Создал общую папку на сервере для обмена файлами. DNS, DHCP не настраивал. ip на всех компах прописал вручную. В целом всё работает, но периодически на некоторых компьютерах пропадает инет и теряется доступ к общей папке. Лечится перезагрузкой сервера. Подскажите в чём может быть причина и как исправить?
-
Вопрос задан
-
591 просмотр
По умолчанию во всех версиях Windows Server 2022/2016/2016/2012R2 отключена поддержка беспроводных WiFi сетей. Если вы подключите сетевой адаптер Wi-Fi (USB или PCI) к хосту с Windows Server, вы просто не сможете включить его в панели управления. В этой небольшой заметке я покажу, как включить поддержку Wi-Fi в Windows Server.
Подключите физический Wi-Fi адаптер к хосту Windows Server и установите драйвера. Убедитесь, что адаптер появился в диспетчере устройств (
devmgmt.msc
) в секции Network Adapters.
Откройте консоль PowerShell с правами администратора и убедитесь, что компонент Wireless LAN Service не установлен.
Get-WindowsFeature *Wireless*
Чтобы установить компонент или роль Windows Server воспользуйтесь PowerShell командой Install-WindowsFeature:
Install-WindowsFeature -Name Wireless-Networking
Или установите компонент Wireless LAN Service с помощью Server Manager (Add Roles and Features -> Features).
После завершения установки компонента нужно перезагрузить хост:
shutdown –f –r –t 0
После перезагрузки в Windows появится служба Wireless LAN Service (WLAN AutoConfig), но по умолчанию она отключена. Чтобы включить службу Windows и настроить ее на автоматический запуск, выполните:
Set-Service WlanSvc –startuptype automatic –passthru
Start-Service WlanSvc –PassThru
Теперь перейдите в центр управления сетями в Панели управления (
ncpa.cp
l) и включите Wi-Fi адаптер вручную (Правой кнопкой -> Enabled).
Теперь вы можете подключиться к Wi-Fi сети (уровень сигнала Wi-Fi доступных точек доступа можно получить с помощью PowerShell) или даже сделать точку доступа на базе вашего Windows Server.
Данная инструкция проверена на Windows Server 2019. В Server Core 2022 роль Wireless-Networking удалена, поэтому в Server Core настроить сеть на Wi-Fi не удастся.
We had a really weird issue on a clients domain server recently that wasted a lot of time trying to get to the bottom of, so I thought I’d document that here to save you the same fate.
We had logged onto the clients domain server and opened Google Chrome to browse to a local network device to administer it via a HTTP UI. We typed in the IP of the device into the address bar and received the dreaded «This site can’t be reached» error message.
Initially we thought the device might be switched off or removed from the network, so to test, we pinged the device to see whether it was in fact accessible. Yes, the device replied without issue. Hmmm, that’s weird. So I opened up a new tab to see whether I could surf the internet, once again I received the «This site can’t be reached» message.
I pinged other devices on the network and they were all responding without issue. I pinged Google via the command line and it responded and resolved correctly, so this wasn’t a DNS issue. I cleared the cache of the browser, flushed the DNS and cleared the cache of the Windows DNS server and the DNS cache of the firewall, closed the browser and re-open and still the same result. What’s going on here?
The server was a domain server as outlined earlier, and it was still serving the local network without issue and clients could connect to file shares hosted on the server, resolve DNS requests for both local and internet locales and nothing was impacted from what I could see.
Time to execute some more advanced remedial action like resetting the network settings. Please be aware that this needs to be done outside of business hours because the server will require a reboot. These are the commands I executed via an admin command line instance:
netsh winsock reset
netsh winhttp reset proxy
netsh winhttp reset tracing
netsh winsock reset catalog
netsh int ipv4 reset catalog
netsh int ipv6 reset catalog
After I rebooted the server, the same issue was still evident. Wow! Because this was a VM running under ESXi I thought that maybe the NIC had some type of issue, so I shut down the server and removed the NIC and re-added to ensure this wasn’t the problem. Still no joy!
So how was this rectified I hear you ask? The issue ended up being resolved by resetting Internet Explorers settings. This can be done by following the screenshots below:
Open Control Panel then:
Once you’ve completed the steps above, close all browsers. Now re-open your browser and you should be able to access the everything normally through the browser. This was a very easy fix in the end, but took a long time to come to the eventual remedy. I hope this saves you some time.
If you’ve found this useful, you may want to sign up to our newsletter where you’ll receive notices on when we post new articles and helpful «how tos». Just fill out your details below and we’ll do the rest…