your Terminal Server know how to route back to the VPN client ? Incorrect default gateway for the VPN tunnel ? Your VPN passing source address or using NAT ?
On Thu, Feb 3, 2011 at 9:52 AM, John Aldrich <[email protected]>wrote: > Yeah... but if the same *exact* account works on the Desktop, but not on > the > laptop, that shouldn't be the issue, should it? > > > > > -----Original Message----- > From: Mayo, Bill [mailto:[email protected]] > Sent: Thursday, February 03, 2011 9:34 AM > To: NT System Admin Issues > Subject: RE: VPN problems > > If the Cisco VPN client connects, but then you can't access anything on > the network, you most likely have some kind of routing problem. The VPN > client has to decide whether to send traffic through the VPN tunnel or > over the local network. This decision is based on the split tunneling > settings (as indicated below) and the available/advertised routes on > both networks. Generally speaking, if the VPN client has an IP address > that is also in the range of a network on the other side (think private > addresses), you can have issues--some of which can be mitigated with the > split tunneling settings. > > Bill Mayo > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
