Exchange online, post migration issues

%3CLINGO-SUB%20id%3D%22lingo-sub-556668%22%20slang%3D%22en-US%22%3EExchange%20online%2C%20post%20migration%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-556668%22%20slang%3D%22en-US%22%3EI'm%20not%20100%25%20sure%20if%20this%20is%20the%20correct%20section%20for%20this%2C%20but%20given%20I%20have%20no%20idea%20what%20the%20problem%20is!%20I%20thought%20I%20would%20start%20here.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20do%20IT%20work%20for%20a%20small%20charity%2C%20they%20were%20running%20POP%20email%20accounts%20with%20only%20local%20copies%20of%20emails.%20Services%20were%20provided%20by%20their%20web%20provider%20so%20we%20had%20no%20administration%20control%20over%20emails.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20migrated%20all%20emails%2C%20via%20PST%20upload%20to%20exchange%20online.%20Migration%20went%20well%2C%20all%20emails%20available%20and%20full%20send%2Freceive%20functionality%20post%20migration.%3CBR%20%2F%3E%3CBR%20%2F%3EHOWEVER!%20They%20can%20no%20longer%20access%20the%20website%20for%20their%20domain.%20For%20example%3A%20all%20email%20addresses%20associated%20with%20contoso.com%20are%20sending%2Freceiving%20fine.%20On%20their%203%20computer%20internal%20network%20they%20can%20no%20longer%20access%20%3CA%20href%3D%22http%3A%2F%2Fwww.contoso.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ewww.contoso.com%3C%2FA%3E.%20It%20simply%20times%20out%20and%20says%20website%20unavailable.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20network%20consists%20of%20a%20BT%20Business%20Broadband%20router%20(running%20DHCP)%2C%20a%20Synology%20DiskStation%20for%20data%20storage%20with%20a%20connected%20laser%20printer.%20Users%20log%20in%20with%20a%20local%20account%20on%20each%20computer.%20All%20computers%20running%20Windows%207.%3CBR%20%2F%3E%3CBR%20%2F%3EFull%20connectivity%20to%20other%20websites%20works%20fine.%20The%20website%20works%20fine%20outside%20the%20network.%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20I've%20done%20so%20far%3A%3CBR%20%2F%3Eping%20fails%3CBR%20%2F%3EFlushed%20DNS%20with%20IP%20config%3CBR%20%2F%3EChanged%20DNS%20servers%20to%20Google%20DNS%3CBR%20%2F%3EHost%20file%20is%20empty%3CBR%20%2F%3EFirewall%20on%2Foff%20-%20still%20fails%3CBR%20%2F%3EAV%20on%2Foff%20-%20still%20fails%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20works%3A%3CBR%20%2F%3EI've%20installed%20a%20VPN%20chrome%20extension%20that%20allows%20it%20to%20connect%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20question%20is...%20Is%20this%20just%20a%20horrible%20coincidence%20relating%20to%20the%20exchange%20migration%20(and%20I'm%20chasing%20down%20a%20never%20ending%20rabbit%20hole)%20or%20have%20I%20inadvertently%20changed%20something%20causing%20this%20to%20happen%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20pretty%20much%20run%20out%20of%20ideas%20so%20any%20suggestions%20gratefully%20received.%3CBR%20%2F%3E%3CBR%20%2F%3EJonathan%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-556668%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-558714%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20online%2C%20post%20migration%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-558714%22%20slang%3D%22en-US%22%3EExchange%20itself%20would%20have%20nothing%20to%20do%20with%20it%2C%20but%20most%20likely%20what%20did%20happen%2C%20someone%20changed%20the%20related%20DNS%20records%20for%20the%20domain%20when%20changing%20where%20the%20e-mail%20domain%20routes%20to.%20So%20your%20website%20DNS%20is%20most%20likely%20not%20correct.%20Need%20to%20find%20out%20what%20the%20IP%20should%20be%20and%20make%20sure%20it's%20resolving%20properly.%20Ping%20from%20local%2C%20and%20when%20it's%20working%20via%20VPN%2C%20see%20where%20it's%20pinging.%20If%20it's%20the%20same%2C%20and%20it%20works%20on%20VPN%2C%20then%20obviously%20there%20is%20some%20kind%20of%20IP%20blocking%20going%20on%20on%20the%20website%20or%20a%20device%20in%20between%20the%20site%20and%20you%20that%20is%20restricting%20certain%20IP's%20from%20connecting.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-560599%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20online%2C%20post%20migration%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-560599%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3Bthank%20you%20very%20much%20for%20taking%20the%20time%20to%20answer%2C%20it%20is%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wish%20I%20could%20say%20that%20your%20suggestion%20helped%2C%20but%20I%20think%20this%20was%20one%20of%20those%20gremlins%20that%20has%20no%20answer...%20because%20when%20I%20checked%20it%20today%20it%20is%20magically%20working%20again.%20I%20have%20not%20changed%20anything%20at%20all%2C%20and%20it%20was%20simply%20left%20for%204%20or%205%20days%20while%20I%20tried%20to%20come%20up%20with%20a%20solution%20and%20it%20is%20now%20working.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20only%20assume%20that%20there%20was%20some%20sort%20of%20DNS%20replication%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEither%20way%2C%20I%20now%20have%20happy%20users%20again.%20Thanks%20again.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor
I'm not 100% sure if this is the correct section for this, but given I have no idea what the problem is! I thought I would start here.

I do IT work for a small charity, they were running POP email accounts with only local copies of emails. Services were provided by their web provider so we had no administration control over emails.

I have migrated all emails, via PST upload to exchange online. Migration went well, all emails available and full send/receive functionality post migration.

HOWEVER! They can no longer access the website for their domain. For example: all email addresses associated with contoso.com are sending/receiving fine. On their 3 computer internal network they can no longer access www.contoso.com. It simply times out and says website unavailable.

The network consists of a BT Business Broadband router (running DHCP), a Synology DiskStation for data storage with a connected laser printer. Users log in with a local account on each computer. All computers running Windows 7.

Full connectivity to other websites works fine. The website works fine outside the network.

What I've done so far:
ping fails
Flushed DNS with IP config
Changed DNS servers to Google DNS
Host file is empty
Firewall on/off - still fails
AV on/off - still fails

What works:
I've installed a VPN chrome extension that allows it to connect

My question is... Is this just a horrible coincidence relating to the exchange migration (and I'm chasing down a never ending rabbit hole) or have I inadvertently changed something causing this to happen?

I've pretty much run out of ideas so any suggestions gratefully received.

Jonathan
2 Replies
Highlighted
Exchange itself would have nothing to do with it, but most likely what did happen, someone changed the related DNS records for the domain when changing where the e-mail domain routes to. So your website DNS is most likely not correct. Need to find out what the IP should be and make sure it's resolving properly. Ping from local, and when it's working via VPN, see where it's pinging. If it's the same, and it works on VPN, then obviously there is some kind of IP blocking going on on the website or a device in between the site and you that is restricting certain IP's from connecting.
Highlighted

@Chris Webb thank you very much for taking the time to answer, it is greatly appreciated.

 

I wish I could say that your suggestion helped, but I think this was one of those gremlins that has no answer... because when I checked it today it is magically working again. I have not changed anything at all, and it was simply left for 4 or 5 days while I tried to come up with a solution and it is now working.

 

I can only assume that there was some sort of DNS replication issue?

 

Either way, I now have happy users again. Thanks again.