Re: Remote Admin on a XP Pro client behind a NAT

I don't know if Cisco offers trial versions or not. You should check the options for the VPN client you're currently using. I would expect almost any good VPN client to allow for integration with the logon sequence.

--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"Wells" <Wells@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:DB81FF27-8A6E-4030-9B2D-E894C9AF3090@xxxxxxxxxxxxxxxx
That sounds perfect (well, actually perfect would be if windows xp already
did this). Do you know if Cisco has any trial software programs so that I
can test it to make sure it works? I've looked all over their site and I
couldn't find anything...

Thanks,
Wells

"Doug Knox MS-MVP" wrote:

The Cisco VPN client we use has an option to remain active, even if the user logs off. It will actually come up as part of the logon process so the user can authenticate against the VPN server, then logon via the domain. Log off and the VPN client is still running in the background and the machine can be administered remotely.

--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"Wells" <Wells@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:982E6FC1-AA49-426E-B951-4A98F5727CF4@xxxxxxxxxxxxxxxx
I may be going about this the wrong way but currently my company has many
laptops out all over the country that connect to the internet through various
ISPs, most of which use NAT. I need to be able to manage these machines and
my prefered way to do this is to have these machines create a VPN connection
to the server in our central office (it has a static IP) and then to use
Remote Desktop to do what ever I need to do on the remote PC. The problem
here is that as soon as I login to the remote PC it logs the current user on
that PC out, which causes the VPN connection to die.

How do I get around this? Is there any way to keep the VPN connection open?

Thanks,
Wells

.

Relevant Pages

  • Re: Site-to-Site VPN
    ... NetVanta router, cant split them up due to our need for the lines for ... I have static at the main office, not sure about the remote. ... VPN between ASA and NetVanta Situation: The client creates a site to site VPN between Cisco ASA5510 and NetVanta 2054, ...
    (microsoft.public.windows.server.networking)
  • Re: Cant start DHCP Service - fixed
    ... Cisco 3000 VPN client...at least I think so...my network ... 3000 VPN client installs components of ZoneLabs' ... ZoneAlarm firewall. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Split Tunnelling
    ... problem to access the Internet or access remote resources. ... establishing a VPN connection, the VPN client can’t access other remote ... The remote default route points to the new connection, which ensures that any packets that are not addressed to the local LAN segment are sent to the remote network. ... the VPN client will not be able to access the Internet. ...
    (microsoft.public.windows.server.networking)
  • Re: [opensuse] Connection Question
    ... with the cisco vpn because it takes over your routing and hostname lookups. ... Now I can connect to my work network from any machine behind my router, ... I run the VPN client from the ...
    (SuSE)
  • Re: VPN/Remote Desktop/Internet problem
    ... If the remote clients are connecting to the PIX using the Cisco VPN ... The remotes may be authenticating their VPN connection against AD though. ...
    (microsoft.public.windows.server.networking)