Fix: Outlook does not support connections to Exchange ActiveSync

While trying to connect your Outlook account with Exchange by using ActiveSync protocol the users may get the Outlook does not support connections to exchange by using ActiveSync error. This error is commonly caused if the Outlook does not support connection to a server that is running Exchange server. A similar discussion can also be read on the Microsoft Community forum.

On the same Windows 8 Pro machine, on the same user account – Windows Mail app is connected successfully to my corporate e-mail account (‘Outlook‘ account type, use SSL connection, domain and user name specified).

In Outlook 2013 the same account can’t be connected (selecting ‘ActiveSync’ account type, specifying server name and user name, however there are no options to specify SSL and domain) – getting error message ‘Log onto Exchange ActiveSync mail server (EAS): The server cannot be found.’

Follow the steps listed in the article below to fix Outlook server issue with ActiveSync and Exchange.

Is the Exchange Activesync supported by Outlook?

1. Connect to Exchange using Standard Exchange Connection

  1. Launch the Outlook desktop app.
  2. Click on File and then click on Add Account button.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  3. Enter your email address and click Connect.outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  4. Now you will be asked to enter your password again. Enter the password, and click OK.
  5. Click Finish to connect to exchange using standard exchange connection.
  6. Trying to set up your email account manually can create issues like the one mentioned earlier. Try to set up the email account normally and check if the error is resolved.

Deal with spam mails for good with these Exchange anti-spam software for Exchange email server.


2. Configure Outlook 2013 / 2016 Manually

  1. If you want to configure Outlook for Exchange by using ActiveSync do the following.
  2. Launch the Outlook desktop client.
  3. Choose “New Email Account“.
  4. Select “Manual setup or additional server types“.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  5. Select “Exchange ActiveSync“.
  6. Now you need to fill in the server setting. The username can be in Domainusername format.
  7. Now press and hold the Enter key on the Keyboard until all the boxes go away.
  8. Once the connection goes through. Launch the Outlook client and check if the error is resolved.

For Outlook 2016 / Office 365

  1. Launch the Outlook client in your Windows system.
  2. Click on File and select Add Account.
  3. Now enter the email address for the account and click the Advanced Options.
  4. Select “Let me set up my account manually” option.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  5. Click the Connect button.
  6. Select “Exchange” option.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  7. Enter the password for your ID and check if the connection is established without any error.

The EAS protocol provides access to data in exchange mailboxes thus keeping all of your connected devices in sync. Since EAS connection does not provide all the features of an Exchange account, Outlook does not support this method resulting in the error.

RELATED STORIES YOU MAY LIKE:

Related:

  • No Related Posts

Monitor for Load Balanced XML Servers Through NetScaler Fails with Error: “Ticket tag not found in response”

Users cannot log on multiple times a day and NetScaler XML monitor shows the following logs:

19483 0 PPE-0 MonServiceBinding_10.20.30.13:8080_(http_xml)(svcg_xml?storefront01.example.com?8080): DOWN; Last response: Failure - TicketTag not found in the response. Sun Oct 17 04:36:17 201519493 7 PPE-0 MonServiceBinding_10.20.30.13:8080_(http_xml)(svcg_xml?storefront01.example.com?8080): UP; Last response: Success - TicketTag found in the response. Sun Oct 17 04:36:47 201519494 0 PPE-0 'server_serviceGroup_NSSVC_HTTP_10.20.30.13:8080(svcg_xml?storefront01.example.com?8080)' UP Sun Oct 17 04:36:47 201519496 0 PPE-0 'server_serviceGroup_NSSVC_HTTP_10.20.32.13:8080(svcg_xml?storefront02.example.com?8080)' DOWN Sun Oct 17 04:38:56 201519497 35 PPE-0 MonServiceBinding_10.20.30.13:8080_(http_xml)(svcg_xml?storefront01.example.com?8080): DOWN; Last response: Failure - TCP connection successful, but application timed out Sun Oct 17 04:39:34 2015[…]19508 14 PPE-0 MonServiceBinding_10.20.30.13:8080_(http_xml)(svcg_xml?storefront01.example.com?8080): UP; Last response: Success - TicketTag found in the response. Sun Oct 17 04:41:33 201519509 0 PPE-0 'server_serviceGroup_NSSVC_HTTP_10.20.30.13:8080(svcg_xml?storefront01.example.com?8080)' UP Sun Oct 17 04:41:33 2015In NetScaler traces you can observe a reset getting sent with reset code 9701.

