Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Which ports do I need to open on the firewall to allow DeviceLock to work?

DeviceLock firewall ports
0
Posted

Which ports do I need to open on the firewall to allow DeviceLock to work?

0

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/Vista administrative tool (such as Event Viewer, Services, Computer Management, etc.) so, if these tools work then DeviceLock 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 DeviceLock management consoles cannot access DeviceLock Servic

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.