Announcement

Collapse
No announcement yet.

Outlook won't connect to Exchange

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Outlook won't connect to Exchange

    Yesterday I installed GFI's MailEssentials and MailSecurity only to reboot and notice that Outlook could not communicate with Exchange. I can easily get to all my emails through OWA, but some users really don't like it too much and we'd much rather use Outlook. I keep getting the 0x8004011D connection errors and nothing I have found works. Taking cached mode off Outlook won't even let me bring up Outlook, as well as creating a new profile. I eventually uninstalled both products figuring one of them was giving me a problem. At this point nothing works and there is nothing out there is really helping me. GFI support says they can't help and I'll have to pay MS an I doubt they'll be able to fix it. Is a reinstall in order? I hope not

  • #2
    Re: Outlook won't connect to Exchange

    Are you 100% sure it was one of their products? I've had some good experience with them in the past. Any other direction worth lookig at?
    Cheers,

    Daniel Petri
    Microsoft Senior Premier Field Engineer
    MCSA/E, MCTS, MCITP, MCT

    Comment


    • #3
      Re: Outlook won't connect to Exchange

      Have a look here and see if that helps. http://forums.petri.com/showthread.php?t=2945
      11 was a racehorse.
      22 was 12
      1111 race 1 day
      22112


      ************************************************** * ************************************************** ***********
      ** Remember to give credit where credit is due and click the LIKE option in the bottom right corner **
      ************************************************** ************************************************** ****** * *****

      Comment


      • #4
        Re: Outlook won't connect to Exchange

        Daniel: Those were the only two things I installed 2 days ago, I didn't figured I'd have this much trouble. I've only heard good things about GFI products. I could guess it's some authentication error since I can do absolutely everything besides use Outlook to connect.

        Biggles77: I saw your post about this yesterday or Wed evening and I tried doing that but I was without any luck. It sounds just like what I was having.

        My client machine get some Event ID's.

        I also keep getting Event ID's 3019 (MrxSmb) The redirector failed to determine the connection type.

        and 40961 (LsaSrv) The Security System could not establish a secured connection with the server cifs/exchange. No authentication protocol was available.

        I'm trying to see why the authentication methods have become crazy. I tried joining the exchange domain with another laptop and I get DNS Name does not exist, so I'm tracking this down slowly, but it's still weird GFI products could do this.

        I think the cause is more along the lines of the 40961, but I've found nothing to assist me with this. I really don't want to reinstall the server, but I've got my bosses breathing down my neck because they want Outlook to work and a few people in the office are a bit upset they can't click on a stupid email link to send an email and copy and pasting is wasting too much time... riiiiighht.

        Comment


        • #5
          Re: Outlook won't connect to Exchange

          So since I tracked this down to the DNS on the Exchange server, this is very odd.

          If I open my DNS snap in and open up my FLZ, I have _msdcs.DOMAIN.local and DOMAIN.local. Which is odd... my _msdcs folder has somehow moved OUTSIDE of my DOMAIN.local area. If I goto _msdcs under DOMAIN.local it's only got one entry, NS.

          Now I gotta figure out how to move my records from _msdcs.DOMAIN.local to the _msdcs folder under DOMAIN.local.

          Comment


          • #6
            Re: Outlook won't connect to Exchange

            I had the same on my home/test domain. I had just completed the TrainSignal CBT on DNS and I wanted to try things on a "live" domain, so I just deleted the zone and created a new one. When Daniel stops cringing he will most likely tell you that is NOT the ideal thing to do in a production environment.
            11 was a racehorse.
            22 was 12
            1111 race 1 day
            22112


            ************************************************** * ************************************************** ***********
            ** Remember to give credit where credit is due and click the LIKE option in the bottom right corner **
            ************************************************** ************************************************** ****** * *****

            Comment


            • #7
              Re: Outlook won't connect to Exchange

              In Win2003 AD and DNS it is quite normal to have the MSDCS namespace as an external zone, and not as a subdomain of your primary zone. This is usualy done in large enterprises where there are more than one AD domains.

              I suggest you check that the MSDCS zone is enabled for dymanic updates, then restart the NETLOGON service on all DCs.

              If this feels wrong and you only have one domain and would like to have the MSDCS subdomain under your domain zone, just delete it, delete the delegation under your normal zone, and then re-create it (make sure you have the right name) under the domain name zone. Restart NETLOGON on all DCs.

              Again, I don't think you need to do that, and I'm not sure if that will solve your issues, but it's worth trying.
              Cheers,

              Daniel Petri
              Microsoft Senior Premier Field Engineer
              MCSA/E, MCTS, MCITP, MCT

              Comment


              • #8
                Re: Outlook won't connect to Exchange

                Thanks for everything, but nothing has seemed to work. I guess I happened to get the craziest problems, especially ones without a clear solution. I guess I should get to backing up everything so I can reinstall :/ Not my idea of a fun weekend.

                Comment


                • #9
                  Re: Outlook won't connect to Exchange

                  Hi,

                  The following url may help:

                  http://support.microsoft.com/default...b;en-us;327291

                  I cannot see how the GFI products could have caused this problem. It seems to be just a coincidence.

                  Regards,
                  Nicholas Sciberras
                  GFI Software Ltd - http://www.gfi.com

                  Comment


                  • #10
                    Re: Outlook won't connect to Exchange

                    I have come across this problem more than once of recent and haven't seen a single answer that worked well. Thus, I will post what has worked for me:

                    I determined the problem to be with DNS issues, particularly where you have an Exchange server at a different address than the web server.

                    For instance:

                    Say that your website (http://myboguswebsite.com) is hosted on a server at 209.15.133.19 but your local system hosts an Exchange server (http://mail.myboguswebsite.com) at 65.44.211.179, small changes to the DNS entries can cause this to occur.

                    For instance, installing a global trap of *.myboguswebsite.com pointing everything to 209.15.133.19 may change this.

                    Here's a workaround on Windows machines:

                    You need to make a change to your HOSTS file. To do this:

                    1) Open Windows Explorer (NOT Internet Explorer - d'oh!) and navigate to: c:\windows\system32\drivers\etc

                    2) Locate the HOSTS file (note, there is no extension!) and open it in NotePad.

                    3) Below the line that reads:

                    127.0.0.1 localhost

                    Enter a line for your exchange server with the LOCAL, INTERNAL IP address - NOT the outside address. For example, if your internal network's IP scheme is 192.168.0.x and your Exchange server is located at .252, and is known on the network as "MailMan", your entry will look like this:

                    127.0.0.1 localhost
                    192.168.0.252 MailMan

                    (NOTE: DO NOT use the external address of: 65.44.211.179!)

                    4) Save this file and restart Outlook. It should now work correctly.

                    Hope that helps everyone - especially me when I go looking for an answer to this error again and can't remember what I did before!

                    Comment


                    • #11
                      Re: Outlook won't connect to Exchange

                      Originally posted by dwneder View Post
                      I have come across this problem more than once of recent and haven't seen a single answer that worked well. Thus, I will post what has worked for me:

                      I determined the problem to be with DNS issues, particularly where you have an Exchange server at a different address than the web server.

                      For instance:

                      Say that your website (http://myboguswebsite.com) is hosted on a server at 209.15.133.19 but your local system hosts an Exchange server (http://mail.myboguswebsite.com) at 65.44.211.179, small changes to the DNS entries can cause this to occur.

                      For instance, installing a global trap of *.myboguswebsite.com pointing everything to 209.15.133.19 may change this.

                      Here's a workaround on Windows machines:

                      You need to make a change to your HOSTS file. To do this:

                      1) Open Windows Explorer (NOT Internet Explorer - d'oh!) and navigate to: c:\windows\system32\drivers\etc

                      2) Locate the HOSTS file (note, there is no extension!) and open it in NotePad.

                      3) Below the line that reads:

                      127.0.0.1 localhost

                      Enter a line for your exchange server with the LOCAL, INTERNAL IP address - NOT the outside address. For example, if your internal network's IP scheme is 192.168.0.x and your Exchange server is located at .252, and is known on the network as "MailMan", your entry will look like this:

                      127.0.0.1 localhost
                      192.168.0.252 MailMan

                      (NOTE: DO NOT use the external address of: 65.44.211.179!)

                      4) Save this file and restart Outlook. It should now work correctly.

                      Hope that helps everyone - especially me when I go looking for an answer to this error again and can't remember what I did before!
                      Thanks for your input. Great post but the initial article is almost 2 years old.

                      Comment

                      Working...
                      X