cancel
Showing results for 
Search instead for 
Did you mean: 

NetSkope SWG and Windows 10 updates failing in Asia

bridge
New Contributor

Hi all, wondered if anyone rolling out SWG has had any issues with getting Windows updates to install with SWG enabled in Asia.   I have the same Windows steering bypasses set up for EU users and Asia but for some reason India and HK  users are getting a fail to update on the windows update page unless i disable the netskope client.   My exceptions are below.  I've covered everything MS say i need except go.microsoft.com and its not needed for EU users and just directs to the micosoft buy our devices  page.  Any ideas ?   

 

*.download.windowsupdate.com
*.update.microsoft.com
*.windowsupdate.com
*.windowsupdate.microsoft.com
dl.delivery.mp.microsoft.com
download.microsoft.com
ntservicepack.microsoft.com
r.manage.microsoft.com
windowsupdate.microsoft.com
wustat.windows.com

1 ACCEPTED SOLUTION
rthomson
Netskope
Netskope

My suggestion would be:

1. attempt the Windows update again

2. download the netkope client logs (right click -> save logs) and unzip.

3. look inside nsdebuglog.log

4. filter the nsdebuglog.log file for the word "Tunneling"

5. You should see a number of lines like:

 

Tunneling flow from addr: 192.168.1.51:56147, process: firefox to host: c1h-word-view-15.cdn.office.net, addr: 23.36.168.220:443 to nsProxy

 

Look for anything in there where the process is related to Microsoft Update, or where the host is a Microsoft related domain.

 

6. Add that process/host into the steering exceptions

 

View solution in original post

2 REPLIES 2
rthomson
Netskope
Netskope

My suggestion would be:

1. attempt the Windows update again

2. download the netkope client logs (right click -> save logs) and unzip.

3. look inside nsdebuglog.log

4. filter the nsdebuglog.log file for the word "Tunneling"

5. You should see a number of lines like:

 

Tunneling flow from addr: 192.168.1.51:56147, process: firefox to host: c1h-word-view-15.cdn.office.net, addr: 23.36.168.220:443 to nsProxy

 

Look for anything in there where the process is related to Microsoft Update, or where the host is a Microsoft related domain.

 

6. Add that process/host into the steering exceptions

 

issue wanted related to netskope.