Forum Discussion
Incorrect Network Egress Location
Hi guys. I just stumbled on this new connectivity analyzer and was playing around with it. I'm seeing the same issue. We are on Comcast fiber in Elkridge, MD but it says our egress location is in Ninnescah, KS over 1,100 miles away.
- Dan RushOct 06, 2021Copper ContributorWe have been fighting this issue since Feb with Microsoft. They just say you need to set a local egress to fix this but there isn’t a person that has a clue on how to do this. Microsoft techs don’t want to help with the situation and they just blame someone else. If you look at the trace routes as soon as you hit the Microsoft network it takes you everywhere else but where it should be. They can’t even tell you how their tool is able to tell the location.
- PaulAndrewOct 06, 2021
Microsoft
Dan Rush We corrected the issues that Jason and John reported some time back. It was showing wrong locations for a small percentage of people. The location detection for the Microsoft 365 Admin Center network connectivity reporting is described on this doc page: https://docs.microsoft.com/en-us/Microsoft-365/Enterprise/office-365-network-mac-perf-overview
Regards,
Paul
- Dan RushOct 07, 2021Copper Contributor
PaulAndrew Hey Paul the issue we are having is strange. We have random users that experience the Office 365 apps that are open become unresponsive when a user replies to an email. This is completely random. Different times, days, users, systems, etc. All systems are on the lasted Office 365 and W10 builds. All drivers are fully up to date. The only way to shutdown the apps is to restart the system. Sometimes it takes up to 3 restarts before they can use any of the office applications.
We have been in contact with Microsoft support for over 6 months now. They have little to no help. Keep asking to run the Advanced S.A.R.A tool on the machine that is having the problem. Well to run this tool you have to be an Admin. Which defeats the purpose of using the tool. As soon as the user is logged our or restarts the system they can't reproduce the issue. The only thing support would tell us is they see packet loss. Which we resolved and then they said we need to setup local internet egress to help with latency since we are in Baltimore and our Egress is in Gig Harbor, Washington. Then back hauling to VA. When I asked how they came up with this the Tech took days to get back and gave no information. Then closed the ticket because we couldn't reproduce the issue within 24hrs.
We tried to reopen the ticket as well but no one responds to it. Open a new ticket and get a response and have to start all over with months of back and forth. Then they go oh you need to go back to your previous ticket to get support. Which no one ever replies.
I have worked with our ISP to verify connectivity. There was an issue with the fiber link being out of spec. That has been resolved. Worked with our MSP's Network Engineers and they can't find an issue with the network.
Appreciate any suggestions. This has been an absolute nightmare to figure out.