I have a Windows XP laptop and can run the Cloverleaf 5.6 and 6.0 clients in the office connected directly to our network, and at home when connected remotely using Cisco Anyconnect.
My new laptop is Windows 7. I can run the 5.6 and 6.0 clients in the office but only the 5.6 client works remotely.
The 6.0 client opens the GUI but hangs if you select Network Monitor or Network Configurator.
I saw a similar problem with the 5.8 client over Cisco VPN as well. This was I when using the tools that return stdout (e.g., testing tool, remote run).
If you use netstat or a near “real-time” viewer (Microsoft’s/Sysinternals TCPView is nice and free), you’ll see that the GUI will open multiple additonal (non-specific) ports, the return conversations for which are possibly ephemeral and being blocked by firewall rules on the VPN/Cisco connection. This probably is allowed when you’re on your office internal network.
In our case, we have an AIX HA environment, and those additional connections to the GUI aren’t coming back to the client with the same IP as the IP solicited by the client. In our case, the return connection is coming from the host cluster node’s IP, which is on a different IP range than the VIO server actually hosting Cloverleaf). So, a firewall would block what is essentially an unsolicited inbound connection.
I’d be curious to know if you are able to resolve it. I never resolved this issue. Instead, I switched to using RDP to an internal workstation, because this is allowed in our environment.
Not resolved yet. TCPView is certainly a lot more useful than netstat. I’ve noticed that on a VPN connection, when opening Net Monitor that all the same ports connect as for a local connectection but one of them goes into TIME_WAIT after being ESTABLISHED. Unfortunately that doesn’t tell me a lot.
It’s odd that my XP laptop behaves correctly when connected remotely. I’ll check it with TCPView.
It occurred to me after I posted my first reply that your Windows 7 device probably has different settings for your various “known” networks. At home, on a VPN, there may be a different firewall policy applied than your trusted work network?