Nortel TAPI User Manual page 67

Common causes for failure of the second RPC connection include:
• The client machine domain doesn't trust the server user domain. This
common failure occurs when the server is in a resource domain that has a
one-way trust relationship with the user domain.
• the client machine is not correctly configured to validate using domain
accounts
• the client machine is not configured to allow the server user to use network
resources
Where there is a resource domain, the simplest configuration is to place the server
user account into the client user domain, creating just one user domain which is
trusted by both machine domains.
To test whether your the server machine and client machine are correctly
configured for RPCs, perform the following tasks:
1
On the client machine, log in as the client user.
2
In the command window, enter the following command:
NET VIEW \\ServerMachine
If the command succeeds, even if there are no entries in the list, the first RPC
connection can be made.
3 On the server machine, log in as the server user.
4 In the command window, enter the following command:
NET VIEW \\ClientMachine
If the command succeeds, even if there are no entries in the list, the second
RPC connection can be made.
If either of the net view commands fails, you have a security problem that must be
resolved. During validation TCP/IP must be the only protocol installed on the
server machine to ensure that the tests do not use other protocols to succeed
accidentally.
Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0
Chapter 3 Preparing the TAPI environment 67