|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Cannot Access OWA from inside the networkHi All,
We are running Exchange 2007 on a dedicated box, with a separate Win2003 DC server. Mail is running fine, and so is access to OWA from outside the office. For some reason, we cannot access OWA using the external FQDN (https://mail.domain.com/owa) from inside the office. Can anyone tell me why? FYI, the internal FQDN of the mail server is mail.domain.local) Thanks Show quote
"circulent" <circul***@discussions.microsoft.com> wrote in message Maybe your DNS host name mail.domain.com resolves to a public IP address, news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > Hi All, > > We are running Exchange 2007 on a dedicated box, with a separate Win2003 > DC > server. Mail is running fine, and so is access to OWA from outside the > office. For some reason, we cannot access OWA using the external FQDN > (https://mail.domain.com/owa) from inside the office. > > Can anyone tell me why? FYI, the internal FQDN of the mail server is > mail.domain.local) > > Thanks even from the LAN? In which case the requests will hit your router, which probably won't be able to reflect them back into the OWA server. If so, then you will need to add an internal DNS record (pointing to the private IP address) for the server. Lee. -- _______________________________________ Outlook Web Access for PDA, OWA For WAP: www.leederbyshire.com ________________________________________ But there already is an A record for mail.domain.local pointing to the
internal IP within our DNS server. Do I need something else? Thanks Show quote "Lee Derbyshire [MVP]" wrote: > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > > Hi All, > > > > We are running Exchange 2007 on a dedicated box, with a separate Win2003 > > DC > > server. Mail is running fine, and so is access to OWA from outside the > > office. For some reason, we cannot access OWA using the external FQDN > > (https://mail.domain.com/owa) from inside the office. > > > > Can anyone tell me why? FYI, the internal FQDN of the mail server is > > mail.domain.local) > > > > Thanks > > Maybe your DNS host name mail.domain.com resolves to a public IP address, > even from the LAN? In which case the requests will hit your router, which > probably won't be able to reflect them back into the OWA server. If so, > then you will need to add an internal DNS record (pointing to the private IP > address) for the server. > > Lee. > > -- > _______________________________________ > > Outlook Web Access for PDA, OWA For WAP: > www.leederbyshire.com > ________________________________________ > > > No, but that seemed the most likely explanation to me. What is displayed
when you try to use OWA internally? Show quote "circulent" <circul***@discussions.microsoft.com> wrote in message news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > But there already is an A record for mail.domain.local pointing to the > internal IP within our DNS server. Do I need something else? > > Thanks > > "Lee Derbyshire [MVP]" wrote: > >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> > Hi All, >> > >> > We are running Exchange 2007 on a dedicated box, with a separate >> > Win2003 >> > DC >> > server. Mail is running fine, and so is access to OWA from outside the >> > office. For some reason, we cannot access OWA using the external FQDN >> > (https://mail.domain.com/owa) from inside the office. >> > >> > Can anyone tell me why? FYI, the internal FQDN of the mail server is >> > mail.domain.local) >> > >> > Thanks >> >> Maybe your DNS host name mail.domain.com resolves to a public IP address, >> even from the LAN? In which case the requests will hit your router, >> which >> probably won't be able to reflect them back into the OWA server. If so, >> then you will need to add an internal DNS record (pointing to the private >> IP >> address) for the server. >> >> Lee. >> >> -- >> _______________________________________ >> >> Outlook Web Access for PDA, OWA For WAP: >> www.leederbyshire.com >> ________________________________________ >> >> >> If I try to access https://mail.domain.com/owa from within the network, here
is the error: Internet Explorer cannot display the webpage Most likely causes: You are not connected to the Internet. The website is encountering problems. There might be a typing error in the address. What you can try: Check your Internet connection. Try visiting another website to make sure you are connected. Retype the address. Go back to the previous page. More information This problem can be caused by a variety of issues, including: Internet connectivity has been lost. The website is temporarily unavailable. The Domain Name Server (DNS) is not reachable. The Domain Name Server (DNS) does not have a listing for the website's domain. If this is an HTTPS (secure) address, click tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section. For offline users You can still view subscribed feeds and some recently viewed webpages. To view subscribed feeds Click the Favorites Center button , click Feeds, and then click the feed you want to view. To view recently visited webpages (might not work on all pages) Click Tools , and then click Work Offline. Click the Favorites Center button , click History, and then click the page you want to view. Show quote "Lee Derbyshire [MVP]" wrote: > > No, but that seemed the most likely explanation to me. What is displayed > when you try to use OWA internally? > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > > But there already is an A record for mail.domain.local pointing to the > > internal IP within our DNS server. Do I need something else? > > > > Thanks > > > > "Lee Derbyshire [MVP]" wrote: > > > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > >> > Hi All, > >> > > >> > We are running Exchange 2007 on a dedicated box, with a separate > >> > Win2003 > >> > DC > >> > server. Mail is running fine, and so is access to OWA from outside the > >> > office. For some reason, we cannot access OWA using the external FQDN > >> > (https://mail.domain.com/owa) from inside the office. > >> > > >> > Can anyone tell me why? FYI, the internal FQDN of the mail server is > >> > mail.domain.local) > >> > > >> > Thanks > >> > >> Maybe your DNS host name mail.domain.com resolves to a public IP address, > >> even from the LAN? In which case the requests will hit your router, > >> which > >> probably won't be able to reflect them back into the OWA server. If so, > >> then you will need to add an internal DNS record (pointing to the private > >> IP > >> address) for the server. > >> > >> Lee. > >> > >> -- > >> _______________________________________ > >> > >> Outlook Web Access for PDA, OWA For WAP: > >> www.leederbyshire.com > >> ________________________________________ > >> > >> > >> > > > Which IP address is returned if you try to ping mail.domain.com from the
LAN? The public one or the private one? Show quote "circulent" <circul***@discussions.microsoft.com> wrote in message news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... > If I try to access https://mail.domain.com/owa from within the network, > here > is the error: > > Internet Explorer cannot display the webpage > > Most likely causes: > You are not connected to the Internet. > The website is encountering problems. > There might be a typing error in the address. > > What you can try: > Check your Internet connection. Try visiting another website to make > sure you are connected. > > Retype the address. > > Go back to the previous page. > > More information > > This problem can be caused by a variety of issues, including: > > Internet connectivity has been lost. > The website is temporarily unavailable. > The Domain Name Server (DNS) is not reachable. > The Domain Name Server (DNS) does not have a listing for the website's > domain. > If this is an HTTPS (secure) address, click tools, click Internet Options, > click Advanced, and check to be sure the SSL and TLS protocols are enabled > under the security section. > > For offline users > > You can still view subscribed feeds and some recently viewed webpages. > To view subscribed feeds > > Click the Favorites Center button , click Feeds, and then click the feed > you > want to view. > > To view recently visited webpages (might not work on all pages) > > Click Tools , and then click Work Offline. > Click the Favorites Center button , click History, and then click the page > you want to view. > > > > > "Lee Derbyshire [MVP]" wrote: > >> >> No, but that seemed the most likely explanation to me. What is displayed >> when you try to use OWA internally? >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... >> > But there already is an A record for mail.domain.local pointing to the >> > internal IP within our DNS server. Do I need something else? >> > >> > Thanks >> > >> > "Lee Derbyshire [MVP]" wrote: >> > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> >> > Hi All, >> >> > >> >> > We are running Exchange 2007 on a dedicated box, with a separate >> >> > Win2003 >> >> > DC >> >> > server. Mail is running fine, and so is access to OWA from outside >> >> > the >> >> > office. For some reason, we cannot access OWA using the external >> >> > FQDN >> >> > (https://mail.domain.com/owa) from inside the office. >> >> > >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail server is >> >> > mail.domain.local) >> >> > >> >> > Thanks >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP >> >> address, >> >> even from the LAN? In which case the requests will hit your router, >> >> which >> >> probably won't be able to reflect them back into the OWA server. If >> >> so, >> >> then you will need to add an internal DNS record (pointing to the >> >> private >> >> IP >> >> address) for the server. >> >> >> >> Lee. >> >> >> >> -- >> >> _______________________________________ >> >> >> >> Outlook Web Access for PDA, OWA For WAP: >> >> www.leederbyshire.com >> >> ________________________________________ >> >> >> >> >> >> >> >> >> The public address.
Thoughts? Show quote "Lee Derbyshire [MVP]" wrote: > Which IP address is returned if you try to ping mail.domain.com from the > LAN? The public one or the private one? > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... > > If I try to access https://mail.domain.com/owa from within the network, > > here > > is the error: > > > > Internet Explorer cannot display the webpage > > > > Most likely causes: > > You are not connected to the Internet. > > The website is encountering problems. > > There might be a typing error in the address. > > > > What you can try: > > Check your Internet connection. Try visiting another website to make > > sure you are connected. > > > > Retype the address. > > > > Go back to the previous page. > > > > More information > > > > This problem can be caused by a variety of issues, including: > > > > Internet connectivity has been lost. > > The website is temporarily unavailable. > > The Domain Name Server (DNS) is not reachable. > > The Domain Name Server (DNS) does not have a listing for the website's > > domain. > > If this is an HTTPS (secure) address, click tools, click Internet Options, > > click Advanced, and check to be sure the SSL and TLS protocols are enabled > > under the security section. > > > > For offline users > > > > You can still view subscribed feeds and some recently viewed webpages. > > To view subscribed feeds > > > > Click the Favorites Center button , click Feeds, and then click the feed > > you > > want to view. > > > > To view recently visited webpages (might not work on all pages) > > > > Click Tools , and then click Work Offline. > > Click the Favorites Center button , click History, and then click the page > > you want to view. > > > > > > > > > > "Lee Derbyshire [MVP]" wrote: > > > >> > >> No, but that seemed the most likely explanation to me. What is displayed > >> when you try to use OWA internally? > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > >> > But there already is an A record for mail.domain.local pointing to the > >> > internal IP within our DNS server. Do I need something else? > >> > > >> > Thanks > >> > > >> > "Lee Derbyshire [MVP]" wrote: > >> > > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > >> >> > Hi All, > >> >> > > >> >> > We are running Exchange 2007 on a dedicated box, with a separate > >> >> > Win2003 > >> >> > DC > >> >> > server. Mail is running fine, and so is access to OWA from outside > >> >> > the > >> >> > office. For some reason, we cannot access OWA using the external > >> >> > FQDN > >> >> > (https://mail.domain.com/owa) from inside the office. > >> >> > > >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail server is > >> >> > mail.domain.local) > >> >> > > >> >> > Thanks > >> >> > >> >> Maybe your DNS host name mail.domain.com resolves to a public IP > >> >> address, > >> >> even from the LAN? In which case the requests will hit your router, > >> >> which > >> >> probably won't be able to reflect them back into the OWA server. If > >> >> so, > >> >> then you will need to add an internal DNS record (pointing to the > >> >> private > >> >> IP > >> >> address) for the server. > >> >> > >> >> Lee. > >> >> > >> >> -- > >> >> _______________________________________ > >> >> > >> >> Outlook Web Access for PDA, OWA For WAP: > >> >> www.leederbyshire.com > >> >> ________________________________________ > >> >> > >> >> > >> >> > >> > >> > >> > > > It has to be some kind of DNS issue. You say that you have internal DNS
records pointing that host name to the internal IP address, but are your computers actually being configured to use your internal DNS server for lookups? Try running ipconfig /all to make sure. Show quote "circulent" <circul***@discussions.microsoft.com> wrote in message news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... > The public address. > > Thoughts? > > "Lee Derbyshire [MVP]" wrote: > >> Which IP address is returned if you try to ping mail.domain.com from the >> LAN? The public one or the private one? >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... >> > If I try to access https://mail.domain.com/owa from within the network, >> > here >> > is the error: >> > >> > Internet Explorer cannot display the webpage >> > >> > Most likely causes: >> > You are not connected to the Internet. >> > The website is encountering problems. >> > There might be a typing error in the address. >> > >> > What you can try: >> > Check your Internet connection. Try visiting another website to >> > make >> > sure you are connected. >> > >> > Retype the address. >> > >> > Go back to the previous page. >> > >> > More information >> > >> > This problem can be caused by a variety of issues, including: >> > >> > Internet connectivity has been lost. >> > The website is temporarily unavailable. >> > The Domain Name Server (DNS) is not reachable. >> > The Domain Name Server (DNS) does not have a listing for the website's >> > domain. >> > If this is an HTTPS (secure) address, click tools, click Internet >> > Options, >> > click Advanced, and check to be sure the SSL and TLS protocols are >> > enabled >> > under the security section. >> > >> > For offline users >> > >> > You can still view subscribed feeds and some recently viewed webpages. >> > To view subscribed feeds >> > >> > Click the Favorites Center button , click Feeds, and then click the >> > feed >> > you >> > want to view. >> > >> > To view recently visited webpages (might not work on all pages) >> > >> > Click Tools , and then click Work Offline. >> > Click the Favorites Center button , click History, and then click the >> > page >> > you want to view. >> > >> > >> > >> > >> > "Lee Derbyshire [MVP]" wrote: >> > >> >> >> >> No, but that seemed the most likely explanation to me. What is >> >> displayed >> >> when you try to use OWA internally? >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... >> >> > But there already is an A record for mail.domain.local pointing to >> >> > the >> >> > internal IP within our DNS server. Do I need something else? >> >> > >> >> > Thanks >> >> > >> >> > "Lee Derbyshire [MVP]" wrote: >> >> > >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> >> >> > Hi All, >> >> >> > >> >> >> > We are running Exchange 2007 on a dedicated box, with a separate >> >> >> > Win2003 >> >> >> > DC >> >> >> > server. Mail is running fine, and so is access to OWA from >> >> >> > outside >> >> >> > the >> >> >> > office. For some reason, we cannot access OWA using the external >> >> >> > FQDN >> >> >> > (https://mail.domain.com/owa) from inside the office. >> >> >> > >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail server >> >> >> > is >> >> >> > mail.domain.local) >> >> >> > >> >> >> > Thanks >> >> >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP >> >> >> address, >> >> >> even from the LAN? In which case the requests will hit your >> >> >> router, >> >> >> which >> >> >> probably won't be able to reflect them back into the OWA server. >> >> >> If >> >> >> so, >> >> >> then you will need to add an internal DNS record (pointing to the >> >> >> private >> >> >> IP >> >> >> address) for the server. >> >> >> >> >> >> Lee. >> >> >> >> >> >> -- >> >> >> _______________________________________ >> >> >> >> >> >> Outlook Web Access for PDA, OWA For WAP: >> >> >> www.leederbyshire.com >> >> >> ________________________________________ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Our DHCP server pushes out an internal DNS server which has external DNS
servers configured as forwarders. With the Exchange server, it includes a static DNS server Show quote "Lee Derbyshire [MVP]" wrote: > > It has to be some kind of DNS issue. You say that you have internal DNS > records pointing that host name to the internal IP address, but are your > computers actually being configured to use your internal DNS server for > lookups? Try running > > ipconfig /all > > to make sure. > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... > > The public address. > > > > Thoughts? > > > > "Lee Derbyshire [MVP]" wrote: > > > >> Which IP address is returned if you try to ping mail.domain.com from the > >> LAN? The public one or the private one? > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... > >> > If I try to access https://mail.domain.com/owa from within the network, > >> > here > >> > is the error: > >> > > >> > Internet Explorer cannot display the webpage > >> > > >> > Most likely causes: > >> > You are not connected to the Internet. > >> > The website is encountering problems. > >> > There might be a typing error in the address. > >> > > >> > What you can try: > >> > Check your Internet connection. Try visiting another website to > >> > make > >> > sure you are connected. > >> > > >> > Retype the address. > >> > > >> > Go back to the previous page. > >> > > >> > More information > >> > > >> > This problem can be caused by a variety of issues, including: > >> > > >> > Internet connectivity has been lost. > >> > The website is temporarily unavailable. > >> > The Domain Name Server (DNS) is not reachable. > >> > The Domain Name Server (DNS) does not have a listing for the website's > >> > domain. > >> > If this is an HTTPS (secure) address, click tools, click Internet > >> > Options, > >> > click Advanced, and check to be sure the SSL and TLS protocols are > >> > enabled > >> > under the security section. > >> > > >> > For offline users > >> > > >> > You can still view subscribed feeds and some recently viewed webpages. > >> > To view subscribed feeds > >> > > >> > Click the Favorites Center button , click Feeds, and then click the > >> > feed > >> > you > >> > want to view. > >> > > >> > To view recently visited webpages (might not work on all pages) > >> > > >> > Click Tools , and then click Work Offline. > >> > Click the Favorites Center button , click History, and then click the > >> > page > >> > you want to view. > >> > > >> > > >> > > >> > > >> > "Lee Derbyshire [MVP]" wrote: > >> > > >> >> > >> >> No, but that seemed the most likely explanation to me. What is > >> >> displayed > >> >> when you try to use OWA internally? > >> >> > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > >> >> > But there already is an A record for mail.domain.local pointing to > >> >> > the > >> >> > internal IP within our DNS server. Do I need something else? > >> >> > > >> >> > Thanks > >> >> > > >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> > > >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > >> >> >> > Hi All, > >> >> >> > > >> >> >> > We are running Exchange 2007 on a dedicated box, with a separate > >> >> >> > Win2003 > >> >> >> > DC > >> >> >> > server. Mail is running fine, and so is access to OWA from > >> >> >> > outside > >> >> >> > the > >> >> >> > office. For some reason, we cannot access OWA using the external > >> >> >> > FQDN > >> >> >> > (https://mail.domain.com/owa) from inside the office. > >> >> >> > > >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail server > >> >> >> > is > >> >> >> > mail.domain.local) > >> >> >> > > >> >> >> > Thanks > >> >> >> > >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP > >> >> >> address, > >> >> >> even from the LAN? In which case the requests will hit your > >> >> >> router, > >> >> >> which > >> >> >> probably won't be able to reflect them back into the OWA server. > >> >> >> If > >> >> >> so, > >> >> >> then you will need to add an internal DNS record (pointing to the > >> >> >> private > >> >> >> IP > >> >> >> address) for the server. > >> >> >> > >> >> >> Lee. > >> >> >> > >> >> >> -- > >> >> >> _______________________________________ > >> >> >> > >> >> >> Outlook Web Access for PDA, OWA For WAP: > >> >> >> www.leederbyshire.com > >> >> >> ________________________________________ > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > That's a common enough setup, which should work. Did you try the ipconfig
/all from your workstation to make sure that it's picking up the correct DNS server from DHCP? Show quote "circulent" <circul***@discussions.microsoft.com> wrote in message news:D0338929-19AA-4A78-878B-2D1017224532@microsoft.com... > Our DHCP server pushes out an internal DNS server which has external DNS > servers configured as forwarders. With the Exchange server, it includes a > static DNS server > > "Lee Derbyshire [MVP]" wrote: > >> >> It has to be some kind of DNS issue. You say that you have internal DNS >> records pointing that host name to the internal IP address, but are your >> computers actually being configured to use your internal DNS server for >> lookups? Try running >> >> ipconfig /all >> >> to make sure. >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... >> > The public address. >> > >> > Thoughts? >> > >> > "Lee Derbyshire [MVP]" wrote: >> > >> >> Which IP address is returned if you try to ping mail.domain.com from >> >> the >> >> LAN? The public one or the private one? >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... >> >> > If I try to access https://mail.domain.com/owa from within the >> >> > network, >> >> > here >> >> > is the error: >> >> > >> >> > Internet Explorer cannot display the webpage >> >> > >> >> > Most likely causes: >> >> > You are not connected to the Internet. >> >> > The website is encountering problems. >> >> > There might be a typing error in the address. >> >> > >> >> > What you can try: >> >> > Check your Internet connection. Try visiting another website to >> >> > make >> >> > sure you are connected. >> >> > >> >> > Retype the address. >> >> > >> >> > Go back to the previous page. >> >> > >> >> > More information >> >> > >> >> > This problem can be caused by a variety of issues, including: >> >> > >> >> > Internet connectivity has been lost. >> >> > The website is temporarily unavailable. >> >> > The Domain Name Server (DNS) is not reachable. >> >> > The Domain Name Server (DNS) does not have a listing for the >> >> > website's >> >> > domain. >> >> > If this is an HTTPS (secure) address, click tools, click Internet >> >> > Options, >> >> > click Advanced, and check to be sure the SSL and TLS protocols are >> >> > enabled >> >> > under the security section. >> >> > >> >> > For offline users >> >> > >> >> > You can still view subscribed feeds and some recently viewed >> >> > webpages. >> >> > To view subscribed feeds >> >> > >> >> > Click the Favorites Center button , click Feeds, and then click the >> >> > feed >> >> > you >> >> > want to view. >> >> > >> >> > To view recently visited webpages (might not work on all pages) >> >> > >> >> > Click Tools , and then click Work Offline. >> >> > Click the Favorites Center button , click History, and then click >> >> > the >> >> > page >> >> > you want to view. >> >> > >> >> > >> >> > >> >> > >> >> > "Lee Derbyshire [MVP]" wrote: >> >> > >> >> >> >> >> >> No, but that seemed the most likely explanation to me. What is >> >> >> displayed >> >> >> when you try to use OWA internally? >> >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... >> >> >> > But there already is an A record for mail.domain.local pointing >> >> >> > to >> >> >> > the >> >> >> > internal IP within our DNS server. Do I need something else? >> >> >> > >> >> >> > Thanks >> >> >> > >> >> >> > "Lee Derbyshire [MVP]" wrote: >> >> >> > >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in >> >> >> >> message >> >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> >> >> >> > Hi All, >> >> >> >> > >> >> >> >> > We are running Exchange 2007 on a dedicated box, with a >> >> >> >> > separate >> >> >> >> > Win2003 >> >> >> >> > DC >> >> >> >> > server. Mail is running fine, and so is access to OWA from >> >> >> >> > outside >> >> >> >> > the >> >> >> >> > office. For some reason, we cannot access OWA using the >> >> >> >> > external >> >> >> >> > FQDN >> >> >> >> > (https://mail.domain.com/owa) from inside the office. >> >> >> >> > >> >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail >> >> >> >> > server >> >> >> >> > is >> >> >> >> > mail.domain.local) >> >> >> >> > >> >> >> >> > Thanks >> >> >> >> >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP >> >> >> >> address, >> >> >> >> even from the LAN? In which case the requests will hit your >> >> >> >> router, >> >> >> >> which >> >> >> >> probably won't be able to reflect them back into the OWA server. >> >> >> >> If >> >> >> >> so, >> >> >> >> then you will need to add an internal DNS record (pointing to >> >> >> >> the >> >> >> >> private >> >> >> >> IP >> >> >> >> address) for the server. >> >> >> >> >> >> >> >> Lee. >> >> >> >> >> >> >> >> -- >> >> >> >> _______________________________________ >> >> >> >> >> >> >> >> Outlook Web Access for PDA, OWA For WAP: >> >> >> >> www.leederbyshire.com >> >> >> >> ________________________________________ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> yup. DNS points to the internal DNS server. I even trued access the external
OWA site from the DNS server and still got nothin Show quote "Lee Derbyshire [MVP]" wrote: > > That's a common enough setup, which should work. Did you try the ipconfig > /all from your workstation to make sure that it's picking up the correct DNS > server from DHCP? > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:D0338929-19AA-4A78-878B-2D1017224532@microsoft.com... > > Our DHCP server pushes out an internal DNS server which has external DNS > > servers configured as forwarders. With the Exchange server, it includes a > > static DNS server > > > > "Lee Derbyshire [MVP]" wrote: > > > >> > >> It has to be some kind of DNS issue. You say that you have internal DNS > >> records pointing that host name to the internal IP address, but are your > >> computers actually being configured to use your internal DNS server for > >> lookups? Try running > >> > >> ipconfig /all > >> > >> to make sure. > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... > >> > The public address. > >> > > >> > Thoughts? > >> > > >> > "Lee Derbyshire [MVP]" wrote: > >> > > >> >> Which IP address is returned if you try to ping mail.domain.com from > >> >> the > >> >> LAN? The public one or the private one? > >> >> > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... > >> >> > If I try to access https://mail.domain.com/owa from within the > >> >> > network, > >> >> > here > >> >> > is the error: > >> >> > > >> >> > Internet Explorer cannot display the webpage > >> >> > > >> >> > Most likely causes: > >> >> > You are not connected to the Internet. > >> >> > The website is encountering problems. > >> >> > There might be a typing error in the address. > >> >> > > >> >> > What you can try: > >> >> > Check your Internet connection. Try visiting another website to > >> >> > make > >> >> > sure you are connected. > >> >> > > >> >> > Retype the address. > >> >> > > >> >> > Go back to the previous page. > >> >> > > >> >> > More information > >> >> > > >> >> > This problem can be caused by a variety of issues, including: > >> >> > > >> >> > Internet connectivity has been lost. > >> >> > The website is temporarily unavailable. > >> >> > The Domain Name Server (DNS) is not reachable. > >> >> > The Domain Name Server (DNS) does not have a listing for the > >> >> > website's > >> >> > domain. > >> >> > If this is an HTTPS (secure) address, click tools, click Internet > >> >> > Options, > >> >> > click Advanced, and check to be sure the SSL and TLS protocols are > >> >> > enabled > >> >> > under the security section. > >> >> > > >> >> > For offline users > >> >> > > >> >> > You can still view subscribed feeds and some recently viewed > >> >> > webpages. > >> >> > To view subscribed feeds > >> >> > > >> >> > Click the Favorites Center button , click Feeds, and then click the > >> >> > feed > >> >> > you > >> >> > want to view. > >> >> > > >> >> > To view recently visited webpages (might not work on all pages) > >> >> > > >> >> > Click Tools , and then click Work Offline. > >> >> > Click the Favorites Center button , click History, and then click > >> >> > the > >> >> > page > >> >> > you want to view. > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> > > >> >> >> > >> >> >> No, but that seemed the most likely explanation to me. What is > >> >> >> displayed > >> >> >> when you try to use OWA internally? > >> >> >> > >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > >> >> >> > But there already is an A record for mail.domain.local pointing > >> >> >> > to > >> >> >> > the > >> >> >> > internal IP within our DNS server. Do I need something else? > >> >> >> > > >> >> >> > Thanks > >> >> >> > > >> >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> >> > > >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in > >> >> >> >> message > >> >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > >> >> >> >> > Hi All, > >> >> >> >> > > >> >> >> >> > We are running Exchange 2007 on a dedicated box, with a > >> >> >> >> > separate > >> >> >> >> > Win2003 > >> >> >> >> > DC > >> >> >> >> > server. Mail is running fine, and so is access to OWA from > >> >> >> >> > outside > >> >> >> >> > the > >> >> >> >> > office. For some reason, we cannot access OWA using the > >> >> >> >> > external > >> >> >> >> > FQDN > >> >> >> >> > (https://mail.domain.com/owa) from inside the office. > >> >> >> >> > > >> >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail > >> >> >> >> > server > >> >> >> >> > is > >> >> >> >> > mail.domain.local) > >> >> >> >> > > >> >> >> >> > Thanks > >> >> >> >> > >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP > >> >> >> >> address, > >> >> >> >> even from the LAN? In which case the requests will hit your > >> >> >> >> router, > >> >> >> >> which > >> >> >> >> probably won't be able to reflect them back into the OWA server. > >> >> >> >> If > >> >> >> >> so, > >> >> >> >> then you will need to add an internal DNS record (pointing to > >> >> >> >> the > >> >> >> >> private > >> >> >> >> IP > >> >> >> >> address) for the server. > >> >> >> >> > >> >> >> >> Lee. > >> >> >> >> > >> >> >> >> -- > >> >> >> >> _______________________________________ > >> >> >> >> > >> >> >> >> Outlook Web Access for PDA, OWA For WAP: > >> >> >> >> www.leederbyshire.com > >> >> >> >> ________________________________________ > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > What IP do you get if you ping the server name from the DNS server?
Internal or external. There's only one thing I can think of that would override queried DNS, and that's a HOSTS file. Have you checked that? Show quote "circulent" <circul***@discussions.microsoft.com> wrote in message news:E708F3B7-D180-44B7-92D2-5A17A84CC1BC@microsoft.com... > yup. DNS points to the internal DNS server. I even trued access the > external > OWA site from the DNS server and still got nothin > > "Lee Derbyshire [MVP]" wrote: > >> >> That's a common enough setup, which should work. Did you try the >> ipconfig >> /all from your workstation to make sure that it's picking up the correct >> DNS >> server from DHCP? >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:D0338929-19AA-4A78-878B-2D1017224532@microsoft.com... >> > Our DHCP server pushes out an internal DNS server which has external >> > DNS >> > servers configured as forwarders. With the Exchange server, it includes >> > a >> > static DNS server >> > >> > "Lee Derbyshire [MVP]" wrote: >> > >> >> >> >> It has to be some kind of DNS issue. You say that you have internal >> >> DNS >> >> records pointing that host name to the internal IP address, but are >> >> your >> >> computers actually being configured to use your internal DNS server >> >> for >> >> lookups? Try running >> >> >> >> ipconfig /all >> >> >> >> to make sure. >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... >> >> > The public address. >> >> > >> >> > Thoughts? >> >> > >> >> > "Lee Derbyshire [MVP]" wrote: >> >> > >> >> >> Which IP address is returned if you try to ping mail.domain.com >> >> >> from >> >> >> the >> >> >> LAN? The public one or the private one? >> >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... >> >> >> > If I try to access https://mail.domain.com/owa from within the >> >> >> > network, >> >> >> > here >> >> >> > is the error: >> >> >> > >> >> >> > Internet Explorer cannot display the webpage >> >> >> > >> >> >> > Most likely causes: >> >> >> > You are not connected to the Internet. >> >> >> > The website is encountering problems. >> >> >> > There might be a typing error in the address. >> >> >> > >> >> >> > What you can try: >> >> >> > Check your Internet connection. Try visiting another website >> >> >> > to >> >> >> > make >> >> >> > sure you are connected. >> >> >> > >> >> >> > Retype the address. >> >> >> > >> >> >> > Go back to the previous page. >> >> >> > >> >> >> > More information >> >> >> > >> >> >> > This problem can be caused by a variety of issues, including: >> >> >> > >> >> >> > Internet connectivity has been lost. >> >> >> > The website is temporarily unavailable. >> >> >> > The Domain Name Server (DNS) is not reachable. >> >> >> > The Domain Name Server (DNS) does not have a listing for the >> >> >> > website's >> >> >> > domain. >> >> >> > If this is an HTTPS (secure) address, click tools, click Internet >> >> >> > Options, >> >> >> > click Advanced, and check to be sure the SSL and TLS protocols >> >> >> > are >> >> >> > enabled >> >> >> > under the security section. >> >> >> > >> >> >> > For offline users >> >> >> > >> >> >> > You can still view subscribed feeds and some recently viewed >> >> >> > webpages. >> >> >> > To view subscribed feeds >> >> >> > >> >> >> > Click the Favorites Center button , click Feeds, and then click >> >> >> > the >> >> >> > feed >> >> >> > you >> >> >> > want to view. >> >> >> > >> >> >> > To view recently visited webpages (might not work on all pages) >> >> >> > >> >> >> > Click Tools , and then click Work Offline. >> >> >> > Click the Favorites Center button , click History, and then click >> >> >> > the >> >> >> > page >> >> >> > you want to view. >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > "Lee Derbyshire [MVP]" wrote: >> >> >> > >> >> >> >> >> >> >> >> No, but that seemed the most likely explanation to me. What is >> >> >> >> displayed >> >> >> >> when you try to use OWA internally? >> >> >> >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in >> >> >> >> message >> >> >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... >> >> >> >> > But there already is an A record for mail.domain.local >> >> >> >> > pointing >> >> >> >> > to >> >> >> >> > the >> >> >> >> > internal IP within our DNS server. Do I need something else? >> >> >> >> > >> >> >> >> > Thanks >> >> >> >> > >> >> >> >> > "Lee Derbyshire [MVP]" wrote: >> >> >> >> > >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in >> >> >> >> >> message >> >> >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> >> >> >> >> > Hi All, >> >> >> >> >> > >> >> >> >> >> > We are running Exchange 2007 on a dedicated box, with a >> >> >> >> >> > separate >> >> >> >> >> > Win2003 >> >> >> >> >> > DC >> >> >> >> >> > server. Mail is running fine, and so is access to OWA from >> >> >> >> >> > outside >> >> >> >> >> > the >> >> >> >> >> > office. For some reason, we cannot access OWA using the >> >> >> >> >> > external >> >> >> >> >> > FQDN >> >> >> >> >> > (https://mail.domain.com/owa) from inside the office. >> >> >> >> >> > >> >> >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail >> >> >> >> >> > server >> >> >> >> >> > is >> >> >> >> >> > mail.domain.local) >> >> >> >> >> > >> >> >> >> >> > Thanks >> >> >> >> >> >> >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public >> >> >> >> >> IP >> >> >> >> >> address, >> >> >> >> >> even from the LAN? In which case the requests will hit your >> >> >> >> >> router, >> >> >> >> >> which >> >> >> >> >> probably won't be able to reflect them back into the OWA >> >> >> >> >> server. >> >> >> >> >> If >> >> >> >> >> so, >> >> >> >> >> then you will need to add an internal DNS record (pointing to >> >> >> >> >> the >> >> >> >> >> private >> >> >> >> >> IP >> >> >> >> >> address) for the server. >> >> >> >> >> >> >> >> >> >> Lee. >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> _______________________________________ >> >> >> >> >> >> >> >> >> >> Outlook Web Access for PDA, OWA For WAP: >> >> >> >> >> www.leederbyshire.com >> >> >> >> >> ________________________________________ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Oh, another thing. Does your internal DNS server have itself (i.e.
127.0.0.1) listed in first place as the DNS servers in it's TCP/IP properties? Show quote "circulent" <circul***@discussions.microsoft.com> wrote in message news:D0338929-19AA-4A78-878B-2D1017224532@microsoft.com... > Our DHCP server pushes out an internal DNS server which has external DNS > servers configured as forwarders. With the Exchange server, it includes a > static DNS server > > "Lee Derbyshire [MVP]" wrote: > >> >> It has to be some kind of DNS issue. You say that you have internal DNS >> records pointing that host name to the internal IP address, but are your >> computers actually being configured to use your internal DNS server for >> lookups? Try running >> >> ipconfig /all >> >> to make sure. >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... >> > The public address. >> > >> > Thoughts? >> > >> > "Lee Derbyshire [MVP]" wrote: >> > >> >> Which IP address is returned if you try to ping mail.domain.com from >> >> the >> >> LAN? The public one or the private one? >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... >> >> > If I try to access https://mail.domain.com/owa from within the >> >> > network, >> >> > here >> >> > is the error: >> >> > >> >> > Internet Explorer cannot display the webpage >> >> > >> >> > Most likely causes: >> >> > You are not connected to the Internet. >> >> > The website is encountering problems. >> >> > There might be a typing error in the address. >> >> > >> >> > What you can try: >> >> > Check your Internet connection. Try visiting another website to >> >> > make >> >> > sure you are connected. >> >> > >> >> > Retype the address. >> >> > >> >> > Go back to the previous page. >> >> > >> >> > More information >> >> > >> >> > This problem can be caused by a variety of issues, including: >> >> > >> >> > Internet connectivity has been lost. >> >> > The website is temporarily unavailable. >> >> > The Domain Name Server (DNS) is not reachable. >> >> > The Domain Name Server (DNS) does not have a listing for the >> >> > website's >> >> > domain. >> >> > If this is an HTTPS (secure) address, click tools, click Internet >> >> > Options, >> >> > click Advanced, and check to be sure the SSL and TLS protocols are >> >> > enabled >> >> > under the security section. >> >> > >> >> > For offline users >> >> > >> >> > You can still view subscribed feeds and some recently viewed >> >> > webpages. >> >> > To view subscribed feeds >> >> > >> >> > Click the Favorites Center button , click Feeds, and then click the >> >> > feed >> >> > you >> >> > want to view. >> >> > >> >> > To view recently visited webpages (might not work on all pages) >> >> > >> >> > Click Tools , and then click Work Offline. >> >> > Click the Favorites Center button , click History, and then click >> >> > the >> >> > page >> >> > you want to view. >> >> > >> >> > >> >> > >> >> > >> >> > "Lee Derbyshire [MVP]" wrote: >> >> > >> >> >> >> >> >> No, but that seemed the most likely explanation to me. What is >> >> >> displayed >> >> >> when you try to use OWA internally? >> >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... >> >> >> > But there already is an A record for mail.domain.local pointing >> >> >> > to >> >> >> > the >> >> >> > internal IP within our DNS server. Do I need something else? >> >> >> > >> >> >> > Thanks >> >> >> > >> >> >> > "Lee Derbyshire [MVP]" wrote: >> >> >> > >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in >> >> >> >> message >> >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> >> >> >> > Hi All, >> >> >> >> > >> >> >> >> > We are running Exchange 2007 on a dedicated box, with a >> >> >> >> > separate >> >> >> >> > Win2003 >> >> >> >> > DC >> >> >> >> > server. Mail is running fine, and so is access to OWA from >> >> >> >> > outside >> >> >> >> > the >> >> >> >> > office. For some reason, we cannot access OWA using the >> >> >> >> > external >> >> >> >> > FQDN >> >> >> >> > (https://mail.domain.com/owa) from inside the office. >> >> >> >> > >> >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail >> >> >> >> > server >> >> >> >> > is >> >> >> >> > mail.domain.local) >> >> >> >> > >> >> >> >> > Thanks >> >> >> >> >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP >> >> >> >> address, >> >> >> >> even from the LAN? In which case the requests will hit your >> >> >> >> router, >> >> >> >> which >> >> >> >> probably won't be able to reflect them back into the OWA server. >> >> >> >> If >> >> >> >> so, >> >> >> >> then you will need to add an internal DNS record (pointing to >> >> >> >> the >> >> >> >> private >> >> >> >> IP >> >> >> >> address) for the server. >> >> >> >> >> >> >> >> Lee. >> >> >> >> >> >> >> >> -- >> >> >> >> _______________________________________ >> >> >> >> >> >> >> >> Outlook Web Access for PDA, OWA For WAP: >> >> >> >> www.leederbyshire.com >> >> >> >> ________________________________________ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> yes. Any other ideas? I'm stumped
Show quote "Lee Derbyshire [MVP]" wrote: > > Oh, another thing. Does your internal DNS server have itself (i.e. > 127.0.0.1) listed in first place as the DNS servers in it's TCP/IP > properties? > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:D0338929-19AA-4A78-878B-2D1017224532@microsoft.com... > > Our DHCP server pushes out an internal DNS server which has external DNS > > servers configured as forwarders. With the Exchange server, it includes a > > static DNS server > > > > "Lee Derbyshire [MVP]" wrote: > > > >> > >> It has to be some kind of DNS issue. You say that you have internal DNS > >> records pointing that host name to the internal IP address, but are your > >> computers actually being configured to use your internal DNS server for > >> lookups? Try running > >> > >> ipconfig /all > >> > >> to make sure. > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... > >> > The public address. > >> > > >> > Thoughts? > >> > > >> > "Lee Derbyshire [MVP]" wrote: > >> > > >> >> Which IP address is returned if you try to ping mail.domain.com from > >> >> the > >> >> LAN? The public one or the private one? > >> >> > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... > >> >> > If I try to access https://mail.domain.com/owa from within the > >> >> > network, > >> >> > here > >> >> > is the error: > >> >> > > >> >> > Internet Explorer cannot display the webpage > >> >> > > >> >> > Most likely causes: > >> >> > You are not connected to the Internet. > >> >> > The website is encountering problems. > >> >> > There might be a typing error in the address. > >> >> > > >> >> > What you can try: > >> >> > Check your Internet connection. Try visiting another website to > >> >> > make > >> >> > sure you are connected. > >> >> > > >> >> > Retype the address. > >> >> > > >> >> > Go back to the previous page. > >> >> > > >> >> > More information > >> >> > > >> >> > This problem can be caused by a variety of issues, including: > >> >> > > >> >> > Internet connectivity has been lost. > >> >> > The website is temporarily unavailable. > >> >> > The Domain Name Server (DNS) is not reachable. > >> >> > The Domain Name Server (DNS) does not have a listing for the > >> >> > website's > >> >> > domain. > >> >> > If this is an HTTPS (secure) address, click tools, click Internet > >> >> > Options, > >> >> > click Advanced, and check to be sure the SSL and TLS protocols are > >> >> > enabled > >> >> > under the security section. > >> >> > > >> >> > For offline users > >> >> > > >> >> > You can still view subscribed feeds and some recently viewed > >> >> > webpages. > >> >> > To view subscribed feeds > >> >> > > >> >> > Click the Favorites Center button , click Feeds, and then click the > >> >> > feed > >> >> > you > >> >> > want to view. > >> >> > > >> >> > To view recently visited webpages (might not work on all pages) > >> >> > > >> >> > Click Tools , and then click Work Offline. > >> >> > Click the Favorites Center button , click History, and then click > >> >> > the > >> >> > page > >> >> > you want to view. > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> > > >> >> >> > >> >> >> No, but that seemed the most likely explanation to me. What is > >> >> >> displayed > >> >> >> when you try to use OWA internally? > >> >> >> > >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > >> >> >> > But there already is an A record for mail.domain.local pointing > >> >> >> > to > >> >> >> > the > >> >> >> > internal IP within our DNS server. Do I need something else? > >> >> >> > > >> >> >> > Thanks > >> >> >> > > >> >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> >> > > >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in > >> >> >> >> message > >> >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > >> >> >> >> > Hi All, > >> >> >> >> > > >> >> >> >> > We are running Exchange 2007 on a dedicated box, with a > >> >> >> >> > separate > >> >> >> >> > Win2003 > >> >> >> >> > DC > >> >> >> >> > server. Mail is running fine, and so is access to OWA from > >> >> >> >> > outside > >> >> >> >> > the > >> >> >> >> > office. For some reason, we cannot access OWA using the > >> >> >> >> > external > >> >> >> >> > FQDN > >> >> >> >> > (https://mail.domain.com/owa) from inside the office. > >> >> >> >> > > >> >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail > >> >> >> >> > server > >> >> >> >> > is > >> >> >> >> > mail.domain.local) > >> >> >> >> > > >> >> >> >> > Thanks > >> >> >> >> > >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP > >> >> >> >> address, > >> >> >> >> even from the LAN? In which case the requests will hit your > >> >> >> >> router, > >> >> >> >> which > >> >> >> >> probably won't be able to reflect them back into the OWA server. > >> >> >> >> If > >> >> >> >> so, > >> >> >> >> then you will need to add an internal DNS record (pointing to > >> >> >> >> the > >> >> >> >> private > >> >> >> >> IP > >> >> >> >> address) for the server. > >> >> >> >> > >> >> >> >> Lee. > >> >> >> >> > >> >> >> >> -- > >> >> >> >> _______________________________________ > >> >> >> >> > >> >> >> >> Outlook Web Access for PDA, OWA For WAP: > >> >> >> >> www.leederbyshire.com > >> >> >> >> ________________________________________ > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > Lee is right. It is a DNS issue. And by the way I HATE DNS. Your
INTERNAL DNS should point to the internal address whan you ping owa.mymailserver.com.from the inside. Be sure to go to a command prompt and go ipconfig /flushdns between tries. You say your external DNS is right whether it's yours of your provider has it. I should be able to ping owa.yourmailserver.com and come up with the correct external IP address. Not necessarly a ping reply because many admins cut ICMP off these days, but it should resolve. Verify for us, there are 2 DNS servers. One internal inside the firewall and one either you control with a public IP or your provider has control of. Tango Yes. It has itself listed as 192.168.1.4 as the primary DNS server
Show quote "Lee Derbyshire [MVP]" wrote: > > Oh, another thing. Does your internal DNS server have itself (i.e. > 127.0.0.1) listed in first place as the DNS servers in it's TCP/IP > properties? > > "circulent" <circul***@discussions.microsoft.com> wrote in message > news:D0338929-19AA-4A78-878B-2D1017224532@microsoft.com... > > Our DHCP server pushes out an internal DNS server which has external DNS > > servers configured as forwarders. With the Exchange server, it includes a > > static DNS server > > > > "Lee Derbyshire [MVP]" wrote: > > > >> > >> It has to be some kind of DNS issue. You say that you have internal DNS > >> records pointing that host name to the internal IP address, but are your > >> computers actually being configured to use your internal DNS server for > >> lookups? Try running > >> > >> ipconfig /all > >> > >> to make sure. > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... > >> > The public address. > >> > > >> > Thoughts? > >> > > >> > "Lee Derbyshire [MVP]" wrote: > >> > > >> >> Which IP address is returned if you try to ping mail.domain.com from > >> >> the > >> >> LAN? The public one or the private one? > >> >> > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... > >> >> > If I try to access https://mail.domain.com/owa from within the > >> >> > network, > >> >> > here > >> >> > is the error: > >> >> > > >> >> > Internet Explorer cannot display the webpage > >> >> > > >> >> > Most likely causes: > >> >> > You are not connected to the Internet. > >> >> > The website is encountering problems. > >> >> > There might be a typing error in the address. > >> >> > > >> >> > What you can try: > >> >> > Check your Internet connection. Try visiting another website to > >> >> > make > >> >> > sure you are connected. > >> >> > > >> >> > Retype the address. > >> >> > > >> >> > Go back to the previous page. > >> >> > > >> >> > More information > >> >> > > >> >> > This problem can be caused by a variety of issues, including: > >> >> > > >> >> > Internet connectivity has been lost. > >> >> > The website is temporarily unavailable. > >> >> > The Domain Name Server (DNS) is not reachable. > >> >> > The Domain Name Server (DNS) does not have a listing for the > >> >> > website's > >> >> > domain. > >> >> > If this is an HTTPS (secure) address, click tools, click Internet > >> >> > Options, > >> >> > click Advanced, and check to be sure the SSL and TLS protocols are > >> >> > enabled > >> >> > under the security section. > >> >> > > >> >> > For offline users > >> >> > > >> >> > You can still view subscribed feeds and some recently viewed > >> >> > webpages. > >> >> > To view subscribed feeds > >> >> > > >> >> > Click the Favorites Center button , click Feeds, and then click the > >> >> > feed > >> >> > you > >> >> > want to view. > >> >> > > >> >> > To view recently visited webpages (might not work on all pages) > >> >> > > >> >> > Click Tools , and then click Work Offline. > >> >> > Click the Favorites Center button , click History, and then click > >> >> > the > >> >> > page > >> >> > you want to view. > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> > > >> >> >> > >> >> >> No, but that seemed the most likely explanation to me. What is > >> >> >> displayed > >> >> >> when you try to use OWA internally? > >> >> >> > >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > >> >> >> > But there already is an A record for mail.domain.local pointing > >> >> >> > to > >> >> >> > the > >> >> >> > internal IP within our DNS server. Do I need something else? > >> >> >> > > >> >> >> > Thanks > >> >> >> > > >> >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> >> > > >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in > >> >> >> >> message > >> >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > >> >> >> >> > Hi All, > >> >> >> >> > > >> >> >> >> > We are running Exchange 2007 on a dedicated box, with a > >> >> >> >> > separate > >> >> >> >> > Win2003 > >> >> >> >> > DC > >> >> >> >> > server. Mail is running fine, and so is access to OWA from > >> >> >> >> > outside > >> >> >> >> > the > >> >> >> >> > office. For some reason, we cannot access OWA using the > >> >> >> >> > external > >> >> >> >> > FQDN > >> >> >> >> > (https://mail.domain.com/owa) from inside the office. > >> >> >> >> > > >> >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail > >> >> >> >> > server > >> >> >> >> > is > >> >> >> >> > mail.domain.local) > >> >> >> >> > > >> >> >> >> > Thanks > >> >> >> >> > >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public IP > >> >> >> >> address, > >> >> >> >> even from the LAN? In which case the requests will hit your > >> >> >> >> router, > >> >> >> >> which > >> >> >> >> probably won't be able to reflect them back into the OWA server. > >> >> >> >> If > >> >> >> >> so, > >> >> >> >> then you will need to add an internal DNS record (pointing to > >> >> >> >> the > >> >> >> >> private > >> >> >> >> IP > >> >> >> >> address) for the server. > >> >> >> >> > >> >> >> >> Lee. > >> >> >> >> > >> >> >> >> -- > >> >> >> >> _______________________________________ > >> >> >> >> > >> >> >> >> Outlook Web Access for PDA, OWA For WAP: > >> >> >> >> www.leederbyshire.com > >> >> >> >> ________________________________________ > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > What IP do you get if you ping the server name from the DNS server?
Internal or external. There's only one thing I can think of that would override queried DNS, and that's a HOSTS file. Have you checked that? Show quote "circulent" <circul***@discussions.microsoft.com> wrote in message news:1DC85C0A-7AA6-4A89-ACA2-3332AB66EF09@microsoft.com... > Yes. It has itself listed as 192.168.1.4 as the primary DNS server > > "Lee Derbyshire [MVP]" wrote: > >> >> Oh, another thing. Does your internal DNS server have itself (i.e. >> 127.0.0.1) listed in first place as the DNS servers in it's TCP/IP >> properties? >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:D0338929-19AA-4A78-878B-2D1017224532@microsoft.com... >> > Our DHCP server pushes out an internal DNS server which has external >> > DNS >> > servers configured as forwarders. With the Exchange server, it includes >> > a >> > static DNS server >> > >> > "Lee Derbyshire [MVP]" wrote: >> > >> >> >> >> It has to be some kind of DNS issue. You say that you have internal >> >> DNS >> >> records pointing that host name to the internal IP address, but are >> >> your >> >> computers actually being configured to use your internal DNS server >> >> for >> >> lookups? Try running >> >> >> >> ipconfig /all >> >> >> >> to make sure. >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com... >> >> > The public address. >> >> > >> >> > Thoughts? >> >> > >> >> > "Lee Derbyshire [MVP]" wrote: >> >> > >> >> >> Which IP address is returned if you try to ping mail.domain.com >> >> >> from >> >> >> the >> >> >> LAN? The public one or the private one? >> >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... >> >> >> > If I try to access https://mail.domain.com/owa from within the >> >> >> > network, >> >> >> > here >> >> >> > is the error: >> >> >> > >> >> >> > Internet Explorer cannot display the webpage >> >> >> > >> >> >> > Most likely causes: >> >> >> > You are not connected to the Internet. >> >> >> > The website is encountering problems. >> >> >> > There might be a typing error in the address. >> >> >> > >> >> >> > What you can try: >> >> >> > Check your Internet connection. Try visiting another website >> >> >> > to >> >> >> > make >> >> >> > sure you are connected. >> >> >> > >> >> >> > Retype the address. >> >> >> > >> >> >> > Go back to the previous page. >> >> >> > >> >> >> > More information >> >> >> > >> >> >> > This problem can be caused by a variety of issues, including: >> >> >> > >> >> >> > Internet connectivity has been lost. >> >> >> > The website is temporarily unavailable. >> >> >> > The Domain Name Server (DNS) is not reachable. >> >> >> > The Domain Name Server (DNS) does not have a listing for the >> >> >> > website's >> >> >> > domain. >> >> >> > If this is an HTTPS (secure) address, click tools, click Internet >> >> >> > Options, >> >> >> > click Advanced, and check to be sure the SSL and TLS protocols >> >> >> > are >> >> >> > enabled >> >> >> > under the security section. >> >> >> > >> >> >> > For offline users >> >> >> > >> >> >> > You can still view subscribed feeds and some recently viewed >> >> >> > webpages. >> >> >> > To view subscribed feeds >> >> >> > >> >> >> > Click the Favorites Center button , click Feeds, and then click >> >> >> > the >> >> >> > feed >> >> >> > you >> >> >> > want to view. >> >> >> > >> >> >> > To view recently visited webpages (might not work on all pages) >> >> >> > >> >> >> > Click Tools , and then click Work Offline. >> >> >> > Click the Favorites Center button , click History, and then click >> >> >> > the >> >> >> > page >> >> >> > you want to view. >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > "Lee Derbyshire [MVP]" wrote: >> >> >> > >> >> >> >> >> >> >> >> No, but that seemed the most likely explanation to me. What is >> >> >> >> displayed >> >> >> >> when you try to use OWA internally? >> >> >> >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in >> >> >> >> message >> >> >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... >> >> >> >> > But there already is an A record for mail.domain.local >> >> >> >> > pointing >> >> >> >> > to >> >> >> >> > the >> >> >> >> > internal IP within our DNS server. Do I need something else? >> >> >> >> > >> >> >> >> > Thanks >> >> >> >> > >> >> >> >> > "Lee Derbyshire [MVP]" wrote: >> >> >> >> > >> >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in >> >> >> >> >> message >> >> >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> >> >> >> >> > Hi All, >> >> >> >> >> > >> >> >> >> >> > We are running Exchange 2007 on a dedicated box, with a >> >> >> >> >> > separate >> >> >> >> >> > Win2003 >> >> >> >> >> > DC >> >> >> >> >> > server. Mail is running fine, and so is access to OWA from >> >> >> >> >> > outside >> >> >> >> >> > the >> >> >> >> >> > office. For some reason, we cannot access OWA using the >> >> >> >> >> > external >> >> >> >> >> > FQDN >> >> >> >> >> > (https://mail.domain.com/owa) from inside the office. >> >> >> >> >> > >> >> >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail >> >> >> >> >> > server >> >> >> >> >> > is >> >> >> >> >> > mail.domain.local) >> >> >> >> >> > >> >> >> >> >> > Thanks >> >> >> >> >> >> >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public >> >> >> >> >> IP >> >> >> >> >> address, >> >> >> >> >> even from the LAN? In which case the requests will hit your >> >> >> >> >> router, >> >> >> >> >> which >> >> >> >> >> probably won't be able to reflect them back into the OWA >> >> >> >> >> server. >> >> >> >> >> If >> >> >> >> >> so, >> >> >> >> >> then you will need to add an internal DNS record (pointing to >> >> >> >> >> the >> >> >> >> >> private >> >> >> >> >> IP >> >> >> >> >> address) for the server. >> >> >> >> >> >> >> >> >> >> Lee. >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> _______________________________________ >> >> >> >> >> >> >> >> >> >> Outlook Web Access for PDA, OWA For WAP: >> >> >> >> >> www.leederbyshire.com >> >> >> >> >> ________________________________________ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> That's the problem. You can't loopback.
You need to set up a split DNS. In your internal DNS, create a new zone by the name of your public domain name. Create a 'A' record in that zone called 'mail' and set the IP address to your INTERNAL Exchange server address. That way when you request mail.domain.com form inside the LAN, DNS will always return the internal address. =?Utf-8?B?Y2lyY3VsZW50?= <circul***@discussions.microsoft.com> wrote in Show quote news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com: > The public address. > > Thoughts? > > "Lee Derbyshire [MVP]" wrote: > >> Which IP address is returned if you try to ping mail.domain.com from >> the LAN? The public one or the private one? >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... >> > If I try to access https://mail.domain.com/owa from within the >> > network, here >> > is the error: >> > >> > Internet Explorer cannot display the webpage >> > >> > Most likely causes: >> > You are not connected to the Internet. >> > The website is encountering problems. >> > There might be a typing error in the address. >> > >> > What you can try: >> > Check your Internet connection. Try visiting another website to >> > make >> > sure you are connected. >> > >> > Retype the address. >> > >> > Go back to the previous page. >> > >> > More information >> > >> > This problem can be caused by a variety of issues, including: >> > >> > Internet connectivity has been lost. >> > The website is temporarily unavailable. >> > The Domain Name Server (DNS) is not reachable. >> > The Domain Name Server (DNS) does not have a listing for the >> > website's domain. >> > If this is an HTTPS (secure) address, click tools, click Internet >> > Options, click Advanced, and check to be sure the SSL and TLS >> > protocols are enabled under the security section. >> > >> > For offline users >> > >> > You can still view subscribed feeds and some recently viewed >> > webpages. To view subscribed feeds >> > >> > Click the Favorites Center button , click Feeds, and then click the >> > feed you >> > want to view. >> > >> > To view recently visited webpages (might not work on all pages) >> > >> > Click Tools , and then click Work Offline. >> > Click the Favorites Center button , click History, and then click >> > the page you want to view. >> > >> > >> > >> > >> > "Lee Derbyshire [MVP]" wrote: >> > >> >> >> >> No, but that seemed the most likely explanation to me. What is >> >> displayed when you try to use OWA internally? >> >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... >> >> > But there already is an A record for mail.domain.local pointing >> >> > to the internal IP within our DNS server. Do I need something >> >> > else? >> >> > >> >> > Thanks >> >> > >> >> > "Lee Derbyshire [MVP]" wrote: >> >> > >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in >> >> >> message >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... >> >> >> > Hi All, >> >> >> > >> >> >> > We are running Exchange 2007 on a dedicated box, with a >> >> >> > separate Win2003 >> >> >> > DC >> >> >> > server. Mail is running fine, and so is access to OWA from >> >> >> > outside the >> >> >> > office. For some reason, we cannot access OWA using the >> >> >> > external FQDN >> >> >> > (https://mail.domain.com/owa) from inside the office. >> >> >> > >> >> >> > Can anyone tell me why? FYI, the internal FQDN of the mail >> >> >> > server is mail.domain.local) >> >> >> > >> >> >> > Thanks >> >> >> >> >> >> Maybe your DNS host name mail.domain.com resolves to a public >> >> >> IP address, >> >> >> even from the LAN? In which case the requests will hit your >> >> >> router, which >> >> >> probably won't be able to reflect them back into the OWA >> >> >> server. If so, >> >> >> then you will need to add an internal DNS record (pointing to >> >> >> the private >> >> >> IP >> >> >> address) for the server. >> >> >> >> >> >> Lee. >> >> >> >> >> >> -- >> >> >> _______________________________________ >> >> >> >> >> >> Outlook Web Access for PDA, OWA For WAP: >> >> >> www.leederbyshire.com >> >> >> ________________________________________ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> That worked. Thanks. What do you mean by a loopback? This problem has only come up once with all of our Exchange installations. Show quote "Asher_N" wrote: > > That's the problem. You can't loopback. > > You need to set up a split DNS. > > In your internal DNS, create a new zone by the name of your public domain > name. > > Create a 'A' record in that zone called 'mail' and set the IP address to > your INTERNAL Exchange server address. That way when you request > mail.domain.com form inside the LAN, DNS will always return the internal > address. > > > =?Utf-8?B?Y2lyY3VsZW50?= <circul***@discussions.microsoft.com> wrote in > news:DDC461B0-34B9-4C8A-8F33-3F328513B9FF@microsoft.com: > > > The public address. > > > > Thoughts? > > > > "Lee Derbyshire [MVP]" wrote: > > > >> Which IP address is returned if you try to ping mail.domain.com from > >> the LAN? The public one or the private one? > >> > >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> news:E2922F54-6B4F-4EC4-8EB4-8BD4944B42F7@microsoft.com... > >> > If I try to access https://mail.domain.com/owa from within the > >> > network, here > >> > is the error: > >> > > >> > Internet Explorer cannot display the webpage > >> > > >> > Most likely causes: > >> > You are not connected to the Internet. > >> > The website is encountering problems. > >> > There might be a typing error in the address. > >> > > >> > What you can try: > >> > Check your Internet connection. Try visiting another website to > >> > make > >> > sure you are connected. > >> > > >> > Retype the address. > >> > > >> > Go back to the previous page. > >> > > >> > More information > >> > > >> > This problem can be caused by a variety of issues, including: > >> > > >> > Internet connectivity has been lost. > >> > The website is temporarily unavailable. > >> > The Domain Name Server (DNS) is not reachable. > >> > The Domain Name Server (DNS) does not have a listing for the > >> > website's domain. > >> > If this is an HTTPS (secure) address, click tools, click Internet > >> > Options, click Advanced, and check to be sure the SSL and TLS > >> > protocols are enabled under the security section. > >> > > >> > For offline users > >> > > >> > You can still view subscribed feeds and some recently viewed > >> > webpages. To view subscribed feeds > >> > > >> > Click the Favorites Center button , click Feeds, and then click the > >> > feed you > >> > want to view. > >> > > >> > To view recently visited webpages (might not work on all pages) > >> > > >> > Click Tools , and then click Work Offline. > >> > Click the Favorites Center button , click History, and then click > >> > the page you want to view. > >> > > >> > > >> > > >> > > >> > "Lee Derbyshire [MVP]" wrote: > >> > > >> >> > >> >> No, but that seemed the most likely explanation to me. What is > >> >> displayed when you try to use OWA internally? > >> >> > >> >> "circulent" <circul***@discussions.microsoft.com> wrote in message > >> >> news:F391D1B2-AF5B-4D8E-954E-0EE2F49B55A8@microsoft.com... > >> >> > But there already is an A record for mail.domain.local pointing > >> >> > to the internal IP within our DNS server. Do I need something > >> >> > else? > >> >> > > >> >> > Thanks > >> >> > > >> >> > "Lee Derbyshire [MVP]" wrote: > >> >> > > >> >> >> "circulent" <circul***@discussions.microsoft.com> wrote in > >> >> >> message > >> >> >> news:3F283B83-3F90-4DF5-8A2B-0AF127F9D2C5@microsoft.com... > >> >> >> > Hi All, > >> >> >> > > >> >> >> > We are running Exchange 2007 on a dedicated box, with a > >> >> >> > separate Win2003 > >> >> >> > DC > >> >> >> > server. Mail is running fine, and so is access to OWA from > >> >> >> > outside the > >> >> >> > office. For some reason, we cannot access OWA using the > >> >> >> > external FQDN > >> >> >> > (https://mail.domain.com/owa) from inside the office. > > | |||||||||||||||||||||||
