RE: Websites hosted on SBS partially load when accessed externally

Hi Ryan,

Thanks for posting here!

Fro your description, I understand that your issue is: the CRM websites can
not loaded first and you need refresh page some times to load it. If I am
off base, please don¡¯t hesitate to let me know.
=====================
Before we go further, please help me collect some information to analyze
the issue:

1. Does the issue happen when you open RWW site through internet
(http://serverFQDN/remote)?

2. Does the issue happen when you load the CRM sites through internet using
server external IP address (http://xx.xx.xx.xx/xx)?

3. Try to use Firefox to open the web page, how about the result?

4. Does the issue happen from any internet computers? Change to other PCs
to try.

5. Do you find any error event logs in Event Viewer? If so, give me detail
info.

6. How you publish the CRM websites? Did you enable SSL listeners? If you
enabled SSL listeners, you need to configure a server certificate.

For the error code, the issue should be related with ISA configuration. I
suggest that you reconfigure the both sites in ISA 2004 to try to resolve
the issue.

Please check following KB article to ensure you have published the websites
correctly.
How To Configure the Web Publishing Service to Work with Internet Security
and Acceleration Server in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323426

=====================

How about the result? If the issue persists, please rename the web.config
file under the C:\Inetpub\wwwroot folder to web.config.old file, then try
again to see if there is an update.

=====================
And also I would like to collect some information to do further
troubleshooting:

1. Shedule 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. Please add files to a zip file and send to
v-yanniw@xxxxxxxxxxxxx

14. Please also let me know the IP address of the testing clients so that
I can filter the data.

I appreciate you time and effort. I am currently standing by for you about
the test result. I am always happy to be of further assistance.

Have a nice day!

Best Regards,

Jenny Wu
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.
--------------------

>I have two SBS 2003 premium with SP1 + ISA 2004 servers. Really, the only
>difference between them is the external NIC IPs and one has CRM installed.
>
>I configured my domain settings at our host to include dns records for
>crm.mydomain.com and projects.mydomain.com pointing to the IP of the
second
>SBS server (the server hosting these two websites)
>
>The problem is that when opening either of these two sites they don't
always
>load on the first try. I often have to refresh to get a login window.
Once
>I login navigation is just as trivial. If I constantly refresh the page
>sometimes it loads fine, more often than that it loads partially, and
>sometimes the site won't refresh at all. These pages load fine internally
>(on SBS workstations) as http://crm.mydomain.com or http://crm and
>http://projects.mydomain.com or http://projects
>
>What could cause web requests to fail intermittently like this?
>
>Here's the error of whatever sections can't refresh:
>
>The page cannot be displayed
>Explanation: The page you requested could not be reached.
>
>Try the following:
>Refresh page: Search for the page again by clicking the Refresh button.
The
>timeout may have occurred due to Internet congestion.
>Check spelling: Check that you typed the Web page address correctly. The
>address may have been mistyped.
>Access from a link: If there is a link to the page you are looking for,
try
>accessing the page from that link.
>
>Technical Information (for support personnel)
>Error code: 12206
>Background: The page you requested could not be reached.
>

.

Loading