Re: 6.5 server heartbeat protocol? I am a bit puzzled by the heartbeat process and the authentication by IAS to allow clients to switch over to the connected Enterprise policy. We currently have a configuration where UDP 6054 is blocked by our VPN firewall but we still have the 'majority' (!!!) of clients quite happily switching over to connected policy. Even those that remain on disconnected policy are quite happily heartbeating to the server and the Enterprise policy update time is incrementing on the client even though not active. We have had zspupd set as the heartbeat protocol since the beginning. Is this the protocol block at fault or is the VPN session-ID fault that was unearthed in HFA05 still present in HFA06 (v199) ?? Unc |