X-Win32 Knowledge Base   >   F-Secure sessions fail to start: CMD file is NULL

Search


About StarNet

StarNet Communications has been a leading developer of X Windows solutions since 1989. After establishing X-Win32 as the de facto standard in the higher education market during the early to mid-1990s -- 150 unlimited Campus Site Licenses worldwide -- X-Win32 has become of one the top three PC X servers in the government and commercial sectors as well.

Unlike its major rivals, Exceed (Hummingbird) and Reflection-X (WRQ/Attachmate), X-Win32 offers a highly focused PC X server that offers superior performance and productivity features, stability, ease of use and low cost (40% or better in most cases).

StarNet also delivers unequaled customer support. Our state-of-the-art engineering infrastructure allows us to fix problems and make a new release available quickly (overnight in many cases). As our testimonials page shows, StarNet customers consistently rate their X-Win32 experience as the best in the industry.




F-Secure sessions fail to start: CMD file is NULL

X-Win32 7.1 and earlier allow integration with F-Secure versions 5.2 and 5.1, allowing you to create a session in X-Win32 that will use F-Secure SSH to handle the SSH connection and X11 Forwarding. However, this integration does not support newer versions of F-Secure (such as version 5.3) and X-Win32 8 and later no longer support this integration. If you upgrade to X-Win32 8, or later, then your F-Secure sessions in X-Win32 can be converted to StarNetSSH sessions using the Session Migration Wizard in X-Config.

This error CMD file is NULL or Command file is NULL typically indicates that F-Secure 5.3 or later is installed.

If you need to continue using the F-Secure integration and you currently have F-Secure 5.3 or later installed, then you will need to contact F-Secure to obtain version 5.2.

Category:Errors
Category:Sessions -> F-Secure