|
|
|
|
|
|
|
FAQ: Why does eXchange WALL fail to connect when running as a service on the same machine as Microsoft Proxy?
Please perform the following steps to ensure Microsoft Proxy is properly installed and configured.
Step 1: Is proxy client installed on computer?
Even though proxy server is installed, you still need the proxy client installed on the same computer to trigger outbound connections.
Step 2: Does the account running the eXchange WALL service have proxy server rights?
By default, the eXchange WALL service runs under the System Account. This account may not have sufficient rights configured under
proxy server. Using the Windows Services Manager, change the logon account assigned to eXchange WALL to an account with
full proxy server rights.
Step 3: Ensure eXchange WALL starts after proxy server service?
When eXchange WALL is started by the Service Control Manager the MS Proxy service may not be started or initialized.
The eXchange WALL service loads the TCP/IP Winsock Proxy stack and initializes it but the underlying network information
has not been initialized by the Proxy server. This problem only seems to occur if the eXchange WALL service is installed
on the same PC as the MS Proxy server.
To correct this situation you need to add a REG_MULTI_SZ registry parameter to the eXchange WALL service to force a dependency on the MS Proxy server.
Start the Registry Editor. From the Windows Start Menu select Run and enter: regedit
Select:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\eXchange WALL [x x.version]
From the main menu select:
Edit  New String Value
Name the parameter DependOnService and press the Enter key.
Double-click the parameter and enter a value of WSPSrv
Press the OK button.
Reboot the computer.
|
|
|
|
|
| © 2003 Kinesphere Corporation. All rights reserved. |
|
