1 Rookie

 • 

13 Posts

1465

March 1st, 2022 16:00

RT10 & RT11 WiFi Problems With Some IPv6 Sites

I have a R11 purched in December 2020 with a R10 purchased in December 2021 and I never really used the R11 much, but 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. 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. 

Rapid reapeted Ctrl+F5 may load the file. 

Chrome will say "This site can’t be reached The connection was reset." ERR_CONNECTION_RESET and Firefox "Secure Connection Failed" PR_CONNECT_RESET_ERROR. 

If I try to load a page that hs the js file as an include in the header, the console on Chrome says "GET https://code.jquery.com/jquery-3.4.1.min.js net::ERR_CONNECTION_RESET" while FireFox says "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://code.jquery.com/jquery-3.4.1.min.js. (Reason: CORS request did not succeed). Status code: (null)."

The R10 has a Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW) running Windows 11.

The R11 has a Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) running Windows 10.

They are both running in 802.11ac, although I can force them into older protocols with no luck. 

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

There is a thread about this here https://github.com/jquery/codeorigin.jquery.com/issues/80 where 2 others have said they have Dell computers with the same problem. You might gain more insight into the trouble on that thread. 

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.

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

Another odd problem is that sites I have no problems with, if they are IPv6 and are reachable, will timeout on the first ping hit and then are successful on the other 4. I can ping again and it then will be successful on the first ping. A while later it may fail again on the 1st ping. This does not happen on my old HP desktop. 

Does anyone know how to fix this? 

1 Rookie

 • 

13 Posts

March 5th, 2022 01:00

Removing the Killer Control Panel or the drivers to load Microsoft provided drivers leaves the "Killer Network Service" installed and running. This is even installed by Windows 10 Updates on a new installation. 

The solution is to stop "Killer Network Service" and set it to manual or disabled with the Services window (services.msc). It can be delete via the Command Prompt and the "SC" command. 

Also, I should ad, this is not a Wi-Fi only problem, this can cause you problems on ethernet too when trying to access some IPv6 sites. 

8 Wizard

 • 

17.1K Posts

March 1st, 2022 17:00


@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 Rookie

 • 

13 Posts

March 1st, 2022 19:00

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. 

 

8 Wizard

 • 

17.1K Posts

March 1st, 2022 20:00


@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.

1 Rookie

 • 

13 Posts

March 2nd, 2022 15:00

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.

10 Elder

 • 

274.2K Posts

May 5th, 2023 00:00

I have fixed my problem by resetting IPv6 and Winsock.

No Events found!

Top