Wingate mishandles hanging up modem with 5.1.0

[saubrey]

I upgraded to 5.1.0 three days ago, and now Wingate 5.1.0 either hangs up the modem too soon (when activity is still occurring) or Wingate doesn't hang up the modem when no activity is taking place. 5.0.7 did not have this problem. How do I correct this? I've set Wingate's modem idle time out to 10 minutes. Some months ago I tweaked some Wingate registry setting (based on advice from deerfield tech support) that controlled Wingate's determination of what is "idle", but I've forgotten what that was. I use ENS with transparent redirection through WWW proxy. Wingate seems to hang up when activity is still taking place when http activity is not passing thru the www proxy (Wingate's activity pane show a NAT connection, not a http connection). Other than this hanging up the modem issue, 5.1.0 seems to have fixed all the problems with 5.0.8 throught 5.0.10 especially with the phantom adapter issue. Thanks, Steve