Strange problem with Outlook 2007 on Vista not connecting to Exchange 2007
in [Microsoft Exchange]
|
From: rwvoss on 2 Sep 2009 17:23 On Aug 28, 7:36 pm, "Rich Matheisen [MVP]" <richn...(a)rmcons.com.NOSPAM.COM> wrote: > On Fri, 28 Aug 2009 12:45:44 -0700 (PDT), rwvoss <rwv...(a)gmail.com> > wrote: > > >I'm about to call Microsoft support, but I thought I would see if I > >could get any advice from here first. I have a user with an mailbox > >on an Exchange 2007 SP 1 server. She has a Vista workstation with > >Outlook 2007. When trying to set up a profile for her, I saw the two > >following errors: > > >The connection to Microsoft Exchange is unavailable. Outlook must be > >online or connected to complete this action. > > >The name cannot be resolved. The connection to Microsoft Exchange is > >unavailable. Outlook must be online or connected to complete this > >action. > > Are there any other applications running on the machine that use the > Outlook profile? Things like Microsoft Office Communicator, desktop > indexing software, etc.? They'll probably start before you try to make > the new profile and they'll keep the connection open to the server. > > DNS name resolution might be a problem, but you say the OWA works so > that's probably not the case. > > Since you have OL2007 and E2K7 you could have a problem with the CAS > role. Is this an error you get after you check the box to manually > configure the profile? > --- > Rich Matheisen > MCSE+I, Exchange MVP I will check and see if there is anything running on the workstation. The only thing it might be is an indexing program. They all have been Vista, so I don't think there will be anything more than the built in one though. They have the problem whether they try do you autodiscover or set it up manually. One update, it seems that the account that I did get working by disabling MAPI stopped working shortly after. However, I enabled MAPI again and she hasn't had a problem sense. I still have 2 other users that cannot set up outlook though. Thanks, Randy
From: rwvoss on 3 Sep 2009 16:49 On Sep 2, 4:23 pm, rwvoss <rwv...(a)gmail.com> wrote: > On Aug 28, 7:36 pm, "Rich Matheisen [MVP]" > > > > <richn...(a)rmcons.com.NOSPAM.COM> wrote: > > On Fri, 28 Aug 2009 12:45:44 -0700 (PDT), rwvoss <rwv...(a)gmail.com> > > wrote: > > > >I'm about to call Microsoft support, but I thought I would see if I > > >could get any advice from here first. I have a user with an mailbox > > >on an Exchange 2007 SP 1 server. She has a Vista workstation with > > >Outlook 2007. When trying to set up a profile for her, I saw the two > > >following errors: > > > >The connection to Microsoft Exchange is unavailable. Outlook must be > > >online or connected to complete this action. > > > >The name cannot be resolved. The connection to Microsoft Exchange is > > >unavailable. Outlook must be online or connected to complete this > > >action. > > > Are there any other applications running on the machine that use the > > Outlook profile? Things like Microsoft Office Communicator, desktop > > indexing software, etc.? They'll probably start before you try to make > > the new profile and they'll keep the connection open to the server. > > > DNS name resolution might be a problem, but you say the OWA works so > > that's probably not the case. > > > Since you have OL2007 and E2K7 you could have a problem with the CAS > > role. Is this an error you get after you check the box to manually > > configure the profile? > > --- > > Rich Matheisen > > MCSE+I, Exchange MVP > > I will check and see if there is anything running on the workstation. > The only thing it might be is an indexing program. They all have been > Vista, so I don't think there will be anything more than the built in > one though. They have the problem whether they try do you > autodiscover or set it up manually. > > One update, it seems that the account that I did get working by > disabling MAPI stopped working shortly after. However, I enabled MAPI > again and she hasn't had a problem sense. I still have 2 other users > that cannot set up outlook though. > > Thanks, > > Randy While researching another issue, I think I may have found part of my problem. Can anyone tell me what Outlook 2007 searches for when it tries to set up a mailbox profile with autodiscover? I thought it was just 'autodiscover.domain.tld' but I'm not sure I believe that any more. I used wireshark to look at network traffic while trying autodiscover off of my network with a workstation that was not part of the domain. In the capture I saw it looking for the following: mail.domain.tld pop.domain.tld pop3.domain.tld imap.domain.tld imap4.domain.tld There were no other programs running besides outlook and wireshark. The issue is mail.domain.tld is a valid address on our network for a iplanet mail server. I start to see communication with that server. Then I see that it looks for http://domian.tld/autodiscover/autodisocver.xml, which does not exist. The, finally, it looks for autodiscover.domain.tld, which does exists and is the Client Access Servers. I also see it talk to my mailbox server. I am challenged for a username and password for autodiscover.domain.tld, but in the end it fails with an error of "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." The next box to show up is name check box for outlook, it lists the correct microsoft exchange server (the mailbox server that holds my mailbox), but for mailbox, it shows "=SMTP:Randy.Voss(a)domain.tld". I cannot get anything to work after that.
From: Ed Crowley [MVP] on 3 Sep 2009 17:03 As far as I know, Outlook will look for: 1. https://domain.tld/autodiscover/autodiscover.xml 2. https://autodiscover.domain.tld/autodiscover/autodiscover.xml 3. If it is in the domain it will look in AD's Configuration naming context for CAS servers' service connection point, and then use that URL. I believe that is set by default to https://CasServerName/autodiscover/autodiscover.xml. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "rwvoss" <rwvoss(a)gmail.com> wrote in message news:860c2a1e-ca91-4788-a5fe-1f0d8aa74ef2(a)l13g2000yqb.googlegroups.com... On Sep 2, 4:23 pm, rwvoss <rwv...(a)gmail.com> wrote: > On Aug 28, 7:36 pm, "Rich Matheisen [MVP]" > > > > <richn...(a)rmcons.com.NOSPAM.COM> wrote: > > On Fri, 28 Aug 2009 12:45:44 -0700 (PDT), rwvoss <rwv...(a)gmail.com> > > wrote: > > > >I'm about to call Microsoft support, but I thought I would see if I > > >could get any advice from here first. I have a user with an mailbox > > >on an Exchange 2007 SP 1 server. She has a Vista workstation with > > >Outlook 2007. When trying to set up a profile for her, I saw the two > > >following errors: > > > >The connection to Microsoft Exchange is unavailable. Outlook must be > > >online or connected to complete this action. > > > >The name cannot be resolved. The connection to Microsoft Exchange is > > >unavailable. Outlook must be online or connected to complete this > > >action. > > > Are there any other applications running on the machine that use the > > Outlook profile? Things like Microsoft Office Communicator, desktop > > indexing software, etc.? They'll probably start before you try to make > > the new profile and they'll keep the connection open to the server. > > > DNS name resolution might be a problem, but you say the OWA works so > > that's probably not the case. > > > Since you have OL2007 and E2K7 you could have a problem with the CAS > > role. Is this an error you get after you check the box to manually > > configure the profile? > > --- > > Rich Matheisen > > MCSE+I, Exchange MVP > > I will check and see if there is anything running on the workstation. > The only thing it might be is an indexing program. They all have been > Vista, so I don't think there will be anything more than the built in > one though. They have the problem whether they try do you > autodiscover or set it up manually. > > One update, it seems that the account that I did get working by > disabling MAPI stopped working shortly after. However, I enabled MAPI > again and she hasn't had a problem sense. I still have 2 other users > that cannot set up outlook though. > > Thanks, > > Randy While researching another issue, I think I may have found part of my problem. Can anyone tell me what Outlook 2007 searches for when it tries to set up a mailbox profile with autodiscover? I thought it was just 'autodiscover.domain.tld' but I'm not sure I believe that any more. I used wireshark to look at network traffic while trying autodiscover off of my network with a workstation that was not part of the domain. In the capture I saw it looking for the following: mail.domain.tld pop.domain.tld pop3.domain.tld imap.domain.tld imap4.domain.tld There were no other programs running besides outlook and wireshark. The issue is mail.domain.tld is a valid address on our network for a iplanet mail server. I start to see communication with that server. Then I see that it looks for http://domian.tld/autodiscover/autodisocver.xml, which does not exist. The, finally, it looks for autodiscover.domain.tld, which does exists and is the Client Access Servers. I also see it talk to my mailbox server. I am challenged for a username and password for autodiscover.domain.tld, but in the end it fails with an error of "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." The next box to show up is name check box for outlook, it lists the correct microsoft exchange server (the mailbox server that holds my mailbox), but for mailbox, it shows "=SMTP:Randy.Voss(a)domain.tld". I cannot get anything to work after that.
From: rwvoss on 21 Sep 2009 10:04 On Sep 3, 4:03 pm, "Ed Crowley [MVP]" <cursp...(a)nospam.net> wrote: > As far as I know, Outlook will look for: > 1. https://domain.tld/autodiscover/autodiscover.xml > 2. https://autodiscover.domain.tld/autodiscover/autodiscover.xml > 3. If it is in the domain it will look in AD's Configuration naming context > for CAS servers' service connection point, and then use that URL. I believe > that is set by default tohttps://CasServerName/autodiscover/autodiscover.xml. > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > . > > "rwvoss" <rwv...(a)gmail.com> wrote in message > > news:860c2a1e-ca91-4788-a5fe-1f0d8aa74ef2(a)l13g2000yqb.googlegroups.com... > On Sep 2, 4:23 pm, rwvoss <rwv...(a)gmail.com> wrote: > > > > > On Aug 28, 7:36 pm, "Rich Matheisen [MVP]" > > > <richn...(a)rmcons.com.NOSPAM.COM> wrote: > > > On Fri, 28 Aug 2009 12:45:44 -0700 (PDT), rwvoss <rwv...(a)gmail.com> > > > wrote: > > > > >I'm about to call Microsoft support, but I thought I would see if I > > > >could get any advice from here first. I have a user with an mailbox > > > >on an Exchange 2007 SP 1 server. She has a Vista workstation with > > > >Outlook 2007. When trying to set up a profile for her, I saw the two > > > >following errors: > > > > >The connection to Microsoft Exchange is unavailable. Outlook must be > > > >online or connected to complete this action. > > > > >The name cannot be resolved. The connection to Microsoft Exchange is > > > >unavailable. Outlook must be online or connected to complete this > > > >action. > > > > Are there any other applications running on the machine that use the > > > Outlook profile? Things like Microsoft Office Communicator, desktop > > > indexing software, etc.? They'll probably start before you try to make > > > the new profile and they'll keep the connection open to the server. > > > > DNS name resolution might be a problem, but you say the OWA works so > > > that's probably not the case. > > > > Since you have OL2007 and E2K7 you could have a problem with the CAS > > > role. Is this an error you get after you check the box to manually > > > configure the profile? > > > --- > > > Rich Matheisen > > > MCSE+I, Exchange MVP > > > I will check and see if there is anything running on the workstation. > > The only thing it might be is an indexing program. They all have been > > Vista, so I don't think there will be anything more than the built in > > one though. They have the problem whether they try do you > > autodiscover or set it up manually. > > > One update, it seems that the account that I did get working by > > disabling MAPI stopped working shortly after. However, I enabled MAPI > > again and she hasn't had a problem sense. I still have 2 other users > > that cannot set up outlook though. > > > Thanks, > > > Randy > > While researching another issue, I think I may have found part of my > problem. Can anyone tell me what Outlook 2007 searches for when it > tries to set up a mailbox profile with autodiscover? I thought it was > just 'autodiscover.domain.tld' but I'm not sure I believe that any > more. I used wireshark to look at network traffic while trying > autodiscover off of my network with a workstation that was not part of > the domain. In the capture I saw it looking for the following: > > mail.domain.tld > pop.domain.tld > pop3.domain.tld > imap.domain.tld > imap4.domain.tld > > There were no other programs running besides outlook and wireshark. > The issue is mail.domain.tld is a valid address on our network for a > iplanet mail server. I start to see communication with that server. > Then I see that it looks forhttp://domian.tld/autodiscover/autodisocver.xml, > which does not exist. The, finally, it looks for > autodiscover.domain.tld, which does exists and is the Client Access > Servers. I also see it talk to my mailbox server. I am challenged for > a username and password for autodiscover.domain.tld, but in the end it > fails with an error of "The connection to Microsoft Exchange is > unavailable. Outlook must be online or connected to complete this > action." The next box to show up is name check box for outlook, it > lists the correct microsoft exchange server (the mailbox server that > holds my mailbox), but for mailbox, it shows > "=SMTP:Randy.V...(a)domain.tld". I cannot get anything to work after > that. Just an update to whoever might stumble across this. The problem seems to be related to IPv6. If I turn off IPv6 on the client system, I no longer have any issues. I realize this should be fixed with Rollup 4, but for some reason the fixes were not applied properly. I have applied up to Rollup 9 with no success. I am currently waiting for escalated support call to resolve it. Randy Voss
From: Ed Crowley [MVP] on 24 Sep 2009 01:19 Please let us know how this resolves for you. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "rwvoss" <rwvoss(a)gmail.com> wrote in message news:e209d80a-7438-44b4-b5b6-84c6792f0092(a)g1g2000vbr.googlegroups.com... On Sep 3, 4:03 pm, "Ed Crowley [MVP]" <cursp...(a)nospam.net> wrote: > As far as I know, Outlook will look for: > 1. https://domain.tld/autodiscover/autodiscover.xml > 2. https://autodiscover.domain.tld/autodiscover/autodiscover.xml > 3. If it is in the domain it will look in AD's Configuration naming > context > for CAS servers' service connection point, and then use that URL. I > believe > that is set by default > tohttps://CasServerName/autodiscover/autodiscover.xml. > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > . > > "rwvoss" <rwv...(a)gmail.com> wrote in message > > news:860c2a1e-ca91-4788-a5fe-1f0d8aa74ef2(a)l13g2000yqb.googlegroups.com... > On Sep 2, 4:23 pm, rwvoss <rwv...(a)gmail.com> wrote: > > > > > On Aug 28, 7:36 pm, "Rich Matheisen [MVP]" > > > <richn...(a)rmcons.com.NOSPAM.COM> wrote: > > > On Fri, 28 Aug 2009 12:45:44 -0700 (PDT), rwvoss <rwv...(a)gmail.com> > > > wrote: > > > > >I'm about to call Microsoft support, but I thought I would see if I > > > >could get any advice from here first. I have a user with an mailbox > > > >on an Exchange 2007 SP 1 server. She has a Vista workstation with > > > >Outlook 2007. When trying to set up a profile for her, I saw the two > > > >following errors: > > > > >The connection to Microsoft Exchange is unavailable. Outlook must be > > > >online or connected to complete this action. > > > > >The name cannot be resolved. The connection to Microsoft Exchange is > > > >unavailable. Outlook must be online or connected to complete this > > > >action. > > > > Are there any other applications running on the machine that use the > > > Outlook profile? Things like Microsoft Office Communicator, desktop > > > indexing software, etc.? They'll probably start before you try to make > > > the new profile and they'll keep the connection open to the server. > > > > DNS name resolution might be a problem, but you say the OWA works so > > > that's probably not the case. > > > > Since you have OL2007 and E2K7 you could have a problem with the CAS > > > role. Is this an error you get after you check the box to manually > > > configure the profile? > > > --- > > > Rich Matheisen > > > MCSE+I, Exchange MVP > > > I will check and see if there is anything running on the workstation. > > The only thing it might be is an indexing program. They all have been > > Vista, so I don't think there will be anything more than the built in > > one though. They have the problem whether they try do you > > autodiscover or set it up manually. > > > One update, it seems that the account that I did get working by > > disabling MAPI stopped working shortly after. However, I enabled MAPI > > again and she hasn't had a problem sense. I still have 2 other users > > that cannot set up outlook though. > > > Thanks, > > > Randy > > While researching another issue, I think I may have found part of my > problem. Can anyone tell me what Outlook 2007 searches for when it > tries to set up a mailbox profile with autodiscover? I thought it was > just 'autodiscover.domain.tld' but I'm not sure I believe that any > more. I used wireshark to look at network traffic while trying > autodiscover off of my network with a workstation that was not part of > the domain. In the capture I saw it looking for the following: > > mail.domain.tld > pop.domain.tld > pop3.domain.tld > imap.domain.tld > imap4.domain.tld > > There were no other programs running besides outlook and wireshark. > The issue is mail.domain.tld is a valid address on our network for a > iplanet mail server. I start to see communication with that server. > Then I see that it looks > forhttp://domian.tld/autodiscover/autodisocver.xml, > which does not exist. The, finally, it looks for > autodiscover.domain.tld, which does exists and is the Client Access > Servers. I also see it talk to my mailbox server. I am challenged for > a username and password for autodiscover.domain.tld, but in the end it > fails with an error of "The connection to Microsoft Exchange is > unavailable. Outlook must be online or connected to complete this > action." The next box to show up is name check box for outlook, it > lists the correct microsoft exchange server (the mailbox server that > holds my mailbox), but for mailbox, it shows > "=SMTP:Randy.V...(a)domain.tld". I cannot get anything to work after > that. Just an update to whoever might stumble across this. The problem seems to be related to IPv6. If I turn off IPv6 on the client system, I no longer have any issues. I realize this should be fixed with Rollup 4, but for some reason the fixes were not applied properly. I have applied up to Rollup 9 with no success. I am currently waiting for escalated support call to resolve it. Randy Voss
|
Pages: 1 Prev: Outlook 2007/Exchange 2007 Out of Office problem Next: Changing Password Through OWA 2003 |