RE: Problems with OWA in SBS 2003
- From: v-stezhu@xxxxxxxxxxxxxxxxxxxx (Steven Zhu [MSFT])
- Date: Wed, 22 Mar 2006 08:02:21 GMT
Hi,
Thanks for posting here.
From your post, my understanding on this issue is: after you configured theIIS server you cannot steady access OWA from Internet. If I am off base,
please feel free to let me know.
Based on current information, I know you can access OWA from local Network,
but you cannot access OWA from Internet. I believe this issue may caused by
your ISA firewall. So I suggest you try the following steps to solve this
issue:
1. Verify that Default web site is listening on all unassigned IP's -
1.) Start->SBS administrative Console->Internet Information Services.
2.) Expand tree under server to Default web site, right click and select
properties.
3.) On Web Site tab, select "All Unassigned" in the drop down box for the
IP address.
2. Verify that ISA is not started if only the external NIC is enabled (or
connected).
1.) From Start, run type "services.msc" without the "s
2.) Right click Microsoft ISA Server Control, select properties.
3.) Set startup type to disabled.
4.) Reboot server.
Also verify that WebProxy dependency on ISA does not cause ISA to start on
reboot.
If it does, stop the ISA service.
If the issue still persists, please help me to collect the ISA log:
Please help to gather the ISA Logs, the following steps for ISA Server 2000:
1) Open ISA Management, and then point to Monitoring Configuration | Logs
2) Double click ISA Server Firewall Service in the right pane, click to
select Enable Logging for this service, click Fields tab, click Select All,
and then click OK.
3) Please repeat Step 2) to enable logging IP Packet Filter and Web Proxy
Services.
4) Run command "net stop isactrl" (without the quotation marks) to stop all
ISA Services.
5) Backup all files in the folder C:\Program Files\Microsoft ISA
Server\ISALogs, and then delete them.
6) In ISA Management | <server name> | Monitoring | Services, start all ISA
services.
7) Reproduce the issue.
8) Wait for about 3 minutes, and then send me that day's firewall, web
proxy and IP Packet filter log in C:\Program Files\Microsoft ISA
Server\ISALogs. You can compress logs into .zip file.
Firewall log: FWSEXTDyyyymmdd.log
Web Proxy log: WEBEXTDyyyymmdd.log
IP Packet Filter log: IPPEXTDyyyymmdd.log
Please also let me know the IP address of the testing client.
Help to gather the ISAinfo:
You can download this utility from:
http://www.isatools.org/isainfo.vbe
Run it on the ISA server. Then attach the ISAINFO report to me at your
earliest convenience.
You can send ISAinfo and ISA logs directly to my working mailbox:
v-stezhu@xxxxxxxxxxxxx
The following steps for ISA Server 2004:
1. 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.
2. Please also help to gather the ISA logs:
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-stezhu@xxxxxxxxxxxxx
Please let me know the above information so that I can provide the further
assistance on the problem. I am looking forward to your reply.
Have a nice day.
Best Regards,
Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile
and access the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- Follow-Ups:
- Re: Problems with OWA in SBS 2003
- From: Cardoso
- Re: Problems with OWA in SBS 2003
- References:
- Problems with OWA in SBS 2003
- From: Cardoso
- Problems with OWA in SBS 2003
- Prev by Date: Re: store.exe repeatedly accessing c:\windows\temp
- Next by Date: Re: Weird problem with password authentication
- Previous by thread: Problems with OWA in SBS 2003
- Next by thread: Re: Problems with OWA in SBS 2003
- Index(es):
Relevant Pages
|
