I agree with this try by IP not UNC.
Jon On Thu, Feb 3, 2011 at 10:20 AM, Candee <[email protected]> wrote: > if the Cisco client said you were connected, then you were. > did you try to connect to the remote desktop machine via IP address? > Did you bother trying to ping anything? > What else have you changed on your laptop? > > On Thu, Feb 3, 2011 at 10:13 AM, John Aldrich < > [email protected]> wrote: > >> Well, I can RDP from my wife’s computer back to the servers or my work >> desktop, so yes, they know how to get back through the VPN. Not sure about >> the last question, but either way, as long as it works on my wife’s >> desktop, >> but not on my laptop (when I’m at home OR out on the road) it shouldn’t >> matter, should it? I think everyone keeps overlooking the fact that it >> works >> at home ON MY WIFE’S DESKTOP, but NOT on my company laptop, when at home >> OR >> on the road. I tried it plugged up to an Ethernet jack at a seminar >> Tuesday >> and it did not work. I tried it wirelessly at McDonald's and while I was >> able to get around, surfing the web and even SSH into my linux box at >> home, >> I was not able to RDP while connected to the VPN. I also plugged up to the >> Ethernet at home and tried to VPN and RDP from the same physical network >> as >> my wife's PC, and was unable to connect via RDP. Cisco client *said* I was >> connected, but I was unable to get past the firewall at the office. >> >> >> >> From: Erik Goldoff [mailto:[email protected]] >> Sent: Thursday, February 03, 2011 10:02 AM >> To: NT System Admin Issues >> Subject: Re: VPN problems >> >> 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 >> >> >> ~ 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 >> >> > ~ 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 > ~ 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
