Not that I can think of - there’s no anti-virus or MDM on the devices.
The majority of websites work, but there’s two distinct symptoms:
- Microsoft Teams and Spotify simply refuse to load, citing network errors.
- It’s pretty often that the first load of a page will fail and it requires a reload.
#2 was something that I thought was just a cursed device but it seems like others have encountered the same.
On WARP 2022.2.288, there are no issues (that I can spot).
Upgrading to WARP 2022.5.346 and I can reliably reproduce #2 just by browsing through a few websites - there is no error, just a simple “unable to connect” from Firefox.
On the off chance it was a Firefox specific issue, it is reproducible in other browsers.
However in Chrome, I can refresh here all day long and it’ll never get anywhere - citing --> net_error = -105 (ERR_NAME_NOT_RESOLVED)
t=906 [st= 0] +HOST_RESOLVER_MANAGER_JOB [dt=21]
--> dns_query_types = ["A"]
--> host = "www.reddit.com"
--> network_isolation_key = "null null"
--> secure_dns_mode = 1
--> source_dependency = 1623 (SSL_CONNECT_JOB)
t=906 [st= 0] HOST_RESOLVER_MANAGER_JOB_REQUEST_ATTACH
--> priority = "HIGHEST"
--> source_dependency = 1623 (SSL_CONNECT_JOB)
t=906 [st= 0] HOST_RESOLVER_MANAGER_JOB_STARTED
t=906 [st= 0] +HOST_RESOLVER_MANAGER_PROC_TASK [dt=21]
t=906 [st= 0] HOST_RESOLVER_MANAGER_ATTEMPT_STARTED
--> attempt_number = 1
t=927 [st=21] -HOST_RESOLVER_MANAGER_PROC_TASK
--> net_error = -105 (ERR_NAME_NOT_RESOLVED)
--> os_error = -5
--> os_error_string = "No address associated with hostname"
t=927 [st=21] HOST_RESOLVER_MANAGER_ATTEMPT_FINISHED
--> attempt_number = 1
--> net_error = -105 (ERR_NAME_NOT_RESOLVED)
--> os_error = -5
--> os_error_string = "No address associated with hostname"
t=927 [st=21] -HOST_RESOLVER_MANAGER_JOB
--> net_error = -105 (ERR_NAME_NOT_RESOLVED)
Trying to launch Microsoft Teams fills the Teams logs with similar net::ERR_NAME_NOT_RESOLVED errors.
Wed Jul 27 2022 20:04:18 GMT+0100 (British Summer Time) <424462> -- info -- OnErrorOccurred - Description: UnifiedPresenceService:PublishEndpoint Method: PUT Error: net::ERR_NAME_NOT_RESOLVED
There is slight differences in how the local DNS proxy & 1.1.1.1 return a lookup for the one of the URL’s it is having issues with, teams.microsoft.com
errorCode: -105, errorUrl: https://teams.microsoft.com, message: ERR_NAME_NOT_RESOLVED
;; QUESTION SECTION:
;teams.microsoft.com. IN A
;; ANSWER SECTION:
s-0005.s-msedge.net. 238 IN A 52.113.194.132
;; ADDITIONAL SECTION:
teams.microsoft.com. 259198 IN CNAME teams.office.com.
teams.office.com. 298 IN CNAME teams-mira-afd.trafficmanager.net.
teams-mira-afd.trafficmanager.net. 58 IN CNAME teams-office-com.s-0005.s-msedge.net.
teams-office-com.s-0005.s-msedge.net. 238 IN CNAME s-0005.s-msedge.net.
;; Query time: 16 msec
;; SERVER: 127.0.2.2#53(127.0.2.2) (UDP)
;; QUESTION SECTION:
;teams.microsoft.com. IN A
;; ANSWER SECTION:
teams.microsoft.com. 259188 IN CNAME teams.office.com.
teams.office.com. 288 IN CNAME teams-mira-afd.trafficmanager.net.
teams-mira-afd.trafficmanager.net. 48 IN CNAME teams-office-com.s-0005.s-msedge.net.
teams-office-com.s-0005.s-msedge.net. 228 IN CNAME s-0005.s-msedge.net.
s-0005.s-msedge.net. 228 IN A 52.113.194.132
;; Query time: 4 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
Albeit both end up returning the same IP
Spotify’s logs don’t give much information beyond http_error_fail but it is reproducible going to and from 2022.2 and 2022.5
The ID I received was 507979 - thanks for the help!
warp-diag is what we need in all cases.