Prev: CompanyWeb Broken
Next: Logon credential request when using website blacklists?
From: mcseman on 15 Jun 2010 10:30
Hi All

We have an engineering client who cannot connect to one particular website
www.schydraulic.com

Client network setup:
SBS 2003 Premium, ISA 2004, 2 nics.

Internet--->Ext nic 192.168.0.2-->Int nic 192.168.16.2--->Internal network

Client installation was carried out over 3 years ago and they have had no
other browsing issues except this one website they have only recently
neededaccess to.
Cannot connect to this site from any workstation or SBS server.

We have another client who has an identical SBS setup and they can access
this website.

I have setup logging in isa and returns the following when trying this
website:

Failed connection attempt Web proxy (forward)

10060 A connection attempt failed because the party did not respond properly
after a period of time
or established connection failed because connection host has failed to
respond.

I have done the usual things of checking dns, pinging the site which
resolves ok, checked the isa access rules for anything that could cause this
problem and have now run out of ideas.

I would be very grateful for help with this.

Thanks,

David

From: "Robbin Meng [MSFT]" on 16 Jun 2010 05:51

Hello Daivd,

Thanks for your post.

1. Can you ping schydraulic.com from workstation or from SBS server? Then how about using http://DestinationServerIP to access that website?
If you can use http://DestinationServerIP to access that website, please add a HOST record in your HOST file to force DNS name resolution. Also, add *.schydraulic.com to your IE trusted website list(or
use other web browser instead of IE to try)

NsLookup tool:
http://network-tools.com/nslook/Default.asp


2. What device is connected in front of your SBS external NIC? Do you have any hardware router or firewall placed between the SBS server and the public Internet?
If there is any, please DOUBLE confirm that no rules or blacklist are used to block this (or this kind of )website.


BTW, try to check and delete the Web Cache on ISA server to have a try:
--------------------
Please refer to the following articles steps to delete the old website cached file.

How to Delete the Web Cache on Internet Security and Acceleration Server
http://support.microsoft.com/kb/301471/en-us

How to delete the Web cache in Internet Security and Acceleration (ISA) Server 2006 or in ISA Server 2004
http://support.microsoft.com/kb/838248/en-us

Hope this helps.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support


From: mcseman on 16 Jun 2010 10:46
Hi Robbin
Thank you very much for your reply.
In answer to your questions:

I can ping the website schydraulic.com.
I cannot access the site using http://ip address. I receive the same timout
10060 error.

I have tried 2 other browsers (Firefox and opera) to access the site with
the same error.
We have a netgear DG834 adsl modem router in front of the sbs server which
has caused no errors in the past 3 years of operation.
I have checked both isa rules and the netgear firewall rules for anything
connected to this site and there are none.
The isa server is not configured for web caching.

Hope this provides the informatiom you need.

Best regards

David

""Robbin Meng [MSFT]"" wrote:

>
> Hello Daivd,
>
> Thanks for your post.
>
> 1. Can you ping schydraulic.com from workstation or from SBS server? Then how about using http://DestinationServerIP to access that website?
> If you can use http://DestinationServerIP to access that website, please add a HOST record in your HOST file to force DNS name resolution. Also, add *.schydraulic.com to your IE trusted website list(or
> use other web browser instead of IE to try)
>
> NsLookup tool:
> http://network-tools.com/nslook/Default.asp
>
>
> 2. What device is connected in front of your SBS external NIC? Do you have any hardware router or firewall placed between the SBS server and the public Internet?
> If there is any, please DOUBLE confirm that no rules or blacklist are used to block this (or this kind of )website.
>
>
> BTW, try to check and delete the Web Cache on ISA server to have a try:
> --------------------
> Please refer to the following articles steps to delete the old website cached file.
>
> How to Delete the Web Cache on Internet Security and Acceleration Server
> http://support.microsoft.com/kb/301471/en-us
>
> How to delete the Web cache in Internet Security and Acceleration (ISA) Server 2006 or in ISA Server 2004
> http://support.microsoft.com/kb/838248/en-us
>
> Hope this helps.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
>
> .
>
From: "Robbin Meng [MSFT]" on 17 Jun 2010 04:47

Hi David,

Thanks for your prompt reponse.

Since you can ping the "schydraulic.com" and we got the same error using http://ip address, it should not be a DNS resolution or website blocking issue, but more likely a Network connection time-
out issue.

Cause of "10060 - Connection timeout":
========================================
This behavior may occur when the Web Proxy service connection settings do not allow enough time to receive a response from the destination Web site before the service closes the connection.

By default, the Web Proxy service waits for 60 seconds on initial connection attempts to a Web site and all later "GET" requests for a response from the server, and it waits 120 seconds before it
times out idle socket connections.


Suggestions:
========================================
To resolve this issue, follow these steps:

Step 1: Troubleshoot the Web Proxy Connection
Determine if this issue occurs only when the Web Proxy service is used. To do this, install the Winsock Proxy Client on the client computer, disable the Web Proxy settings (under Local Area Network
[LAN] settings on the Connections tab of the Internet Options dialog box), and then try to go to the Web site where you experience the problem. If you can reach the site successfully, the problem is
with the Web Proxy timeout settings. If so, go to the next step.


Step 2: Increase the Web Proxy Timeout Settings
To increase the amount of time that the Web Proxy service waits before it closes idle sessions, follow these steps:

