1/3
Remote App Server showing offline in VDC - troubleshooting
  

George Fady Lv2  Posted 2026-Oct-15 17:21

Hello Sangfor Community,
I am George Fady, Technical Support Engineer, and I would like to share a practical troubleshooting case related to a Remote App Server showing Offline in VDC in Sangfor VDI.
Problem Description
After completing the Remote App Server installation, the server appeared as Offline in VDC (Assets > Remote App Servers):
Product: Sangfor HCI 6.3.1 with VDI (VDC 5.9.6)
Server status: Offline
Agent Protocol, Agent Version, Cluster, Run Location: all blank (“-”)
On the Remote App Server itself, the Agent Console showed “Service is running...” with the correct VDC IP and Agent Port 7170, so the agent looked healthy locally.
Root Cause
The blank fields mean VDC had never received a successful registration from the agent. The service was running, but the connection between VDC and the server was never established because of:

  • TCP port 7170 (VDC to Remote App Server, used for agent status monitoring and registration) was blocked by the firewall.

  • The IP/port in the VDC server entry did not match the Agent Console configuration.

Resolution Steps

  • On the Remote App Server, open the Agent Console and note the VDC IP and Agent Port (default 7170).

  • From the VDC, test TCP 7170 to the Remote App Server (telnet or Test-NetConnection).

  • Allow inbound TCP 7170 on the Windows Firewall of the Remote App Server and on any network firewall in the path.

  • Navigate to: Assets → Remote App Servers and make sure the server IP and port match the Agent Console.

  • Select the server and click More → Update Agent to force VDC to retry the connection.

  • Refresh the page and confirm the server status changes to Online with the agent fields populated.

Key Takeaway
If the Agent Console says “Service is running” but VDC shows Offline with blank fields, do not reinstall the agent first. Check the network path and configuration match first:
Port 7170 reachability → Firewall rules → IP/port match in VDC → Update Agent
Also note:

  • The “IOM Not deployed yet” label in the VDC header is unrelated to this issue.

  • Client-side ports are separate: 7171 (SRAP2.0), 7172 (SRAP1.0), 8801-9001 (protocol V2.0).

  • On newer builds the logs are under C:\sflogs (rapp, upm, xdesk). “Sangfor VMSTool” is a VM component, not the Remote App agent.

I hope this troubleshooting case helps other engineers working with Sangfor VDI.
Feel free to share your experience with Remote App Server registration issues in the comments.
#Sangfor #SangforHCI #HCI #VDI #VDC #RemoteApp #Firewall #TechnicalSupport #Troubleshooting
Humayun Ahmed Lv4  Posted 2026-Oct-15 17:46
  
Thanks to share!