---

@MackSix wrote:

I am using the R10 a lot and I am experience a problem with accessing https://code.jquery.com/jquery-3.4.1.min.js via their IPv6 addresses.

1. I have to put a IPv4 address in my HOSTS file to force it to request the file via IPv4 so I don't have that trouble. 

2. The R10 has a Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW) running Windows 11. They are both running in 802.11ac, although I can force them into older protocols with no luck. 

3. I have updated the drivers from Intel on the R10 with no luck.

4. The AT&T router/wifi was installed only a few months ago and it works fine on my HP Desktop that I bought in 2017.

5. Being this happens on 2 similar Alienware desktop, it appears to be some sort of problem with the 2 desktops. 

---

I'm guessing you mean Aurora's .

1. No. Don't edit your HOST file.

2. Interesting you are not using an actual ethernet wire (disconnect from Access-Point).

3. Good.

4. Good test. However, be "really sure" it does work fine, otherwise we are troubleshooting under a false premise. Apparently, not in your case ... but often ... this kind of problem is usually the modem/router/residential-gateway/etc.

5. Uninstall all Killer-Networking (heavy driver-suite) non-sense . Then, delete the card(s) from Device-Manager. Reboot and let Windows Plug-and-Pray . It will detect and then use the Microsoft Broadcom drivers it tosses you. They are lean/fast and just work (which is what you need).

https://www.dell.com/community/XPS-Desktops/XPS-8930-Killer-E2400-Gigabit-Ethernet-stopped-working/m-p/8156140/highlight/true#M69383

1. Haha, don't worry, I know what I am doing.  

5. I just tried the Microsoft drivers v22.0.1.5. It made no difference. Going back to the Dell provided drivers. 

---

@MackSix wrote:

1. Haha, don't worry, I know what I am doing.  

5. I just tried the Microsoft drivers v22.0.1.5. It made no difference. Going back to the Dell provided drivers. 

 

---

1. What I mean is:

a. No one does that any more
b. It should not be required
c. Put it back to default and work toward fixing it the right way.

5. The "Dell provided drivers" and all that Killer-Networking stuff is really for local/client QoS . So, if you "know what you are doing" you would know that is suppose to be done at the router (or in your case, ISP-provided Residential-Gateway ... a combo-modem/router unit). The only reason you would want all that is if you had your computer connected directly to a simple cable/DSL modem (with no router). But again ... no-one does that these days.

Basically, it's not needed and this forum is full of instances where Killer-Networking and xTend (on Inspirons usually) does more hard than good.

Dell Engineers are looking at this. I spoke with their tech support and they remote controlled my desktop and saw the problem.

Since then, I have found the problem with this URL  when accessing IPv6.

$ dig AAAA 

; <<>> DiG 9.16.26 <<>> AAAA 
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21342
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
; IN AAAA

;; ANSWER SECTION:

153 IN CNAME 7cfz4.x.incapdns.net.
7cfz4.x.incapdns.net. 23 IN AAAA 2a02:e980:b1::b0

;; Query time: 44 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Mar 02 17:45:02 Central Standard Time 2022
;; MSG SIZE rcvd: 107

It will load if I reload it several times. It will then work until I delete the browser file cache and the cookies for it.

Again, I have not problems with my older HP desktop with these sites on the same Internet connection.

I have fixed my problem by resetting IPv6 and Winsock.