RE: Remote Web Workspace
- From: v-terliu@xxxxxxxxxxxxxxxxxxxx (Terence Liu [MSFT])
- Date: Wed, 11 Apr 2007 03:43:13 GMT
Hello Customer,
Thank you for posting here.
According to your description, I understand that you get error http 403
when you try to access RWW. If I have misunderstood the problem, please
don't hesitate to let me know.
Based on my experience, this issue can occur if the URL you use in the Web
browser to access OWA, RWW and other web sites that does not match the name
in ISA server 2004 web publishing rules. I suggest we try the following
steps to see if we can resolve this issue:
Please re-run the CEICW and specify the FQDN that you will use to access
the sites as the web server certificate. To do so:
1. On the SBS 2003 Server open the Server Management console. Go to
Standard Management\To Do List.
2. Click the "Connect to the Internet" link.
3. Choose not to change the connection type and click Next. On the Firewall
page, select "Enable firewall" and click Next (I suppose you have 2 network
adapters in SBS 2003).
4. On the "Services Configuration" page, select all the items and then
click Next.
5. On the "Web Services Configuration" page, make sure "Allow access to the
entire Web site from the Internet" is selected. If you select "Allow access
to only the following Web site services from the Internet", make sure
"Remote Web Workplace" item is selected. Click Next.
6. On the "Web Server Certificate" page, choose to create a new Web server
certificate and then type the public FQDN that you will use to access OWA
(for example, if your public FQDN that you use to access the sites is
mail.domain.com, you should type mail.domain.com as the new certificate
name). If you already requested a certificate with the name
"mail.domain.com" from a third party CA, you can choose "Use a Web server
certificate from a trusted authority" and then import the certificate.
7. Go through the remaining steps. The wizard will automatically configure
the ISA 2004 to securely publish the RWW site.
8. If you have a router or hardware firewall, configure it to forward
inbound traffic on TCP port 80 and 443 to the SBS server's external
address.
9. Then check if you can access RWW using
https://server.DomainName.com/remote.
For more information regarding this problem, see:
842612 You receive a "403 Forbidden" message when you try to connect to a
Web
http://support.microsoft.com/?id=842612
If the problem persists, please help me gather the following info:
1. What detail error message did you receive when you access RWW from
internet clients? Please capture a screenshot on the IE error page and send
the .jpg file to my mailbox at v-terliu@xxxxxxxxxxxxx
2. How many NIC is installed on the SBS box?
3. Can you access the RWW from internal clients using https://<internal IP
of the SBS Server>/remote?
4. On the SBS Server itself, can you view the RWW using
https://localhost/remote?
5. Please help to gather the ISA Info:
1) Download the file from the following URL:
http://www.isatools.org/isainfo/ISAInfo.zip
2) Extract all files to a folder on ISA server.
3) Double click Isainfo.js. This will generate 2 files
ISAInfo2004-<computer-name>.log and ISAInfo2004-<computer-name>.xml in the
current folder.
4) Please send these files to me at v-terliu@xxxxxxxxxxxxx
6. Please also help to gather the ISA logs:
1) Schedule a down time.
2) Open ISA 2004 management console.
3) Expand the server node and highlight 'Monitoring'.
4) In the right pane, switch to the 'Logging' tab, make sure the 'Task
Pane' is showed there.
5) In the 'Task Pane', click 'Configure Firewall Logging' under 'Logging
Tasks', and then switch the 'log storage format' from 'MSDE database'
(default) to 'File'.
6) Switch to the 'Fields' tab, click 'Select All', and then click OK.
7) In the 'Task Pane', click 'Configure Web Proxy Logging' under 'Logging
Tasks', and then switch the 'log storage format' from 'MSDE database'
(default) to 'File'.
8) Switch to the 'Fields' tab, click 'Select All', and then click OK.
9) Click 'Apply' to save changes and update the configuration.
10) Temporarily disable the Firewall service. To do that, please click
Monitoring | Services tab, and then right click 'Microsoft Firewall' to
choose 'Stop'.
11) Clear the current existing W3C logs. To do that, go to the log saving
directory and clean any existing .W3C logs. By default, the logs will be
saved to 'C:\Program Files\Microsoft ISA Server\ISALogs'. (Some MDF may not
be able to deleted, that's normal.) You may backup them first and then
delete them.
12) Go back to the ISA 2004 management console, and then Start the stopped
'Microsoft Firewall' service.
13) Reproduce the problem, stop the service, and then gather the resulting
W3C files to me for analysis.
14) Please also let me know the IP address of the testing clients so that I
can filter the data.
Hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Remote Web Workspace
| thread-index: Acd7VwF2a4Yfh1QpQdaW1MYWm0sdbQ==
| X-WBNR-Posting-Host: 86.8.101.149
| From: =?Utf-8?B?SWFuIEd1cmRlbg==?= <iang@xxxxxxxxxxxxxxxxxxxx>
| Subject: Remote Web Workspace
| Date: Tue, 10 Apr 2007 03:00:02 -0700
| Lines: 15
| Message-ID: <7C9D4177-E0D0-4AAE-A0C3-EE6307BBDF0A@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:28843
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi,
|
| I ma having problems access the remote web workspace both from inside the
| company newtork and remotely.
|
| Exchange works fine and can access Outlook from inside and remotely.
|
| It is just when you click the Remote Web Workspace i get a HTTP 403
| Forbidden message - The Website declined to show this webpage with a note
| 'Most likely causes:
| This website requires you to log in.'
|
| HELP!!
|
| Thanks
|
.
- Follow-Ups:
- RE: Remote Web Workspace
- From: Ian Gurden
- RE: Remote Web Workspace
- Prev by Date: Re: Setting up a Connection
- Next by Date: Re: People who pay for internet may wish to know about WSUS
- Previous by thread: Re: Setting up a Connection
- Next by thread: RE: Remote Web Workspace
- Index(es):
Relevant Pages
|
Loading
