This article applies to:
Symptoms:
- Performance slowed
- Debugging log output will show name resolution taking 4.5 seconds per request
Causes:
WebMarshal attempts to resolve the computer names of client computers. Resolving the computer names helps to identify the computers in the console and reports.
The processing node server attempts to resolve the computer name using WINS and direct RPC connections. Where access to these methods is denied, browsing is delayed until the attempts time out. User experience can be noticeably affected.
Resolution:
To resolve this issue, upgrade to the latest version of WebMarshal.
This issue was addressed in version 6.1.1 with improved caching of lookups.
You can also disable the resolution as described below.
Workaround:
In WebMarshal 6.0.3 and above, you can stop the attempts to resolve computer names. If you have more than one processing server, you must make the changes on each server.
- In version 6.5.5 and above, use the WebMarshal Server Tool > Advanced tab, and select No Reverse Lookup.
- In version 6.0.3 and above, you can add an entry in the WebMarshal Proxy Configuration file (WMProxy.config.xml) as follows:
<WebMarshal>
<Proxy>
<Config>
<ProxySettings noReverseLookup="true" />
</Config>
</Proxy>
</WebMarshal>
To apply the change, restart the Proxy service. If you use the Server Tool, you will be prompted.
Notes:
- For general information about editing XML settings files, see article Q12705.
- The file WMProxy.config.xml is located on the processing server. If you have more than one processing server, you must make the changes on each server.
- Back up configuration before making changes.
- The file WMProxy.config.xml normally contains additional settings. The ProxySettings node can have multiple attributes. This node should only occur once.
- Only add (or remove) the specific attribute noReverseLookup.
- Previously this issue was stated to apply in DMZ situations with IP authentication. However it is now known to occur more widely.