OWA not working on two machines

Office 2013 on home and laptop computer.  Home computer obvisouly external network, laptop computer is on network when at work.  Exchange 2013 is setup and my desktop computer at work also has Outlook 2013 with no issues.  No one else (so far) has reported any issues as well.

Activesync works, like iPhone, iPad, Windows Mail.

Outlook 2013 is just stuck in disconnected state.  I deleted my mail profile on my laptop and recreated it.  Autodiscover fills in all the information automatically but then I get "The name cannot be resolved.  The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action".  With wireshark, I see the traffic going to and from the internal Exchange server but I don't know what it is since its https tls 1.2, so its all encrypted data.

If I click OK on this dialog box, I see my GUID@domain.com for the exchange server which matches the working Outlook on my desktop.  What is different however is on the laptop, under mailbox it appended =SMTP: in front of my username@domain.com.  I clear this out and it still doesn't work.  It eventually asks for the password and I enter it in but nothing.

On home computer with the same initial issue, since I did not delete the mail profile yet I checked outlooks connection status and I just see my one server name GUID with a status of disconnected.

On my work desktop where outlook works, when I check outlook connection status I see the first line is disconnected, but the next 30 lines with different GUID's are all "Established".  I did a test autodiscover from off network (home) and on network (desktop) and no issue there, however msrca test outlook connectivity gives me an error 401 not authorized.

Any idea what to check and where to look first?

April 9th, 2015 9:50am

Oh I also tried renaming my profile on the laptop and logging in with a new profile (windows created a new  C:\users\username directory).  Still didn't work.

I uninstalled Office 2013 and reinstalled it.  Outlook still doesn't connect.

Wireshark indicates traffic is connecting but it says it cannot resolve the mailbox name when I manually tried typing in the long GUID for server (copied form working desktop pc).

Also if I go to https://autodiscover.domain.com/Autodiscover/Autodiscover.xml and put in my username and password in the prompt, I get the XML code with error code 600 in it, which from my understanding when viewing from a browser, this is normal.
  • Edited by KJSTech1 17 hours 28 minutes ago
Free Windows Admin Tool Kit Click here and download it now
April 9th, 2015 9:57am

Ok I got my home computer and laptop working.

I just closed outlook on my work destkop computer.  Remember I said it had 30+ guid's listed in Outlook's connection window?  Well a week ago we were migrating to room mailboxes, and I was giving myself full permissions to them so I could export a room calendar to a pst file, then import it back in to the new room mailboxes.  Well that was all done and I removed full access to those mailboxes in exchange, but for some reason my Outlook 2013 client still had all the GUID's listed.  I wonder if that imposed some sort of connection limit with my account and exchange (makes sense why no one else called about this type of issue).

So with outlook closed, in a few minutes I relaunched outlook on my home computer (I am connected via RDP right now) and it worked fine (only 5 GUID's showing in Outlook connection status).  I did a repair on my laptop's Outlook profile and it loaded fine as well.  7 GUID's are listed on the on-premise laptop outlook connection status and its downloading the mailbox as I type this.

msrca still gives this"An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN)." However I can ASSURE you autodiscover works as I tested both on premise and off premise Outlook 2013 test autodiscover feature.

April 9th, 2015 10:37am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics