Re: cannot connect to /remote externally
- From: "Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Sun, 1 Apr 2007 13:10:28 -0500
Yep, sounds like the drill ;-).
--
Les Connor [SBS MVP]
"chadsichello" <chadsichello@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:78E4B433-F596-4D07-93C6-E1607599CCD7@xxxxxxxxxxxxxxxx
Hi Les,
I contacted my ISP about this problem earlier today and asked them if they
had any restrictions... and it turns out they do. So we have to upgrade our
account to a static IP account, or use another port for the server. In order
to make this simple, I'm just going to upgrade our account and be done with
this problem.
I must admit I really don't agree with this policy, I believe that
protecting our network and restricting ports should be our responsibility,
not Telus's. But I guess they have their reasons, and reason #1 is likely to
make us pay more...
Thanks for your help on this Les. Best, Chad Sichello / G-SKY
"Les Connor [SBS MVP]" wrote:
Hi Chad,
Are you trying https://remote.ourdomain.com/remote from an external
location, or from within the lan?
Does RWW work from within the lan, if you enter https://<servername>/remote
?
From an external location, what happens if you run this from a command
prompt: telnet remote.ourdomain.com 443 ? Do you get a blank screen with a
flashing cursor, or something else?
Does OWA work? From an external location, type
https://remote.ourdomain.com/exchange.
--
Les Connor [SBS MVP]
"chadsichello" <chadsichello@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3E2F4465-81AF-43C1-992D-DE9CA02E4EDB@xxxxxxxxxxxxxxxx
> Hi Cris, Thanks for the quick reply. We did exactly what you outlined
> below, to the 'T'. There is an A host record setup to point to
> remote.ourdomain.com, it resolves and works fine for the companyweb, > but
> it
> does not work for the Default Website setup in IIS. Any suggestions? > To
> test our server out, I just setup another site up in IIS on port 8181
> (HTTP)
> and port 445 (SSL), then I created an access rule in ISA server, and I
> created a default.htm file that said 'Hello, World!'. It works fine, > we
> can
> access it on both HTTP and HTTPS... I then compared the rule to access > the
> Default Website instance in IIS that the remote services are setup on, > and
> they are setup exactly the same. I'm at my rope's end here, and a
> re-install
> of SBS server is simply not an option. Any suggestions...
> -- > Chad Sichello / G-SKY
>
>
> "Cris Hanna [SBS-MVP]" wrote:
>
>> When you run the ICW to are asked for the URL for the self-signed >> cert,
>> you
>> should enter whatever url you have set up an A record for with your
>> Public
>> DNS provider that points to your public IP
>> This same URL is usually referenced in your MX record.
>>
>> If this A record is setup as remote.domain.com then when you create >> the
>> self signed cert...you should put in remote.domain.com
>> When you attempt to connect to RWW from the outside, the URL should be
>> http://remote.domain.com/remote (or whatever URL followed by /remote)
>> NO
>> PORT NUMBER is required
>> You are correct that a port Number is required to get the companyweb
>>
>> Each time you run the CEICW, if you change the URL or use an IP
>> address...it
>> overwrites the previous cert.
>> Hope that helps
>>
>> -- >> Cris Hanna [SBS-MVP]
>> ------------------------------
>> Please do not contact me directly, only respond in the Newsgroups
>> MVPs do not work for Microsoft
>> ------------------------------
>> Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2
>> "chadsichello" <chadsichello@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in >> message
>> news:C983CB0A-496C-4BFA-AD40-44B3C821B913@xxxxxxxxxxxxxxxx
>> > Hi, I've got a lingering problem. We can access our companyweb
>> > externally
>> > from outside of our network at https://remote.ourdomain.com:444/,
>> > however,
>> > we
>> > cannot access https://remote.ourdomain.com:443/remote (default ssl
>> > port).
>> > We've got SBS 2003 R2 Premium edition. I've ran the Internet
>> > Connection
>> > Wizard twice now, once to create a certificate using ourdomain.com >> > and
>> > once
>> > with the IP address of our server for the cert.
>> >
>> > In both instances we get the error "Internet Explorer cannot display
>> > the
>> > webpage". As I understand it, the Internet Connection Wizard is
>> > supposed
>> > to
>> > just make this "work"... no such luck. Am I missing something???
>> >
>> > -- >> > Chad Sichello / G-SKY
>>
>>
.
- References:
- Re: cannot connect to /remote externally
- From: Cris Hanna [SBS-MVP]
- Re: cannot connect to /remote externally
- From: Les Connor [SBS MVP]
- Re: cannot connect to /remote externally
- From: chadsichello
- Re: cannot connect to /remote externally
- Prev by Date: Re: IIS logs for Exchange/OMA Access
- Next by Date: Re: Physical Disk performance error
- Previous by thread: Re: cannot connect to /remote externally
- Next by thread: Re: Folder Redirection
- Index(es):
Relevant Pages
|
