RE: Problem with Remote Web Workspace, error 403, 12202
- From: "Victor Max" <VictorMax@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Oct 2005 14:52:03 -0700
The problem is solved due to a nice moderator at isaserver.org...
It was a misconfiguration of the RWW Weblistener which the wizzard Internet
and e-mail settings in SBS 2003 doesn't configure...
Victor
"Victor Max" schreef:
> We have a problem with Remote Web Workspace, none of our external users can
> connect from the Internet to the internal network.
> The error code is:
> Error Code: 403 Forbidden. The server denied the specified Uniform Resource
> Locator (URL). Contact the server administrator. (12202)
>
> We have one dual Xeon Server with:
> Windows Small Business Server 2003 Premium Edition SP1 which act as an DNS,
> DHCP, SQL and ISA 2004 Server
> The server has 2 ethernetcards onboard, 1 for External communication and 1
> for the Internal network:
> External NIC > 3Com firewall Router
> Internal NIC > Network Switch
> IP address External NIC 192.168.1.2, 255.255.255.0, Gateway 192.168.1.1
> (Router), DNS 192.168.16.2 (Internal NIC)
> IP address Internal NIC 192.168.16.2, 255.255.255.0, Gateway None, DNS
> 192.168.16.2
> The DNS Server (192.168.16.2) has forward rules to the Public DNS Servers of
> the ISP. DNS is working perfectly for all outbound communications.
> The 3Com Router has the public IP address and ports 80, 443, 3389 and 4125
> ‘mapped’ thru the firewall to the external NIC (192.168.1.2)
> Terminal Services inbound communications works fine, but I’m not sure how to
> set the NAT, both the Router and ISA 2004 can do this, in our case the Router
> does the NAT.
>
> When external users wants to connect from the internet using IE 6 SP2
> browser (https://public-ip-address/remote) they first get a certificate
> security warning because the name on the certificate doesn’t match the name
> of the certificate authority. Just clicking “Yes” on the dialog pane gets
> them thru but then they get the above mentioned 403 warning.
>
> All the settings in de server are on default, we followed all of the
> installation wizards during setup, no errors occurred, installed all the
> updates and patches, no errors in the logfiles of the server. The Server just
> works fine and internally all users can connect to all the published internal
> webserver services like Companyweb, Remote Web Workspace, OWA etc.. and the
> Internet with no restrictions. The only glitch is that connecting to these
> internal webserver services gives them also the same certificate error
> warning, but by just clicking “yes” they can connect to the webservice they
> want.
>
> So I think that it has something to do with ISA Server 2004 SP1 or with the
> Server Certificate. Microsoft recommended the use of the Internet and E-mail
> Connection Wizard at the server, so we did, but with no results. We use the
> FQDN to make a new certificate (in the wizard) like
> (name-of-the-server.domaine-name.local) but looking at the certificate in IIS
> and ISA the name is changed in (publishing.domain-name.local) but the server
> name stays the same in DHCP and DNS etc. I’ve re-runned the wizard and at the
> certificate question I used the Internal IP Address instead of the FQDN but
> with no results, the error 403 stays.
> Looking in certificates of one of my friend’s Small Business 2003 Server
> with no ISA server 2004 I see that the name matches the name of the server
> and that the services are mentioned in the certificate like Remote Web
> connections etc.
> In our certificate there is only one a line which says that the server is
> trusted but that the name is not matching with the certificate. The
> difference is that the certificate has the name
> (publishing.domain-name.local) and the CN name in the certificate is
> (name-of-the-server.domaine-name.local). So I think is has something to do
> with the certificate or ISA… both are using the same certificate, so this
> matches and therefore tackles one of the possible problems.
>
> This problem is beginning to be an annoyance because I’ve read all the
> newsgroups and forums on the Internet and tried all sorts of solutions but
> with no result.
> Maybe I’ve overlooked something (probably) in ISA Server 2004 because this
> is the first time I use ISA…
>
> I hope that someone of you has a solution, anyway thanks in advance.
>
> Victor
>
>
.
- Prev by Date: Re: Publish media server
- Next by Date: Re: Published WEB sites interfering with each other
- Previous by thread: Re: Publish media server
- Next by thread: Re: Published WEB sites interfering with each other
- Index(es):
Relevant Pages
|
Loading
