Re: Updated info
- From: "Frank McCallister SBS MVP" <anonymous>
- Date: Sat, 18 Jun 2005 18:02:15 -0500
Hi MG
Two ways to do this. If you are getting your mail by POP3 from ISP then the
A record to your FQDN goes to the mail server at your ISP and you would need
an A record to servername.FQDN and access by Https://servername.fqdn/remote
if you are hosting your own mail and it is working you already have an A
record and you access with Https://fqdn/remote
The other approach if you are popping mail is to use
Https://IPaddress/remote
Whichever approach you use rerun CEICW from todo list and install
certificate with name you are using ie servername.fqdn, fqdn, or
xxx.xxx.xxx.xxx This will setup RWW and OWA with the proper destination sets
and security cert in ISA
--
Frank McCallister SBS MVP
COMPUMAC
"VG" <VG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2EF76F38-77FB-47B4-B06A-5FE8E8E22A4A@xxxxxxxxxxxxxxxx
> Susan,
> After much digging today, this MS kb article has solved at least part of
> the
> puzzle:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823379
> Now I can login on the server and on the clients and access RWW. All
> that's
> left to do is figure out how to access it from an outside PC. I'm thinking
> it's related to the FQDN. We have a dot com name but it's not actually
> being
> used other than for email. I've seen info on having the ISP assign an A
> pointer or record??? Is this what needs to be done for outside access??
> Thanx for your time as it's greatly appreciated,
> MG
>
>
> "Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
>
>> Ray-Ism: Are you getting prompted for username and password when you
>> connect to http://localhost/backup and http://localhost/remote?:
>> http://msmvps.com/bradley/archive/2004/12/08/23029.aspx
>>
>>
>> Try that
>>
>> VG wrote:
>>
>> >We finally got the info from our DSL ISP to setup the router using the
>> >static
>> >IP addresses. It seems they assign you a block with a certain type of
>> >account
>> >and then the router has to be setup a certain way to use them. Basically
>> >the
>> >first IP address is the gateway so you set this in the router and set
>> >the
>> >following one to your external NIC. The external NIC's IP info is set to
>> >correspond and web access now works.
>> >However, we still can't access http or https://localhost/remote and
>> >after
>> >modifying the C:\Inetpub\Remote\web.config to allow extended error
>> >reporting,
>> >we get this on a failed login attempt:
>> >Server Error in '/Remote' Application.
>> >--------------------------------------------------------------------------------
>> >
>> >Access to the path
>> >"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
>> >ASP.NET Files\remote\3f1585d2\3070828a" is denied.
>> >Description: An unhandled exception occurred during the execution of the
>> >current web request. Please review the stack trace for more information
>> >about
>> >the error and where it originated in the code.
>> >
>> >Exception Details: System.UnauthorizedAccessException: Access to the
>> >path
>> >"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
>> >Files\remote\3f1585d2\3070828a" is denied.
>> >
>> >ASP.NET is not authorized to access the requested resource. Consider
>> >granting access rights to the resource to the ASP.NET request identity.
>> >ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5
>> >or
>> >Network Service on IIS 6) that is used if the application is not
>> >impersonating. If the application is impersonating via <identity
>> >impersonate="true"/>, the identity will be the anonymous user (typically
>> >IUSR_MACHINENAME) or the authenticated request user.
>> >
>> >To grant ASP.NET write access to a file, right-click the file in
>> >Explorer,
>> >choose "Properties" and select the Security tab. Click "Add" to add the
>> >appropriate user or group. Highlight the ASP.NET account, and check the
>> >boxes
>> >for the desired access.
>> >
>> >Source Error:
>> >
>> >An unhandled exception was generated during the execution of the current
>> >web
>> >request. Information regarding the origin and location of the exception
>> >can
>> >be identified using the exception stack trace below.
>> >(Stack trace omitted for brevity)
>> >Ports 443 and 4125 are being forwarded to the IP of the external NIC as
>> >well. We're still pulling our hair out on this one (What little is
>> >left..hehe). BTW, we can access OWA on the server and attached clients.
>> >Thanx,
>> >MG
>> >
>> >"VG" wrote:
>> >
>> >
>> >
>> >>We would like to setup RWW on our network. We have SBS 2003 with ISA
>> >>and a
>> >>DSL broadband connection with the requisite 2 NIC setup. Our DSL ISP
>> >>has
>> >>assigned us a block of 5 IP addresses. We've run CEICW and have full
>> >>web
>> >>access from server and all clients. When we type in https://one of 5 ip
>> >>addresses/remote, we get the page cannot be displayed.
>> >>We've opened ports 443 and 4125 in the Netopia router but still can't
>> >>get a
>> >>RWW logon prompt. Any advice or pointers to info would be greatly
>> >>appreciated.
>> >>Regards,
>> >>MG
>> >>
>> >>
>>
>> --
>> An open letter to the Security Community::
>> http://msmvps.com/bradley/archive/2004/12/12/23540.aspx
>>
.
- References:
- RWW setup through ISA, DSL, etc.
- From: VG
- Updated info
- From: VG
- Re: Updated info
- From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- Re: Updated info
- From: VG
- RWW setup through ISA, DSL, etc.
- Prev by Date: Re: Back up theory?
- Next by Date: Re: Back up theory?
- Previous by thread: Re: Updated info
- Next by thread: SMTP Connector Forward Vs. DNS
- Index(es):
Relevant Pages
|
