Updated info
- From: "VG" <VG@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 18 Jun 2005 14:22:01 -0700
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
.
- Follow-Ups:
- Re: Updated info
- From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- Re: Updated info
- References:
- RWW setup through ISA, DSL, etc.
- From: VG
- RWW setup through ISA, DSL, etc.
- Prev by Date: Re: Mirrored Drive
- Next by Date: Re: User with Access to Sharepoint Only
- Previous by thread: Re: RWW setup through ISA, DSL, etc.
- Next by thread: Re: Updated info
- Index(es):
Relevant Pages
|
|
