Posted on by givenscj

Testing Office 365 Connectivity

Recently had a customer with an issue with accessing Office 365\SharePoint site.  They were complaining that the performance was not great.  So I needed to see what issues they might be having with their network.  Results were really interesting, they were being routed (via ATT) from SJC to CHI to NYC to DUB then back to LAX and finally to the US West data center in SJC.  Woah…that’s definitely not good!
Decided to write down all the tools I use and the script commands I execute to test a sites connectivity to Office 365.

  1. Fiddler
    1. Open a site collection, sort the HTTP requests by latency\execution time
  2. MeasurementLab tools
  3. Ping – Network level
  4. Tracert – Transport level
  5. WireShark – For really tough, weird things that don’t show up in regular network tools (Session, Transport issuse)

Services to ping:

  • Exchange
    • ping outlook.office365.com
      • Ensure you are getting the closest data center:
        • outlook-namcentral3.office365.com – 40.97.125.146
        • outlook-namnorthwest.office365.com – 40.97.134.178
        • outlook-apacsouth.office365.com – 40.100.17.34
        • outlook-emeawest.office365.com – 40.101.69.226
        • etc…
    •  SharePoint
      • Resolve-DnsName tenant.sharepoint.com
        • Determine DNS servers serving your requests
      • ping tenant.sharepoint.com -t
      • ping 104.146.168.28 (tenant.sharepoint.com)
        • Target latency = <100ms
      • ping 40.97.119.178 (outlook.office365.com)
        • Target latency = <50ms
  •  Skype
    • ping global.tr.skype.com
    • ping 13.107.8.2 -t
      • Target latency = <20ms
  • Azure
  • Other IPs

Services to tracert (use the db-ip.com service to find their locations):

  • tracert 13.107.8.2
  • tracert 40.97.119.178

Look up each ip along the way…to see if unnecessary routing is occurring.  If it is, then ISP needs to configure route to data center or customer needs to setup ExpressRoute.
https://db-ip.com/{IPADDRESS}
Painful Example:

  • 192.168.25.12 – local router (San Jose)
  • 12.251.115.241 – Chicago (ATT)
  • 12.122.110.58 – New York (ATT)
  • 12.122.163.34 – New York (ATT)
  • 12.122.158.9 – New York (ATT)
  • 104.44.9.183 – Dublin (Microsoft)
  • 104.44.4.105 – Los Angeles (Microsoft)
  • 104.44.4.102 – Los Angeles (Microsoft)
  • 104.44.9.215 – Los Angeles (Microsoft)
  • 40.97.119.178 – San Jose (Microsoft)

Helpful references:

Post Views: 469