|
| How can I configure DeviceLock® to use a fixed TCP port? |
By default, DeviceLock® Service is using dynamic ports for the RPC communication with DeviceLock® management consoles. The ports change every time DeviceLock® Service is started, making it difficult to configure a firewall. To overcome this difficulty, you can instruct DeviceLock® Service to use a fixed port. To do so, open Regedit and set the following entry:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\SmartLine Vision\DeviceLock
Name: ncacn_ip_tcp[port number]
Type: REG_SZ
Value: not used (can be empty)
port number - the fixed TCP port number that you want to use for the communication between DeviceLock® Service and DeviceLock® management consoles.
You should restart DeviceLock® Service for the setting to take effect.
Now, to connect DeviceLock® management consoles to the computer where DeviceLock® Service was configured to use a fixed port, you should specify this port in square brackets next to the computer name, e.g. computer_name[port number].
Please note that when you connect to DeviceLock® Service using a fixed port, the remote install/update function is disabled, i.e. you can’t install or update DeviceLock® Service on remote computers without using dynamic ports. Also, Audit Log Viewer doesn’t work if the 139 TCP port is closed on the firewall. |
| |
| How can I configure DeviceLock® to use a fixed TCP port? |
A: You can instruct DeviceLock® to use a fixed port, making it easier to configure a firewall. If you want to configure the firewall for dynamic ports connection, follow the instructions below.
You need to open 135-139 ports and all ports above 1024 for incoming and outgoing packets:
Port 135 (TCP) - for Remote Procedure Call (RPC) Service
Port 137 (UDP) - for NetBIOS Name Service
Port 138 (UDP) - for NetBIOS Netlogon and Browsing
Port 139 (TCP) - for NetBIOS session (NET USE)
Ports above 1024 (TCP) - for RPC Communication
DeviceLock® works like any other standard Windows NT/2000/XP administrative tool (such as Event Viewer, Services, Computer Management, etc.) so, if these tools work then DeviceLock® will work, too.
|
| I am receiving the error 1722 ("The RPC Server is unavailable") whenever I try to connect to a computer. |
The error 1722 means that DeviceLock® management consoles cannot access DeviceLock® Service on the remote computer. There are several possible reasons:
the remote computer does not exist on the network (the computer's name or IP address is incorrect or this computer was shut down recently but its name still exists in the network browser);
the remote computer is not a Windows NT 4.0/2000/XP computer and DeviceLock® Service cannot be installed on this computer;
the remote computer is behind a firewall that was not configured properly (to configure a firewall, please read this answer);
the remote computer is on another segment of your network that is not accessible from your segment, i.e. the routing was not configured properly and you cannot access that network's segment at all. |
|
What's new in version 6.2
More To Try
|
|
Home
Download
