At certain times, connections through Surrogate Socket will be extremely sluggish or will not connect at all. Stopping and restarting Surrogate Socket will occasionally resolve the problem for a short period of time.
More Information:
We have identified a problem with a routine which performs DNS lookups within Surrogate Socket. Certain combinations of system date and time will cause the DNS lookups to fail. Once this occurs, Surrogate Socket then continuously executes a routine which consumes CPU resources and causes connections and data transfer to become extremely sluggish.
Resolution:
This problem will be fixed in an upcoming release of Surrogate Socket. Until that time, the following work-around will resolve the issue:
Click on Start and then Run
Type Regedt32 hit enter.
Then go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ SurrogateSocket\Parameters
Then click on edit at the top of the screen then click on add value.
Value Name: AllowAltDNS
Type: REG_SZ
Value: 1
Then exit out of the registry. Go back to the Surrogate Socket service control.
Stop and restart Surrogate Socket.
After this is done, you should see an entry similar to the following:
9/20/00,11:17:04,AllowAltDNS=Yes in the Surrogate Socket log.
|
