OWA & RWW unable to connect [WiredBox.Net

> Hello,
>
> Thanks for posing in our newsgroup.
>
> Please take following steps to narrow down this problem:
>
> Step 1: Go to the FVS318 router, there should be IP address assigned from
> DDNS, please record this address. Then ping mycompany.dyndns.org, will the
> two IP address be the same one?
>
> Step 2: Please visit http://IP/remote instead of
> http://mycompany.dyndns.org/remote, can you visit successfully? If not, can
> you see DNS error?
>
> Step 3: Please do the following test:
>
> 1. Connect a laptop to the External NIC of the SBS server.
> 2. Assign the laptop IP address 192.168.0.10.
> 3. Can you visit https://192.168.0.2/remote?
> (Suppose the external NIC IP of SBS is 192.168.0.2)
> 4. If yes, the problem is caused by the DDNS configuration on router.
> 5. If you still cannot visit RWW, that's caused by SBS configuration,
> please help me collect the following information for further research:
>
> 1. 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.
>
> 2. 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.
>
> 3. Gather IIS log:
>
> 1) Open IIS snap-in.
> 2) Right click Default Web Site and click Properties.
> 3) Uncheck the "Enable Logging" box and click Apply.
> 4) Go to C:\WINDOWS\system32\LogFiles\W3SVC1 folder and move all files to
> a backup location.
> 5) Check "Enable Logging" box and click OK.
> 6) Run IISReset command.
> 7) Reproduce the problem and send the log file in
> C:\WINDOWS\system32\LogFiles\W3SVC1 folder to me for research.
>
> 4. Gather IIS Metabase:
>
> 1) Download the IIS Resource Kit tools from the following page:
> http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
> B628-ADE629C89499&displaylang=en
> 2) Install it, run MBExplorer (Metabase Explorer)
> 3) Right click the "LM" node and choose "Export to file".
> 4) Specify a file name, specify the password and finish the export.
> 5) Send the file and the password to me.
>
> Please send the information to v-robeli[ at ]microsoft.com with subject:
> 39795680-OWA & RWW unable to connect.
>
> I am looking forward to hear from you.
>
> If you need further assistance, please don't hesitate to let me know.
>
> Best regards,
>
> Robert Li(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: OWA & RWW unable to connect
> <thread-index: Ace+6UuKMt5ZyYh0QQWGx6Ozo6IXpw==
> <X-WBNR-Posting-Host: 207.46.192.207
> <From: =?Utf-8?B?SWFuIEVtcHNvbg==?= <IanEmpson[ at ]discussions.microsoft.com>
> <Subject: OWA & RWW unable to connect
> <Date: Thu, 5 Jul 2007 02:46:00 -0700
> <Lines: 22
> <Message-ID: <C4A48487-5430-4897-BD2A-431F0570058C[ at ]microsoft.com>
> <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.2826
> <Newsgroups: microsoft.public.windows.server.sbs
> <Path: TK2MSFTNGHUB02.phx.gbl
> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:48327
> <NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
> <X-Tomcat-NG: microsoft.public.windows.server.sbs
> <
> <Hello
> <Running SBS 2003 Premium R2 with SP2, ISA 2004 SP3. 2 x NIC's, internal
> <network 192.168.6.*; External network 192.168.0.* - router is Netgear
> FVS318
> <router/firewall on 192.168.0.1. Broadband dynamic ip connection. Ports
> open
> <on router include 80, 443, 444, 4125. Have run CEICW to enable firewall -
> OWA
> <& RWW have 'allow access' selected. Web certificate has been set up to
> <mycompany.dyndns.org - worked successfully before on SBS2000 to access OWA.
> <Can browse internally companyweb, OWA and RWW locally on server and
> <connected workstations. Can browse internet internally.
> <Cannot browse OWA, RWW etc externally. Have run CEICW many times, switched
> <options on and off but no success using
> http://mycompany.dyndns.org/exchange.
> <Have tried https for that as well as http://mycompany.dyndns.org/remote
> <Web pages display either 404, 403 or DNS error depending on how I try
> <options. I'm confident the router is working ok - some of the pages have
> made
> <404 errors mentioning ISA 2004 and the server name. Have tried telnet from
> <laptop connected to hub between external NIC and router and got
> connections
> <(blank screen) on 443 and 444. Wonder if ISA is not set up right but have
> <only used wizards. Have used CEICW to switch off firewall and seem to have
> <had success connecting to RWW and OWA login screen - but the pc was on the
> <internal network and using the dyndns address.
> <Any suggestions please!
> <Thanks
> <
>
>

> Hi Iran,
>
> I check your following IIS settings, they are exactly the same as my test
> machine.
>
> Default first website
> Remote virtual directory
> Exchange virtual directory
>
> When I check the ISA info, I found is not correctly collected. Please help
> me collect again. Thanks for your time and understanding.
>
> 1. 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.
>
> 2. 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.
>
> Best regards,
>
> Robert Li(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: OWA & RWW unable to connect
> <thread-index: Ace/tvB8sjsdbUVJQr+YjNoM6EActg==
> <X-WBNR-Posting-Host: 207.46.193.207
> <From: =?Utf-8?B?SWFuIEVtcHNvbg==?= <IanEmpson[ at ]discussions.microsoft.com>
> <References: <C4A48487-5430-4897-BD2A-431F0570058C[ at ]microsoft.com>
> <gLj3EY7vHHA.4612[ at ]TK2MSFTNGHUB02.phx.gbl>
> <Subject: RE: OWA & RWW unable to connect
> <Date: Fri, 6 Jul 2007 03:18:04 -0700
> <Lines: 191
> <Message-ID: <E53D2F4B-A16C-4841-877D-E4C972461192[ at ]microsoft.com>
> <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.2826
> <Newsgroups: microsoft.public.windows.server.sbs
> <Path: TK2MSFTNGHUB02.phx.gbl
> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:48618
> <NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
> <X-Tomcat-NG: microsoft.public.windows.server.sbs
> <
> <Thankyou Robert for your detailed reply - I will go through your steps
> over
> <the weekend/early next week and report back.
> <Thanks again
> <
> <"Robert Li [MSFT]" wrote:
> <
> <> Hello,
> <>
> <> Thanks for posing in our newsgroup.
> <>
> <> Please take following steps to narrow down this problem:
> <>
> <> Step 1: Go to the FVS318 router, there should be IP address assigned
> from
> <> DDNS, please record this address. Then ping mycompany.dyndns.org, will
> the
> <> two IP address be the same one?
> <>
> <> Step 2: Please visit http://IP/remote instead of
> <> http://mycompany.dyndns.org/remote, can you visit successfully? If not,
> can
> <> you see DNS error?
> <>
> <> Step 3: Please do the following test:
> <>
> <> 1. Connect a laptop to the External NIC of the SBS server.
> <> 2. Assign the laptop IP address 192.168.0.10.
> <> 3. Can you visit https://192.168.0.2/remote?
> <> (Suppose the external NIC IP of SBS is 192.168.0.2)
> <> 4. If yes, the problem is caused by the DDNS configuration on router.
> <> 5. If you still cannot visit RWW, that's caused by SBS configuration,
> <> please help me collect the following information for further research:
> <>
> <> 1. 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.
> <>
> <> 2. 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.
> <>
> <> 3. Gather IIS log:
> <>
> <> 1) Open IIS snap-in.
> <> 2) Right click Default Web Site and click Properties.
> <> 3) Uncheck the "Enable Logging" box and click Apply.
> <> 4) Go to C:\WINDOWS\system32\LogFiles\W3SVC1 folder and move all files
> to
> <> a backup location.
> <> 5) Check "Enable Logging" box and click OK.
> <> 6) Run IISReset command.
> <> 7) Reproduce the problem and send the log file in
> <> C:\WINDOWS\system32\LogFiles\W3SVC1 folder to me for research.
> <>
> <> 4. Gather IIS Metabase:
> <>
> <> 1) Download the IIS Resource Kit tools from the following page:
> <>
> http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
> <> B628-ADE629C89499&displaylang=en
> <> 2) Install it, run MBExplorer (Metabase Explorer)
> <> 3) Right click the "LM" node and choose "Export to file".
> <> 4) Specify a file name, specify the password and finish the export.
> <> 5) Send the file and the password to me.
> <>
> <> Please send the information to v-robeli[ at ]microsoft.com with subject:
> <> 39795680-OWA & RWW unable to connect.
> <>
> <> I am looking forward to hear from you.
> <>
> <> If you need further assistance, please don't hesitate to let me know.
> <>
> <> Best regards,
> <>
> <> Robert Li(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: OWA & RWW unable to connect
> <> <thread-index: Ace+6UuKMt5ZyYh0QQWGx6Ozo6IXpw==
> <> <X-WBNR-Posting-Host: 207.46.192.207
> <> <From: =?Utf-8?B?SWFuIEVtcHNvbg==?= <IanEmpson[ at ]discussions.microsoft.com>
> <> <Subject: OWA & RWW unable to connect
> <> <Date: Thu, 5 Jul 2007 02:46:00 -0700
> <> <Lines: 22
> <> <Message-ID: <C4A48487-5430-4897-BD2A-431F0570058C[ at ]microsoft.com>
> <> <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.2826
> <> <Newsgroups: microsoft.public.windows.server.sbs
> <> <Path: TK2MSFTNGHUB02.phx.gbl
> <> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:48327
> <> <NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
> <> <X-Tomcat-NG: microsoft.public.windows.server.sbs
> <> <
> <> <Hello
> <> <Running SBS 2003 Premium R2 with SP2, ISA 2004 SP3. 2 x NIC's, internal
> <> <network 192.168.6.*; External network 192.168.0.* - router is Netgear