Forum Discussion
MicrosoftAnnoucement: Updated Network Assessment Tool released on 12/8 - added network connectivity checks
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?
Kind regards
Ben
MicrosoftWilliam Looney - greatly appreciate the update. Any rough ETA on when we can expect the fix? Weeks? A month? Longer?
- William LooneyIts high priority on our list to get this release updated to address this and a couple other items of feedback we've received. I am not committing to a specific ETA or date, but I'm aiming for week or two provided everything goes well.
Question - Any update on new version ETA?
Additional issue below:
The "/connectivitycheck" param appears to query for hosts in five domains:
*.dc.trouter.io
*.msg.skype.com
*.broker.skype.com
*.cc.skype.com
*.conv.skype.comProblems with this are as follows:
- The domains bolded black are only listed as "Required" for Teams on the Office365 URL/IP support page. There is no mention at all of these domains for Skype4B. For organizations that adhere to strict DNS recursion configurations based off the Office365 URL/IP support page, when they are not deploying Teams and only Skype4B, the "/connectivitycheck" param flat out does not work.
- Note: The network assessment feature still works - albeit with the caveats listed in this thread - so that remains unchanged.
- The domain bolded red is not listed anywhere on the Office365 URL/IP support page. For organizations that adhere to strict DNS recursion configurations based off the Office365 URL/IP support page, this domain will not be available since it is not documented.
- Note: This domain isn't even listed anywhere in the RSS feed, either.
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.
- The domains bolded black are only listed as "Required" for Teams on the Office365 URL/IP support page. There is no mention at all of these domains for Skype4B. For organizations that adhere to strict DNS recursion configurations based off the Office365 URL/IP support page, when they are not deploying Teams and only Skype4B, the "/connectivitycheck" param flat out does not work.
