Tag Archives: Mobility

Lync Mobility: E_AuthError E2-3-2

17 Wednesday Jun 2015

Posted by in Error Codes, mobility

≈ Leave a comment

Tags

, ,

Issue

Lync Mobile Client won’t sign in.
Mobile client logs contain the error E_AuthError E2-3-2
Tests from testconnectivity.microsoft.com are successful.

NOTE
If the tests from testconnectivity.microsoft.com are unsuccessful then you may need to recheck the user credentials

Reviewing the logs from the mobile device you find the following error messages:-

  • 401 – Unauthorized: Access is denied due to invalid credentials.
  • You do not have permission to view this directory or page using the credentials that you supplied.
  • Received webticket resposne with status E_AuthError (E2-3-2)
  • Mapping error code = 0x22030002
  • Mapped error message is ‘We can’t sign you in. Please check your account info and try again.

Clearly there is some issue with your credentials.

If you go back to the testconnectivity.microsoft.com  site you will recall being prompted for Domain\User Name (or UPN)

Skype Mobile Connectivity failure

Cause and Resolution

The issue is that the mobile client does not require or prompt the user for the Domain\User Name (or UPN). The field is actually a little hidden and thus often overlooked. You can find it in Show Advanced Options.

Lync 2013 Mobile ApplicationWindows mobile Lync 2013 mobile UPN

TIP

If you enable UPN Naming for the user account and the SIP address is also the UPN address then the mobile user does not need to provide the User Name in Advanced options.

Lync Mobility: E_ConnectionError E2-2-1

08 Monday Jun 2015

Posted by in Uncategorized

≈ Leave a comment

Tags

,

Issue

Lync Mobile Client won’t sign in.
Mobile client logs contain the error E_ConnectionError E2-2-1
Tests from testconnectivity.microsoft.com are failing.

Lync Mobile Error E2-2-1

 What we do know from testconnectivity.microsoft.com:

  • the DNS record is resolving correctly
  • the TCP port 443 is allowing the connection
  • the SSL certificate seems to be OK

This means that we have made it onto the Reverse Proxy.

What appears to be failing is the jump from the Reverse Proxy to the Front End.

Following the Tell me more about this issue and how to resolve it link lands you on the following page

Mobitliy Issue E_ConnectionError (E2-2-1)

To be honest , that’s actually rather solid information from Microsoft..let us take a deeper look at this info

A Network Error Occurred while Communicating with Remote Host (Front End)

  • The server is down.
  • The specified port is not listening for TCP connections.
  • A firewall, proxy server, or hardware device is blocking the connection to your server.
  • The network is congested.

Resolution

So what the underlying issue here boils down to is that for some reason the traffic is not reaching the Front End Server from the Reverse Proxy.

Of course this could be that the Reverse Proxy is incorrectly configured.

From my experience, the most common causes in a new deployment are:-

  • Reverse Proxy cant resolve the host name for the Front End
  • Ports are blocked (from Reverse Proxy to Front End port 4443)
  • Forgot to port forward 443 to 4443 (or 80 to 8080) on the Reverse Proxy

TIP

The E2-2 errors usually refer to a connectivity issue. E2-2-1 generally means that the client couldn’t reach the destination.

Conclusion

When you get redirected to a hyperlink do take the time to consider the common causes. Who knows, you might even find the answer..