Config - Firewall Ports Configuration

Modified on Wed, 21 May at 3:08 PM


This guide walks you through configuring the necessary firewall and port settings for proper communication between the Softdrive Remote Desktop Client and Server.


1. Overview

Softdrive uses a combination of UDP and TCP ports for secure communication between its client and server applications. Both ends must have appropriate firewall rules to ensure connectivity.


2. Security and Encryption

All traffic is encrypted using secure protocols:

TransportProtocolEncryption MethodCipher
TCPTLSPre-Shared KeyChaCha20-Poly1305
TCPHTTPSCertificate-BasedAES
UDPSRTPPre-Shared KeyAES


3. Server Configuration

Ensure the following firewall rules are applied on the server:

ProtocolDirectionPort RangeDescription
UDPInbound9250–9254Softstream application data (SRTP + AES)
TCPInbound9260Softstream application data (TLS + ChaCha)
TCPInboundEphemeral (OS default)Communications with Softnet (HTTPS)
UDPOutbound58000–59000Sends data to client
Add SoftdriveServer.exe to the Windows Firewall as allowed.


4. Client Configuration

Apply the following firewall rules on the client:

ProtocolDirectionPort RangeDescription
UDPOutbound9250–9254Sends data to server
TCPOutbound9260Softstream application data (TLS + ChaCha)
TCPOutbound443Communications with Softnet (HTTPS)
UDPInbound58000–59000Receives data from server
    Add SoftdriveClient.exe to the Windows Firewall as allowed.


5. Testing Connectivity

After configuring the firewall:

  • Verify that the client can connect to the remote session.

  • Use tools like Test-NetConnection or telnet to validate TCP connectivity.

  • Use packet capture (Wireshark) to verify encrypted traffic over correct ports.


Final Notes

  • Ephemeral ports are assigned dynamically by the OS and must be open for responses.

  • All communication is encrypted for confidentiality and integrity.

  • Always test with the firewall enabled to confirm ports are functioning correctly.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article