Re: RWW and OWA don't work remotely; VPN does
- From: "Russ Grover" <russ@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 24 Sep 2005 21:29:46 -0700
Now that' I've thought about this...
no don't change the Server Certificate
Should be Something like Server.YourDomain.com
And just a thought? is there a subdomain (Server.YourDomain.com)
from your domain pointing to your external IP?
You should be able to Ping server.yourdomain.com and get your external IP
If you can't call where you Host and have them Create a Subdomain and point
it to your external IP
Russ
--
Russ Grover
Small Business IT Support
SBS Rocks!
Portland/Beaverton OR
Email: Sales at SmallBusinessITSupport.com
Website: http://www.SmallBusinessITSupport.com
"bjammin" <bjammin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3ACB5D85-E6ED-4C3A-A912-DACC0443BCD1@xxxxxxxxxxxxxxxx
> Hi Russ and thanks for the reply...
>
> I ran CEICW and all services including RWW and OWA are enabled. When I
> ran
> it again, I tried changing the server certificate to the public IP
> address,
> instead of the FQDN, but ultimately got the same results, "The page cannot
> be
> displayed "The page you are looking for is currently unavailable. The Web
> site might be experiencing technical difficulties, or you may need to
> adjust
> your browser settings."
>
> I've also tried using the DMZ zones in the routers, instead of forwarding
> specific ports, but that didn't fix the RWW/OWA problem either.
>
> Additionally, RWW and OWA work from within the network, using the server's
> local IP as part of the string. It just doesn't seem to work remotely.
> VPN
> works remotely, so port 1723 is being forwarded. RDC works remotely, so
> port
> 3389 is being forwarded. Just browsing to the public IP with IE,
> unsecured,
> works, so port 80 is being forwarded.
>
> I had initially followed some recommendations made by MS's Small IT
> solution
> document series regarding adding additional DNS zones internally, so that
> users connected locally could use the same path to access RWW that they
> would
> use remotely. I ended up removing those zones, because it was confusing
> the
> 3rd party POP3 software that was pulling down the mail from an offsite web
> hoster and feeding it to Exchange. Is there any way that that might have
> affected RWW?
>
> "Russ Grover" wrote:
>
>> Run Internet Connection Wizard (CEICW)
>> And see if RWW and OWA access is Enabled?
>>
>> Russ
>>
>> --
>> Russ Grover
>> Small Business IT Support
>> SBS Rocks!
>> Portland/Beaverton OR
>> Email: Sales at SmallBusinessITSupport.com
>> Website: http://www.SmallBusinessITSupport.com
>>
>>
>> "bjammin" <bjammin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:FFB90F36-0EA6-4C33-B12F-55A821B2FC5A@xxxxxxxxxxxxxxxx
>> > Hello all,
>> > SBS2003 newbie here.
>> >
>> > I recently installed SBS2003 server and everything is working fine
>> > except
>> > RWW and OWA remotely. RWW and OWA work from within the LAN but not
>> > remotely.
>> >
>> > Details:
>> > server: single-homed SBS2003 box with SP1 installed
>> > internet: static-IP DSL
>> > routers: (2) Netgear FVS114 routers back-to-back
>> > router IP configs:
>> > perimeter router (connected directly to DSL modem)
>> > WAN IP: set as publicIP assigned by ISP
>> > LAN IP: 10.5.xxx.xxx
>> > ports: 25, 80, 443, 444, 3389, 4125 forwarded to DMZ router's WAN IP
>> > DMZ router (connected directly to server)
>> > WAN IP: 10.5.xxx.xxx (same subnet as perimeter router's LAN IP)
>> > LAN IP: 192.168.xxx.xxx
>> > ports: 25, 80, 443, 444, 3389, 4125 forwarded to server's IP
>> >
>> > On the local LAN, RWW works using https://serverIP/remote and OWA works
>> > using https://serverIP/exchange. From the outside, trying to RWW at
>> > https://publicIP/remote displays "page cannot be found" and the same
>> > happens
>> > trying to OWA at https://publicIP/exchange. I can actually RDC into
>> > the
>> > server remotely, without a VPN connection, just using the publicIP, as
>> > port
>> > 3389 is forwarded to server, so it looks like at least ports 3389 and
>> > 1723
>> > (VPN works remotely) are being forwarded successfully through the 2
>> > routers.
>> >
>> > ISA isn't installed. I've never used Telnet before, but if it means
>> > using
>> > HyperTerminal to see if it connects at port 443, then it works on the
>> > local
>> > LAN (just displays "connected" on the status bar), but does not work
>> > remotely. By the way, clients are WinXP Pro with SP2.
>> >
>> > I called and confirmed with the ISP that they do not block port 443.
>> >
>> > Note: (2) routers were installed, as there was a need for a DMZ zone
>> > for
>> > additional computers connecting to the same internet connection, but
>> > belonging to a different company.
>> >
>> > Any help would be appreciated.
>> >
>> > Thank you.
>>
>>
>>
.
- Prev by Date: Re: RWW and OWA don't work remotely; VPN does
- Next by Date: Re: When create new user, email addresss not created
- Previous by thread: Re: RWW and OWA don't work remotely; VPN does
- Next by thread: Re: Intelligent Message Filter DOES NOT show after intalled.
- Index(es):
Relevant Pages
|
