Forum Discussion
Annoucement: Updated Network Assessment Tool released on 12/8 - added network connectivity checks
William Looney - greatly appreciate the update. Any rough ETA on when we can expect the fix? Weeks? A month? Longer?
- rovert506Feb 07, 2018Iron Contributor
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.
- Mark GarzaFeb 20, 2018Copper Contributor
Opened a ticket with MSP and pressing on this question.
- Mark GarzaMar 12, 2018Copper Contributor
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.
- 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.
- rovert506Jan 19, 2018Iron Contributor10-4. Thanks for letting me know!
- Philippe PiquereauFeb 02, 2018Copper Contributor
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, ... ?