Which ports do I need to open to allow PortsLock to work?
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 PortsLock 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 PortsLock will work, too.
• 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 PortsLock 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 PortsLock will work, too. You can find more information in the Microsoft’s Knowledge Base Q: I am receiving the error 1722 (“The RPC Server is unavailable”) whenever I try to connect to a computer. A: The error 1722 means that PortsLock Manager cannot access PortsLock 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
