12-08-2017 03:37 PM
12-08-2017 03:37 PM
I'm happy to announce we have just released an updated Network Assessment Tool for Skype for Business and Microsoft Teams. Download link is: https://www.microsoft.com/en-us/download/details.aspx?id=53885 (version 2017.1.0.51)
This new version has the following new features:
Refer to the usage.docx file included with the tool for usage/etc.
Important: Starting around 12/15, older versions of the tool may stop working and will report an issue with the relay configuration. Please update accordingly.
The download site takes a few hours to replicate, so if the link doesn't work today (12/8), pleased try again in a few hours.
12-09-2017 06:23 AM
12-10-2017 03:03 AM
I can't find the usage.docx ? It only downloaded the .exe ?
12-10-2017 01:18 PM
Connectivity tests to the real services will be really useful in environments where the firewall is locked down. Great that it goes and pulls the current IP's and FQDNs to catch changes over time.
I did a quick hands-on blog post here: http://tomtalks.uk/2017/12/updated-free-sfbo-microsoft-teams-network-assessment-tool-added-connectiv...
12-10-2017 01:19 PM
The EXE installs to a file path that has the usage.docx. check out this blog for a quick overview: http://tomtalks.uk/2017/12/updated-free-sfbo-microsoft-teams-network-assessment-tool-added-connectiv...
12-10-2017 04:33 PM
Is this purely for Skype for Business Online? It would be good to make sure the word 'Online' is used as I often find things related to SfB to find out they're Online only.
12-10-2017 09:37 PM
Looks great! We were waiting for this :)
One point, do we have option to check what all IPs it tested during connectivity checks? I can only see two lines:
Starting Connectivity checks
Verifications completed successfully
12-11-2017 07:40 AM
The IP's are not surfaced in the tool, but I agree to see them would be cool.
If you are interested you can trace them with wireshark/NetMon - I took a screenshot in my blog post
12-11-2017 07:50 AM
Thanks for response.
I got what I was looking for using following command:
NetworkAssessmentTool.exe /Connectivitycheck /verbose
I can see list of IPs which were checked during connectivity check with port number.
12-11-2017 01:16 PM
Those IP addresses are the Transport Relay anycast ip addresses. I'm trying to understand why you are trying to achieve with change your relay.ip to your CCE Edge.
12-15-2017 11:01 AM
I was helping a customer troubleshoot with this today and comparing the results with running it on my computer. I noticed that not all the IPs listed on the Office 365 IPs and URLs support page appear when testing the tool. In fact, it seemed the customer would get a different set than I would get. Any reason why not all the IPs would be tested?
12-18-2017 05:22 AM - edited 12-18-2017 05:23 AM
The current version of this tool appears to be very broken; after changing the number of iterations to the desired amount (2000 in the below example), only about one quarter of the results are processed with the results analyser - the rest are skipped.
Looking at the source results file, it's clear that only tests with around 850 packets sent / received are processed, and that any tests with around 280 packets sent / received are skipped;
I've tested this thoroughly and can see no logic as to why it utilises 250ish packets sometimes, and 850ish others. This isn't a configurable variable.
Any chance of getting this fixed?
01-18-2018 02:48 PM
01-19-2018 08:06 AM
I have noticed the same issue with tests being run with either 250-ish or 850-ish packets in a 3:1-ish ratio. I was thinking this was potentially an indication of an issue with my ISP but now seeing this reported by someone else I too wonder if it's an issue with the tool.
01-19-2018 08:20 AM
+1 to issues with the new version. Several attempts on multiple machines results in 283 packets sent/received. When trying to use resultsanalyzer, it claims:
"Error: No data in input file. Please check that at least one record exists."
This is despite the fact that the TSV file has 10 rows of data.
For attempts that result in 800+ packets (851 seems to be the magic number for perfect), resultsanalyzer will skip rows with 283 packets sent/received. I've tried modifying the relay IP to several different ones (18.104.22.168, 22.214.171.124, 126.96.36.199, and 188.8.131.52) and results don't improve.
Is this a tool issue? Or a relay issue? Seems to be the former...
01-19-2018 12:55 PM
01-19-2018 12:57 PM
01-19-2018 12:58 PM
01-19-2018 12:59 PM
01-19-2018 01:06 PM
@William Looney - greatly appreciate the update. Any rough ETA on when we can expect the fix? Weeks? A month? Longer?
01-19-2018 01:21 PM
02-02-2018 07:01 AM
Same case as Trevor
Maybe a tool that may become useful after some update one day ?
or another tool for network assessment is in preparation somewhere ?
By the way, I notice there are plenty of Microsoft tools checking O365 needs, but I'm not sure if one is really working. If there is one to use, which one is it as I'm lost between all tools that are not working, deprecated, abandoned, ... ?
02-07-2018 05:18 AM
Question - Any update on new version ETA?
Additional issue below:
The "/connectivitycheck" param appears to query for hosts in five domains:
Problems with this are as follows:
I cannot overstate how disappointing and frustrating it is for partners and customers to have to deal with these issues. Even more frustrating is the fact that we're now nearing two months since the version was released with no updates to fix the initial issues.
Please, please, PLEASE, get these issues (both technical and documentation) fixed ASAP.
02-08-2018 06:15 AM
02-20-2018 07:58 AM
Opened a ticket with MSP and pressing on this question.
03-08-2018 10:51 AM
Microsoft has released the update for the Network Assessment Tool on March 5th. It is version 184.108.40.206.
It's at the regular download page:
Has anyone had a chance to try it out yet?
03-08-2018 12:39 PM
Initial issue encountered was that attempting to install the new version over an existing version (if there was already an existing version installed) resulted in the new version bits never being installed. The NTFS timestamps on all the files remained showing the Dec version. Using the assessment tool after the attempted install also resulted in the same issues already listed in the thread.
As of today, I uninstalled the Dec version. Then installed the new Mar version and thus far I have not had issues with packet sent/received being reported as 283. All of my smoke-tests today have been positive, with packets sent/received being reported as >848.
03-09-2018 09:31 AM
On the *.broker.skype.com, MS is looking into reconciling the tool and/or the URL/IP for Office 365. No date given yet.
03-12-2018 02:39 AM
I can confirm that uninstalling and reinstalling seems to have fixed the 283 packets bug. Thanks Trevor.
03-12-2018 10:41 AM
Microsoft has updated their Monthly URL and IP addresses for O365 to include *.cc.skype.com. This replaces any reference to *.broker.skype.com showing up with the SFBNA tool 1.1 There were no changes to network ranges for Teams.
Do we have change log available for latest release?
I do see initial connection request is changed. Old version was connecting to "s2s.config.skype.com" and new is connecting to "config.team.microsoft.com" to fetch media location.