9700 – NSDBG_RST_PASS

This code indicates that the NetScaler appliance receives a TCP RST code from either the client or the server, and is transferring it. For example, the back end server sends a RST code, and the NetScaler appliance forwards it to the client with this code.

9701 – NSDBG_RST_NEST/NSDBG_RST_ACK_PASS

In NetScaler software release 9.1 and the later this code indicates that a RST code was forwarded as in the preceding RST code 9700, and the ACK flag was also set.

Related:

  • No Related Posts

Cisco IOS Software Precision Time Protocol Denial of Service Vulnerability

A vulnerability in the Precision Time Protocol (PTP) subsystem of Cisco IOS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition of the Precision Time Protocol.

The vulnerability is due to insufficient processing of PTP packets. An attacker could exploit this vulnerability by sending a custom PTP packet to, or through, an affected device. A successful exploit could allow the attacker to cause a DoS condition for the PTP subsystem, resulting in time synchronization issues across the network.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

This advisory is available at the following link:
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180926-ptp

This advisory is part of the September 26, 2018, release of the Cisco IOS and IOS XE Software Security Advisory Bundled Publication, which includes 12 Cisco Security Advisories that describe 13 vulnerabilities. For a complete list of the advisories and links to them, see Cisco Event Response: September 2018 Semiannual Cisco IOS and IOS XE Software Security Advisory Bundled Publication.

Security Impact Rating: High

CVE: CVE-2018-0473

Related:

  • No Related Posts

Failover issues with SGOS on ESX and Cisco

I need a solution

Hi there,

I’m having an issue with failover on two virtualized Symantec ( Bluecoat) proxies on two ESX hosts in two datacenters connected with Cisco switches.

I can see the Mulicast traffice leaving the proxy getting out into the world over the Cisco switches till the firewall blocks them. The packets should be delivered on L2 to the other switch to get into the other ESX-host on the other proxy running there.

But on the other host I don’t see any multicast-traffic incoming. Hence both feel responsible for the virtual IP what makes problems with Skype etc.

Did anyone have such an issue before? On ESX we activated promiscuous mode already for that vlan/subnet. But that didn’t change the issue.

The hardware proxies in the same network see the multicast-traffic incoming from the virtual machines and behave accordingly. As the virtual proxies don’t receive any multicast traffic they always assume to be master as the other one is not sending any updates.

I would understand that there might be an issue between the two Cisco-Switches that multicast traffic is not forwarded to the other. Other idea is – that there is a special setting on the ESX-Machine I’m not aware of? Any idea?

Thanks in advance,

Manfred

0

Related:

  • No Related Posts

NetScaler Gateway : EPA scan slowness on Windows 10 build 1809

There is a known EPA slowness issue in Windows10(1809).

EPA plugin uses a third party tool OPSWAT to do EPA scan. The issue is fixed in OPSWAT 4.0. Due to code layout, NetScaler 11.1 is only compatible with OPSWAT 3.0.

NetScaler 12.0 and NetScaler 12.1 are compatible with OPSWAT 4.0. So to fix the issue, we can downgrade the windows build version or upgrade the NetScaler to the fixed build.

Related:

  • No Related Posts

Ghost multicast Server to client negotiation

I need a solution

Hi,

we are using ghost server to multi clients using multicast.

Just a question on bandwidth and communication.

When the image is being transferred my understanding is that the communication is via udp.

Does anyone know how the client server communication for setup works?

Also what determines the max transfer speed? I know this is the slowest client but how does this

client communicate the speed it is happy with to the server, is this again tcp?

Is there a tcp “management” stream between client and server checking for variations in speed capabilities?

Any help or if anyone knows where to find it much appreciated.

0

Related:

  • No Related Posts