Issue: Failure to login. Reason: RPC Server Unavailable. The DNAdrvr32 driver cannot connect to the client station. The driver is failing to connect to the client on port 135.
Solution: The most common cause of RPC failure log in is due to the firewall blocking the traffic on port 135.
1. To test this, try to connect to the client from the machine running the DNADrvr32 driver using a Hyper Terminal connection on port 135.
2. Turn off the firewall or configure it to allow connections on port 135 between the client and the machine configured to run the driver.
a. To turn OFF the Firewall: Open the Control Panel, select the Windows Firewall icon and configure the set the firewall to OFF. If another firewall application is used, turn it OFF. OR
b. If the firewall is enabled it will need to be configured to allow communication to the server on port 135. On the server, create Exceptions for the NPowerDNA.exe, NPowerIDSL.exe and Dnadrvr32.exe executables. For TCP connections, exceptions will also need to be created for ports 135, 1087, 1088 and 1089. The number of DCOM ports that need to be opened is dependent on the number of clients that will be connecting to the server. Open Options recommends configuring DCOM to use a 500 port range on the Server and each client PC.
3. The DNAFusion client(s) will need an exception created for port 135 for TCP connections and an exception created for the NPowerDNA.exe executable. To open a port on the Windows Firewall: Open the Control Panel, select the Windows Firewall icon, select the Advanced Setting option and create a New Inbound Rule for port 135 as well as an exception for the NPowerDNA.exe. If another firewall application is used, configure it to allow communication on port 135 along an exception for the NPowerDNA.exe. The following command line can also be run on the client machine: netsh advfirewall firewall add Rule name=”Fusion DCOM” dir=in action=allow protocol=TCP localport = 5000-5150