irfanhussain Since you want the user to get a OWA 2003 link, this is all web based. The user does not need to get an IP address or built an actual IPSec tunnel from the end-point to the SSL VPN. What you need to do is create a Web Resource Policy, which is basically a web link/bookmark to the OWA URL. Associate that web link/bookmark with the role created for the user. The user will go to https://100.100.100.1, login and providing authentication is successful and user is mapped to the correct role, they will get a portal page on the SSL VPN with at least 1 web link to OWA. The user clicks on OWA and the SSL device acts as a proxy between the OWA server and the user. FYI ... the SA can be configured to provide a number of different type of access -- Terminal Services, Web Resources, Telnet/SSH, Network Connect, SAM. Only Network Connect would provide a full IPSec tunnel and at that point the user will get an IP address that from a configured IP Pool on the SSL VPN. You should take a look at the admin guide for detail info on all these features. In general, I do not enable Network Connect unless it's absolutely necessary. If I can provide the same access using one of the other features, I do that. Network Connect makes the end-point communicate with the internal networks directly (of course youc an setup ACLs on the SA to limit access). Hope that helps. -Mike
... View more