Microsoft KB Archive/240055

= TableURL Only Shows NetBIOS Names of Proxy Array Members =

Article ID: 240055

Article Last Modified on 4/7/2006

-

APPLIES TO


 * Microsoft Proxy Server 2.0 Standard Edition

-



This article was previously published under Q240055



SYMPTOMS
When you create a proxy array, the TableURL only shows the NetBIOS name of the array members. It is not possible to set it to the Fully Qualified Domain Name (FQDN). This is a problem for downstream Proxy Server computers that are chained to the array and cannot resolve NetBIOS names.

When a downstream Proxy Server computer makes a request to update its cache using active caching, the reference in that server's cache points to a NetBIOS name of an array member. Because this name cannot be resolved, the request fails. The following is an example of the 11001 error message that appears in the Web Proxy log:

xxx.xxx.xxx.xxx, anonymous, -, N, 6/29/99, 10:51:46, 1, -, -, PROXY-SRV1, -, 80, 6900, -, 407, http, tcp, -, http://www.company.com/, -, Upstream, 11001, 2



WORKAROUND
On each downstream Proxy Server computer, configure the LMHOSTS file or WINS so that all of the array members' NetBIOS names can be resolved to an IP address.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Product Name service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

  Date      Time    Version      Size    File name     Platform -  08/13/99  17:30   2.0.390.16   190,224 W3proxy.dll   x86 08/13/99 17:29   2.0.390.16   304,400 W3proxy.dll   Alpha

To install this hotfix, please follow these steps on the upstream proxy array and propagate the change to the downstream proxies.  Go in to the array configuration UI, and record the existing array Time to Live (TTL) value, which is most likely 50 minutes. Change the number to a small value, such as one minute. Wait 50 minutes for all of the downstream proxies to download the new TTL information. Break the array. Stop the Proxy services on all the array members. Update the W3Proxy.dll file on all of the array members. Add the following new registry key to each of the array members: <ol style="list-style-type: lower-alpha;"> Start Registry Editor (Regedt32.exe).</li> Locate the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3proxy\parameters

NOTE: The above registry key is one path; it has been wrapped for readability.

</li>  On the Edit menu, click Add Value, and then add the following registry value: <pre class="fixed_text">  Value Name: ArrayHostSuffix Set this key value equal to the string you need to append to your computer name to get a valid DNS host name. For example, .dns.microsoft.com (note the dot at the beginning of the string). The same ArrayHostSuffix registry key must be set on all members of the array. If the registry key is not present, the hotfix behaves exactly as before. </li> Quit Registry Editor.</li></ol> </li> Restart the Proxy service on all members of the array.</li> Recreate the array.</li> Restore the original TTL value.</li> Within one minute, all of the downstream proxies should have the new information.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in Proxy Server version 2.0.

This hotfix is a post-Microsoft Proxy 2.0 SP1 hotfix.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB240055

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.