|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
OWA - No external accessHi,
I've searched these forums for an answer to this issue, but have come up dry. Trying to set up OWA - works fine internally. However, when I try to access externally, I get a "Page cannot be displayed" error. Have two servers running SBS 2003. Primary server has Exchange 2003 server running, which is where OWA is hosted. The other one is our web server, and hosts several public websites. Port 80/443 traffic is forwarded to the web server. Not sure how to configure the two servers to pass OWA traffic externally. Any help will be appreciated. Thanks! Tom Since port 80 and 443 are pointing to your web server, you will need to get
another Public IP from your ISP to make this work with Exchange being hosted on another server. Once you get the additional Public IP, have the ISP responsible for your External DNS to create an A Record for the IP similar to webmail.yourdomain.com so it makes it easy for the users to access OWA with a FQDN. -- Show quoteJohn Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2006 Microsoft Certified Partner "Tom" <T**@discussions.microsoft.com> wrote in message news:16083F63-BC30-4F15-BCE7-285D0B1D2536@microsoft.com... > Hi, > > I've searched these forums for an answer to this issue, but have come up > dry. > > Trying to set up OWA - works fine internally. However, when I try to > access > externally, I get a "Page cannot be displayed" error. > > Have two servers running SBS 2003. Primary server has Exchange 2003 > server > running, which is where OWA is hosted. The other one is our web server, > and > hosts several public websites. Port 80/443 traffic is forwarded to the > web > server. > > Not sure how to configure the two servers to pass OWA traffic externally. > Any help will be appreciated. > > Thanks! > Tom Thanks. Once I get an additional IP, how do I assign it? The web server is
behind the firewall / router, which hosts our primary public IP address. Port 25 mail gets forwarded to the Exchange server, 80 & 443 to the web server. Show quote "John Oliver, Jr. [MVP]" wrote: > Since port 80 and 443 are pointing to your web server, you will need to get > another Public IP from your ISP to make this work with Exchange being hosted > on another server. Once you get the additional Public IP, have the ISP > responsible for your External DNS to create an A Record for the IP similar > to webmail.yourdomain.com so it makes it easy for the users to access OWA > with a FQDN. > > -- > John Oliver, Jr > MCSE, MCT, CCNA > Exchange MVP 2006 > Microsoft Certified Partner > > "Tom" <T**@discussions.microsoft.com> wrote in message > news:16083F63-BC30-4F15-BCE7-285D0B1D2536@microsoft.com... > > Hi, > > > > I've searched these forums for an answer to this issue, but have come up > > dry. > > > > Trying to set up OWA - works fine internally. However, when I try to > > access > > externally, I get a "Page cannot be displayed" error. > > > > Have two servers running SBS 2003. Primary server has Exchange 2003 > > server > > running, which is where OWA is hosted. The other one is our web server, > > and > > hosts several public websites. Port 80/443 traffic is forwarded to the > > web > > server. > > > > Not sure how to configure the two servers to pass OWA traffic externally. > > Any help will be appreciated. > > > > Thanks! > > Tom > > > Hi,
You would then need to assign another port to SSL. This will of course cause confusion in your user community (they would have to type https://webmail.yourcompany.com:SSLport . You can avoid this confusion by creating a link on your web server that calls this address. Leif Show quote "Tom" <T**@discussions.microsoft.com> wrote in message news:83A0E2C4-AF7D-411C-9BE7-D698B14B66BF@microsoft.com... > Thanks. Once I get an additional IP, how do I assign it? The web server > is > behind the firewall / router, which hosts our primary public IP address. > Port 25 mail gets forwarded to the Exchange server, 80 & 443 to the web > server. > > "John Oliver, Jr. [MVP]" wrote: > >> Since port 80 and 443 are pointing to your web server, you will need to >> get >> another Public IP from your ISP to make this work with Exchange being >> hosted >> on another server. Once you get the additional Public IP, have the ISP >> responsible for your External DNS to create an A Record for the IP >> similar >> to webmail.yourdomain.com so it makes it easy for the users to access OWA >> with a FQDN. >> >> -- >> John Oliver, Jr >> MCSE, MCT, CCNA >> Exchange MVP 2006 >> Microsoft Certified Partner >> >> "Tom" <T**@discussions.microsoft.com> wrote in message >> news:16083F63-BC30-4F15-BCE7-285D0B1D2536@microsoft.com... >> > Hi, >> > >> > I've searched these forums for an answer to this issue, but have come >> > up >> > dry. >> > >> > Trying to set up OWA - works fine internally. However, when I try to >> > access >> > externally, I get a "Page cannot be displayed" error. >> > >> > Have two servers running SBS 2003. Primary server has Exchange 2003 >> > server >> > running, which is where OWA is hosted. The other one is our web >> > server, >> > and >> > hosts several public websites. Port 80/443 traffic is forwarded to the >> > web >> > server. >> > >> > Not sure how to configure the two servers to pass OWA traffic >> > externally. >> > Any help will be appreciated. >> > >> > Thanks! >> > Tom >> >> >> You will need a Router that supports this. I work with Cisco Products so I
know which Routers support this. You may need to contact your ISP or Router tech support to see if they provide for multiple IP's and port forwarding for these IP's. -- Show quoteJohn Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2006 Microsoft Certified Partner "Tom" <T**@discussions.microsoft.com> wrote in message news:83A0E2C4-AF7D-411C-9BE7-D698B14B66BF@microsoft.com... > Thanks. Once I get an additional IP, how do I assign it? The web server > is > behind the firewall / router, which hosts our primary public IP address. > Port 25 mail gets forwarded to the Exchange server, 80 & 443 to the web > server. > > "John Oliver, Jr. [MVP]" wrote: > >> Since port 80 and 443 are pointing to your web server, you will need to >> get >> another Public IP from your ISP to make this work with Exchange being >> hosted >> on another server. Once you get the additional Public IP, have the ISP >> responsible for your External DNS to create an A Record for the IP >> similar >> to webmail.yourdomain.com so it makes it easy for the users to access OWA >> with a FQDN. >> >> -- >> John Oliver, Jr >> MCSE, MCT, CCNA >> Exchange MVP 2006 >> Microsoft Certified Partner >> >> "Tom" <T**@discussions.microsoft.com> wrote in message >> news:16083F63-BC30-4F15-BCE7-285D0B1D2536@microsoft.com... >> > Hi, >> > >> > I've searched these forums for an answer to this issue, but have come >> > up >> > dry. >> > >> > Trying to set up OWA - works fine internally. However, when I try to >> > access >> > externally, I get a "Page cannot be displayed" error. >> > >> > Have two servers running SBS 2003. Primary server has Exchange 2003 >> > server >> > running, which is where OWA is hosted. The other one is our web >> > server, >> > and >> > hosts several public websites. Port 80/443 traffic is forwarded to the >> > web >> > server. >> > >> > Not sure how to configure the two servers to pass OWA traffic >> > externally. >> > Any help will be appreciated. >> > >> > Thanks! >> > Tom >> >> >> Thanks for all the help. After your first post, I checked-out our
router/firewall (Netscreen 5GT). It supports mapped IP addresses, so I can assign the additional IP address there. I don't think I need to add the port in the URL as Leif suggested, should I? Since port 443 isn't assigned to anything on the Exchange server, I think all I have to do is map the public IP to that server. Also, I'm currently using the web server to forward RPC over HTTP traffic to the Exchange box for our remote users. Don't think the MIP config will affect this traffic, will it? Thanks again. Tom Show quote "John Oliver, Jr. [MVP]" wrote: > You will need a Router that supports this. I work with Cisco Products so I > know which Routers support this. You may need to contact your ISP or Router > tech support to see if they provide for multiple IP's and port forwarding > for these IP's. > > -- > John Oliver, Jr > MCSE, MCT, CCNA > Exchange MVP 2006 > Microsoft Certified Partner > > "Tom" <T**@discussions.microsoft.com> wrote in message > news:83A0E2C4-AF7D-411C-9BE7-D698B14B66BF@microsoft.com... > > Thanks. Once I get an additional IP, how do I assign it? The web server > > is > > behind the firewall / router, which hosts our primary public IP address. > > Port 25 mail gets forwarded to the Exchange server, 80 & 443 to the web > > server. > > > > "John Oliver, Jr. [MVP]" wrote: > > > >> Since port 80 and 443 are pointing to your web server, you will need to > >> get > >> another Public IP from your ISP to make this work with Exchange being > >> hosted > >> on another server. Once you get the additional Public IP, have the ISP > >> responsible for your External DNS to create an A Record for the IP > >> similar > >> to webmail.yourdomain.com so it makes it easy for the users to access OWA > >> with a FQDN. > >> > >> -- > >> John Oliver, Jr > >> MCSE, MCT, CCNA > >> Exchange MVP 2006 > >> Microsoft Certified Partner > >> > >> "Tom" <T**@discussions.microsoft.com> wrote in message > >> news:16083F63-BC30-4F15-BCE7-285D0B1D2536@microsoft.com... > >> > Hi, > >> > > >> > I've searched these forums for an answer to this issue, but have come > >> > up > >> > dry. > >> > > >> > Trying to set up OWA - works fine internally. However, when I try to > >> > access > >> > externally, I get a "Page cannot be displayed" error. > >> > > >> > Have two servers running SBS 2003. Primary server has Exchange 2003 > >> > server > >> > running, which is where OWA is hosted. The other one is our web > >> > server, > >> > and > >> > hosts several public websites. Port 80/443 traffic is forwarded to the > >> > web > >> > server. > >> > > >> > Not sure how to configure the two servers to pass OWA traffic > >> > externally. > >> > Any help will be appreciated. > >> > > >> > Thanks! > >> > Tom > >> > >> > >> > > > The whole reason for adding the additional IP is so if you have mutiple
services that use the same ports you can assign them based on IP. In your case its Port 80 and 443 are needed for Web Server and Exchange. As for forwarding RPC over HTTPs from Web server, you will not need to do this anymore since you have the additional IP and you have configured the Router to Port Forward these directly to the to the Exchange Server. Again, this all asumes your Router support this configuration. -- Show quoteJohn Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2006 Microsoft Certified Partner "Tom" <T**@discussions.microsoft.com> wrote in message news:0A40832D-C7A0-492F-B88C-7BC51B1225B2@microsoft.com... > Thanks for all the help. After your first post, I checked-out our > router/firewall (Netscreen 5GT). It supports mapped IP addresses, so I > can > assign the additional IP address there. I don't think I need to add the > port > in the URL as Leif suggested, should I? Since port 443 isn't assigned to > anything on the Exchange server, I think all I have to do is map the > public > IP to that server. > > Also, I'm currently using the web server to forward RPC over HTTP traffic > to > the Exchange box for our remote users. Don't think the MIP config will > affect this traffic, will it? > > Thanks again. > > Tom > > "John Oliver, Jr. [MVP]" wrote: > >> You will need a Router that supports this. I work with Cisco Products so >> I >> know which Routers support this. You may need to contact your ISP or >> Router >> tech support to see if they provide for multiple IP's and port forwarding >> for these IP's. >> >> -- >> John Oliver, Jr >> MCSE, MCT, CCNA >> Exchange MVP 2006 >> Microsoft Certified Partner >> >> "Tom" <T**@discussions.microsoft.com> wrote in message >> news:83A0E2C4-AF7D-411C-9BE7-D698B14B66BF@microsoft.com... >> > Thanks. Once I get an additional IP, how do I assign it? The web >> > server >> > is >> > behind the firewall / router, which hosts our primary public IP >> > address. >> > Port 25 mail gets forwarded to the Exchange server, 80 & 443 to the web >> > server. >> > >> > "John Oliver, Jr. [MVP]" wrote: >> > >> >> Since port 80 and 443 are pointing to your web server, you will need >> >> to >> >> get >> >> another Public IP from your ISP to make this work with Exchange being >> >> hosted >> >> on another server. Once you get the additional Public IP, have the >> >> ISP >> >> responsible for your External DNS to create an A Record for the IP >> >> similar >> >> to webmail.yourdomain.com so it makes it easy for the users to access >> >> OWA >> >> with a FQDN. >> >> >> >> -- >> >> John Oliver, Jr >> >> MCSE, MCT, CCNA >> >> Exchange MVP 2006 >> >> Microsoft Certified Partner >> >> >> >> "Tom" <T**@discussions.microsoft.com> wrote in message >> >> news:16083F63-BC30-4F15-BCE7-285D0B1D2536@microsoft.com... >> >> > Hi, >> >> > >> >> > I've searched these forums for an answer to this issue, but have >> >> > come >> >> > up >> >> > dry. >> >> > >> >> > Trying to set up OWA - works fine internally. However, when I try >> >> > to >> >> > access >> >> > externally, I get a "Page cannot be displayed" error. >> >> > >> >> > Have two servers running SBS 2003. Primary server has Exchange 2003 >> >> > server >> >> > running, which is where OWA is hosted. The other one is our web >> >> > server, >> >> > and >> >> > hosts several public websites. Port 80/443 traffic is forwarded to >> >> > the >> >> > web >> >> > server. >> >> > >> >> > Not sure how to configure the two servers to pass OWA traffic >> >> > externally. >> >> > Any help will be appreciated. >> >> > >> >> > Thanks! >> >> > Tom >> >> >> >> >> >> >> >> >> Thanks, John!
Show quote "John Oliver, Jr. [MVP]" wrote: > The whole reason for adding the additional IP is so if you have mutiple > services that use the same ports you can assign them based on IP. In your > case its Port 80 and 443 are needed for Web Server and Exchange. As for > forwarding RPC over HTTPs from Web server, you will not need to do this > anymore since you have the additional IP and you have configured the Router > to Port Forward these directly to the to the Exchange Server. Again, this > all asumes your Router support this configuration. > > -- > John Oliver, Jr > MCSE, MCT, CCNA > Exchange MVP 2006 > Microsoft Certified Partner > > "Tom" <T**@discussions.microsoft.com> wrote in message > news:0A40832D-C7A0-492F-B88C-7BC51B1225B2@microsoft.com... > > Thanks for all the help. After your first post, I checked-out our > > router/firewall (Netscreen 5GT). It supports mapped IP addresses, so I > > can > > assign the additional IP address there. I don't think I need to add the > > port > > in the URL as Leif suggested, should I? Since port 443 isn't assigned to > > anything on the Exchange server, I think all I have to do is map the > > public > > IP to that server. > > > > Also, I'm currently using the web server to forward RPC over HTTP traffic > > to > > the Exchange box for our remote users. Don't think the MIP config will > > affect this traffic, will it? > > > > Thanks again. > > > > Tom > > > > "John Oliver, Jr. [MVP]" wrote: > > > >> You will need a Router that supports this. I work with Cisco Products so > >> I > >> know which Routers support this. You may need to contact your ISP or > >> Router > >> tech support to see if they provide for multiple IP's and port forwarding > >> for these IP's. > >> > >> -- > >> John Oliver, Jr > >> MCSE, MCT, CCNA > >> Exchange MVP 2006 > >> Microsoft Certified Partner > >> > >> "Tom" <T**@discussions.microsoft.com> wrote in message > >> news:83A0E2C4-AF7D-411C-9BE7-D698B14B66BF@microsoft.com... > >> > Thanks. Once I get an additional IP, how do I assign it? The web > >> > server > >> > is > >> > behind the firewall / router, which hosts our primary public IP > >> > address. > >> > Port 25 mail gets forwarded to the Exchange server, 80 & 443 to the web > >> > server. > >> > > >> > "John Oliver, Jr. [MVP]" wrote: > >> > > >> >> Since port 80 and 443 are pointing to your web server, you will need > >> >> to > >> >> get > >> >> another Public IP from your ISP to make this work with Exchange being > >> >> hosted > >> >> on another server. Once you get the additional Public IP, have the > >> >> ISP > >> >> responsible for your External DNS to create an A Record for the IP > >> >> similar > >> >> to webmail.yourdomain.com so it makes it easy for the users to access > >> >> OWA > >> >> with a FQDN. > >> >> > >> >> -- > >> >> John Oliver, Jr > >> >> MCSE, MCT, CCNA > >> >> Exchange MVP 2006 > >> >> Microsoft Certified Partner > >> >> > >> >> "Tom" <T**@discussions.microsoft.com> wrote in message > >> >> news:16083F63-BC30-4F15-BCE7-285D0B1D2536@microsoft.com... > >> >> > Hi, > >> >> > > >> >> > I've searched these forums for an answer to this issue, but have > >> >> > come > >> >> > up > >> >> > dry. > >> >> > > >> >> > Trying to set up OWA - works fine internally. However, when I try > >> >> > to > >> >> > access > >> >> > externally, I get a "Page cannot be displayed" error. > >> >> > > >> >> > Have two servers running SBS 2003. Primary server has Exchange 2003 > >> >> > server > >> >> > running, which is where OWA is hosted. The other one is our web > >> >> > server, > >> >> > and > >> >> > hosts several public websites. Port 80/443 traffic is forwarded to > >> >> > the > >> >> > web > >> >> > server. > >> >> > > >> >> > Not sure how to configure the two servers to pass OWA traffic > >> >> > externally. > >> >> > Any help will be appreciated. > >> >> > > >> >> > Thanks! > >> >> > Tom > >> >> > >> >> > >> >> > >> > >> > >> > > >  |
|||||||||||||||||||||||
Other interesting topics