Since you have a Killer E2400 NIC, try removing the Killer Control Center that probably got automagically installed from the Microsoft Store. It's been the cause of random connectivity issues in the past and its presence is completely unnecessary.
Several Dell Windows 11 cannot use wired Ethernet but can use WIFI
- Thread starter Donald
- Start date
See if you can ping google.com. If DNS is working it should reply with 142.251.167.113 and if not, it'll say unreachable which is a DNS issue.
Try to go to google.com in a browser. If it fails, try going to 142.251.167.113 and if it works then this is entirely a DNS issue.
Not necessarily, the answer is geography dependent.
But, it's very likley something starting with 142.250 or 142.251.
All of my tests for ping.ui.com all resolve to the 1.1.1.1 or 8.8.8.8.
Regardless, his test was valid, it's a DNS lookup problem.
Last edited:
So from my screen prints the DNS looks identical from the wired that does not work to the wireless that does.
If I can ping by IP address is there a point in removing the Killer Control Center.
If I can ping by IP address is there a point in removing the Killer Control Center.
Your screenshots are only showing that they are getting DHCP info and that your router is relaying whatever DNS server is assigned to it by your ISP. It doesn't show that DNS is actually working.
Do a 'ipconfig /flushdns' and try browsing via wire.
Do a 'ipconfig /flushdns' and try browsing via wire.
So besides changing the DNS to one of the DNS addresses you posted, what else to try?
I would like to be able to go to the church at lunchtime and have a few things to try.
- Joined
- Dec 20, 2024
- Messages
- 580
Control Panel > View as icons > Network and Sharing Center > Find the LAN > Doubleclick for Properties > Doubleclick on IPv4.
Picture, thousand words, etc:
My screenshot shows WiFi settings, in your case you'll of course go for the LAN settings.
You can disable most protocols as well. Usually you need ipv4 and client for Microsoft networks.
Might be a good idea to still keep the gateway's local address as the last DNS server in the list, so they can still revert to it if they are searching something on the local network.
Keep in mind that it might be able to set up something similar on the router itself, as it's likely that it's crapping the DNS by relying on the internet provider's DNS address (this would be something similar to the above, but done in the router's interface), but don't overcomplicate it for three computers. Try the above. Good luck.
Picture, thousand words, etc:
My screenshot shows WiFi settings, in your case you'll of course go for the LAN settings.
You can disable most protocols as well. Usually you need ipv4 and client for Microsoft networks.
Might be a good idea to still keep the gateway's local address as the last DNS server in the list, so they can still revert to it if they are searching something on the local network.
Keep in mind that it might be able to set up something similar on the router itself, as it's likely that it's crapping the DNS by relying on the internet provider's DNS address (this would be something similar to the above, but done in the router's interface), but don't overcomplicate it for three computers. Try the above. Good luck.
That’s enough for now
So I set the primary DNS to 8.8.8.8 and the backup to 8.8.4.4 and I can now ping ping.ui.com and browser works properly accessing websites. Do have a question on the options DNS over HTTPS. Off or On (automatic template) or On (manual template).
I am thinking On over automatic template
I am pretty sure previously wired and wireless both had DNS as automatic and only wireless worked. Cannot explain that yet.
This is another Unifi network that I am just taking over managing. I looked over the VLAN it would get wired vs wireless and they both default to automatic DNS. So whatever the ISP provides. The display of the wireless connection within IPCONFIG /all shows the Unifi router as the DNS.
I don't use unifi routers, so I can't comment on their setup. I do use their wifi stuff though.
The main reason you would rely on your gateway to forward/relay DNS requests is because you're trying some type of monitoring/blocking setup in the router and it needs that for the filtering insight. If you aren't filtering there, then don't add the relay function to the router's list of responsibilities, let the clients query the provider's DNS directly.
In order for the local gateway's filtering to be successsful, you'd need it to also block all other DNS requests to outside servers. If you don't, this filtering setup is easily bypassed by a client specifying an outside DNS server. I would note that this is a common tactic for infected systems, change the preferred DNS to complete/maintain the infection.
If you want DNS filtering, I'd suggest looking at OpenDNS's free "Home" solution, you can use it with custom lists. But as I mentioned above, you should also block all other DNS traffic that isn't to your desired server.
For my home stuff, I opt for a slightly more advanced design. I allow DNS to my OpenDNS resolvers and I redirect all other DNS traffic to outside servers (like 8.8.8.8 and 1.1.1.1) to my OpenDNS servers. So, that ChromeCast HDMI dongle that really really wants to use 8.8.8.8, disregarding what it got in DHCP, will still get an answer - but it's from my OpenDNS solution because I destination NAT'd all DNS traffic to my preferred server.
The main reason you would rely on your gateway to forward/relay DNS requests is because you're trying some type of monitoring/blocking setup in the router and it needs that for the filtering insight. If you aren't filtering there, then don't add the relay function to the router's list of responsibilities, let the clients query the provider's DNS directly.
In order for the local gateway's filtering to be successsful, you'd need it to also block all other DNS requests to outside servers. If you don't, this filtering setup is easily bypassed by a client specifying an outside DNS server. I would note that this is a common tactic for infected systems, change the preferred DNS to complete/maintain the infection.
If you want DNS filtering, I'd suggest looking at OpenDNS's free "Home" solution, you can use it with custom lists. But as I mentioned above, you should also block all other DNS traffic that isn't to your desired server.
For my home stuff, I opt for a slightly more advanced design. I allow DNS to my OpenDNS resolvers and I redirect all other DNS traffic to outside servers (like 8.8.8.8 and 1.1.1.1) to my OpenDNS servers. So, that ChromeCast HDMI dongle that really really wants to use 8.8.8.8, disregarding what it got in DHCP, will still get an answer - but it's from my OpenDNS solution because I destination NAT'd all DNS traffic to my preferred server.
I walked someone via phone to setup the DNS and turn off WIFI on a second computer at the church and while after the DNS was setup she could still ping 8.8.8.8 she could not ping ping.ui.com.
I forgot to have her do the netsh command first and reboot so maybe that was why.
I forgot to have her do the netsh command first and reboot so maybe that was why.
I forgot to have her do the netsh command first and reboot so maybe that was why.
I walked someone via phone to setup the manual DNS and turn off WIFI on a second computer at the church and while after the DNS was setup she could still ping 8.8.8.8 she could not ping ping.ui.com.
I forgot to have her do the netsh command first and reboot so maybe that was why.
So the one computer I thought I had fixed so it could use a wired connection had an issue with programming keyfobs using WinDSX. I only had 8.8.8.8 and 8.8.4.4.
Maybe I need 192.168.1.1 after the 8.8.4.4 or instead of 8.8.4.4. I think I only have space for a primary and alternate.
Maybe I need 192.168.1.1 after the 8.8.4.4 or instead of 8.8.4.4. I think I only have space for a primary and alternate.
No
How about if this DSX access control software has registered itself to a local DNS at the church. I am reading through about DSX. Not sure it does.
Similar threads