1.
Click Start , click Run , type regedit in the Open box, and then click OK .
2. Navigate to the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters
3. In the right pane of Registry Editor, right-click RequestTimeoutSecs , and then click Modify .
4. Click Decimal , and then type the number of seconds that you want the Web Proxy service to wait for a response before it returns an error message. A recommended value for this setting is
180 or more.
5. Click OK , and then restart the World Wide Web Publishing service. To restart this service:
a. Click Start , click Run , type cmd in the Open box, and then click OK .
b. Type net stop iisadmin /y , and then press ENTER.
c. When the service has stopped successfully, type net start iisadmin /y , and then press ENTER.

Note You may have to restart additional dependent services that were stopped together with the IIS Admin Service.

6. Test the new settings from a client computer that is configured to use the Web Proxy service: try to go to the Web site where you experienced the problem. If the issue is not resolved, go to the
next step.
7. If you still experience the timeout problems, start Registry Editor (if it is not already started), and then navigate to the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters
8. In the right pane of Registry Editor, right-click SocketIoTimeoutSecs , and then click Modify .
9. Click Decimal , and then type a value of 300 (or more) in the Value data box.

Note This is the time in seconds that the Web Proxy service will wait before ending idle socket connections.
10. Restart the World Wide Web Publishing service.
11. Test the new settings from a client computer that is configured to use the Web Proxy service: try to go to the Web site where you experienced the problem. If the issue is not resolved, go to the
next step.
12. Add the TcpMaxDataRetransmissions value to the Windows registry. For additional information about how to add and configure this value, click the following article number to view the article
in the Microsoft Knowledge Base:
KB191143 10060 Connection Timed Out Error with Proxy Server on Slow Link



Please take your time to have a try. Also, if you have any questions or concerns, please do not hesitate to let me know.



Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================



From: mcseman on 17 Jun 2010 10:19
Hi Robin

Thanks again for your reply. I will follow your suggestions and report back.

Regards

David

""Robbin Meng [MSFT]"" wrote:

>
> Hi David,
>
> Thanks for your prompt reponse.
>
> Since you can ping the "schydraulic.com" and we got the same error using http://ip address, it should not be a DNS resolution or website blocking issue, but more likely a Network connection time-
> out issue.
>
> Cause of "10060 - Connection timeout":
> ========================================
> This behavior may occur when the Web Proxy service connection settings do not allow enough time to receive a response from the destination Web site before the service closes the connection.
>
> By default, the Web Proxy service waits for 60 seconds on initial connection attempts to a Web site and all later "GET" requests for a response from the server, and it waits 120 seconds before it
> times out idle socket connections.
>
>
> Suggestions:
> ========================================
> To resolve this issue, follow these steps:
>
> Step 1: Troubleshoot the Web Proxy Connection
> Determine if this issue occurs only when the Web Proxy service is used. To do this, install the Winsock Proxy Client on the client computer, disable the Web Proxy settings (under Local Area Network
> [LAN] settings on the Connections tab of the Internet Options dialog box), and then try to go to the Web site where you experience the problem. If you can reach the site successfully, the problem is
> with the Web Proxy timeout settings. If so, go to the next step.
>
>
> Step 2: Increase the Web Proxy Timeout Settings
> To increase the amount of time that the Web Proxy service waits before it closes idle sessions, follow these steps:
>
> 1.
> Click Start , click Run , type regedit in the Open box, and then click OK .
> 2. Navigate to the following registry subkey:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters
> 3. In the right pane of Registry Editor, right-click RequestTimeoutSecs , and then click Modify .
> 4. Click Decimal , and then type the number of seconds that you want the Web Proxy service to wait for a response before it returns an error message. A recommended value for this setting is
> 180 or more.
> 5. Click OK , and then restart the World Wide Web Publishing service. To restart this service:
> a. Click Start , click Run , type cmd in the Open box, and then click OK .
> b. Type net stop iisadmin /y , and then press ENTER.
> c. When the service has stopped successfully, type net start iisadmin /y , and then press ENTER.
>
> Note You may have to restart additional dependent services that were stopped together with the IIS Admin Service.
>
> 6. Test the new settings from a client computer that is configured to use the Web Proxy service: try to go to the Web site where you experienced the problem. If the issue is not resolved, go to the
> next step.
> 7. If you still experience the timeout problems, start Registry Editor (if it is not already started), and then navigate to the following registry subkey:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters
> 8. In the right pane of Registry Editor, right-click SocketIoTimeoutSecs , and then click Modify .
> 9. Click Decimal , and then type a value of 300 (or more) in the Value data box.
>
> Note This is the time in seconds that the Web Proxy service will wait before ending idle socket connections.
> 10. Restart the World Wide Web Publishing service.
> 11. Test the new settings from a client computer that is configured to use the Web Proxy service: try to go to the Web site where you experienced the problem. If the issue is not resolved, go to the
> next step.
> 12. Add the TcpMaxDataRetransmissions value to the Windows registry. For additional information about how to add and configure this value, click the following article number to view the article
> in the Microsoft Knowledge Base:
> KB191143 10060 Connection Timed Out Error with Proxy Server on Slow Link

>
>
> Please take your time to have a try. Also, if you have any questions or concerns, please do not hesitate to let me know.
>
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
> ==================================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ==================================================================
>
>
>
> .
>
 |  Next  |  Last
Pages: 1 2
Prev: CompanyWeb Broken
Next: Logon credential request when using website blacklists?