Hello Edwin I would agree with some of what you say. Using an Sun box instead of an NT box tends to improve any application. As for the timeouts, this always points to an SDI machine without enough CPU and RAM resources. Also, Navis Radius 3.1 has many performance improvements over Navis Radius 3.0 Cheers James ----- Original Message ----- From: <Edwin_Everett at cargill.com> To: <ascend-users at bungi.com>; <jcdutton at lucent.com>; <thorsten at eckey.do.uunet.de> Cc: <Matt_Brunsvold at cargill.com>; <Jeff_Owens at cargill.com> Sent: Friday, November 03, 2000 4:53 PM Subject: RE: Re: (ASCEND) Upgrading NavisRadius v1.3 to v3.1 with SecurID I would recommend against the use of Securid's Radius proxy method as we have taken that tack before and are trying to dig ourselves out as a result. Use the Auth Securid Plugin(if you can) we have seen many timeouts when proxying to SDI radius. We had to try it because our radius machines were NT and NT version of Radius does not support the Securid Plugin yet.(ever?) Were currently working on implementing Solaris to enable this direct Radius to ACE authentication, but its been a long road.... I agree. 3.1 is very flexible. If you want to team up as a Navis Radius using SDI, we can take it offline from the usergroup,let me know. My group has gained a bit of experience with the newer radius atmosphere... Edwin_Everett at cargill.com Cargill, Inc. Minneapolis, MN ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>