Sysinternal static Links need to be updated

Sysinternal static Links need to be updated

Postby risk » 13.02.2017, 02:44

I downloaded the latest version of WSUS Offline, "29.01.2017 Version 10.9.1 released. See Download area." However the Sysinternal static list pointed to:

Code: Select all
https://download.sysinternals.com/files


It needs to be updated to:

Code: Select all
https://live.sysinternals.com/files


WSUS Offline started working after I changed this. I only got a gist of this because of a past update where they changed the names to have capital first letters or vice versa.
risk
 
Posts: 2
Joined: 13.02.2017, 02:40

Re: Sysinternal static Links need to be updated

Postby Gerby » 13.02.2017, 15:53

Hello risk,

the download links for the Sysinternals tools in WOU version 10.9.1 don't use the secured https but http for the links. They also did not include https ever before.

trac.wsusoffline.net/browser/tags/wsusoffline10.9.1/static/StaticDownloadLinks-sysinternals.txt

Those links work just fine.

Did you adjust the file in any way?

Greetz
Gerby
Mach mit - der Übersichtlichkeit wegen! Füge Log-Auszüge als [Code] ein.
Make it clear! Insert log excerpts as [Code].
Gerby
 
Posts: 435
Joined: 11.09.2009, 15:57
Location: DE > SH > SE

Re: Sysinternal static Links need to be updated

Postby risk » 13.02.2017, 20:43

Hi Gerby,

I had to modify my own static links to live.sysinternals.com as download.sysinternals.com sends me nowhere.

Code: Select all
C:\Users\Risk>ping download.sysinternals.com

Pinging cs9.wpc.v0cdn.net [72.21.81.200] with 32 bytes of data:
General failure.
General failure.

Ping statistics for 72.21.81.200:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\Risk>ping live.sysinternals.com

Pinging live.sysinternals.com [191.236.128.229] with 32 bytes of data:
Request timed out.
Request timed out.
risk
 
Posts: 2
Joined: 13.02.2017, 02:40

Re: Sysinternal static Links need to be updated

Postby boco » 13.02.2017, 21:51

Strange server, but definitely reachable via IPv4. IPv6 is 3 of 4 (maybe the reason for Bad Gateway errors)

Code: Select all
C:\>ping download.sysinternals.com -4

Pinging cs9.wpc.v0cdn.net [93.184.221.200] with 32 bytes of data:
Reply from 93.184.221.200: bytes=32 time=30ms TTL=57
Reply from 93.184.221.200: bytes=32 time=21ms TTL=57
Reply from 93.184.221.200: bytes=32 time=25ms TTL=57
Reply from 93.184.221.200: bytes=32 time=35ms TTL=57

Ping statistics for 93.184.221.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 35ms, Average = 27ms

C:\>ping download.sysinternals.com

Pinging cs9.wpc.v0cdn.net [2606:2800:133:206e:1315:22a5:2006:24fd] with 32 bytes of data:
Request timed out.
Reply from 2606:2800:133:206e:1315:22a5:2006:24fd: time=23ms
Reply from 2606:2800:133:206e:1315:22a5:2006:24fd: time=29ms
Reply from 2606:2800:133:206e:1315:22a5:2006:24fd: time=26ms

Ping statistics for 2606:2800:133:206e:1315:22a5:2006:24fd:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 29ms, Average = 26ms

C:\>


The other server probably blocks ICMPv4 and is IPv4-only.

Code: Select all
C:\>ping live.sysinternals.com

Pinging live.sysinternals.com [191.236.128.229] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 191.236.128.229:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>


Looks like server to be used is a case of one's own location, after all. The global net is a complex beast...


Ping for the General Failure address above:
Code: Select all
C:\>ping 72.21.81.200

Pinging 72.21.81.200 with 32 bytes of data:
Reply from 72.21.81.200: bytes=32 time=201ms TTL=50
Reply from 72.21.81.200: bytes=32 time=131ms TTL=50
Reply from 72.21.81.200: bytes=32 time=153ms TTL=50
Reply from 72.21.81.200: bytes=32 time=151ms TTL=50

Ping statistics for 72.21.81.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 131ms, Maximum = 201ms, Average = 159ms
Microsoft update catalog: http://catalog.update.microsoft.com/v7/site/
Windows Install media creator: https://support.microsoft.com/en-us/help/15088/windows-create-installation-media
boco
 
Posts: 1780
Joined: 24.11.2009, 17:00
Location: Germany


Return to Anregungen / Suggestions

Who is online

Users browsing this forum: Baidu [Spider] and 5 guests