RE: Two different vpn clients on XP possible?



Okay-so I think this may not be possible and has something to do with the
fact that both clients want to bind to the port on boot. Does that sound
right to everyone-and if so, one client has to get there first and therefore
the other can't bind to the same port as well.

So is there anyway to make a vpn client bind to the port only when required?


-----Original Message-----
From: Murad Talukdar [mailto:talukdar_m@xxxxxxxxxx]
Sent: Wednesday, November 22, 2006 1:25 PM
To: 'security-basics@xxxxxxxxxxxxxxxxx'
Subject: Two different vpn clients on XP possible?



Hi all,
I'm faced with a dilemma;
We have mobile users who connect to our HQ in the US using Nortel's VPN
client so that they can send audit info. This is used possibly once or twice
a week for period of a few minutes each time.

We would also like to give them VPN access to our LAN here in Aus. However,
we have a watchguard and the two clients are not compatible it seems.

Could I instead use Xp's built in IPsec to tunnel through our WG and keep
the existing Nortel client? Has anyone had success with two different
clients on same box? Reading posts and googling does not fill me with
confidence.
I've thought of VM"s but know that the mobile staff would shoot me if I
suggested this. Some of them still ask where the 'any' key is without a hint
of irony....





---------------------------------------------------------------------------
This list is sponsored by: Norwich University

EARN A MASTER OF SCIENCE IN INFORMATION ASSURANCE - ONLINE
The NSA has designated Norwich University a center of Academic Excellence
in Information Security. Our program offers unparalleled Infosec management
education and the case study affords you unmatched consulting experience.
Using interactive e-Learning technology, you can earn this esteemed degree,
without disrupting your career or home life.

http://www.msia.norwich.edu/secfocus
---------------------------------------------------------------------------

Relevant Pages

  • Re: adding machine to domain with NATed IPs
    ... sounds that the DCs are not reaching the clients ... weight 100, port 389, target srv5.mydomain.local ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding machine to domain with NATed IPs
    ... sounds that the DCs are not reaching the clients ... Type: SRV (Service location) ... weight 100, port 389, target srv5.mydomain.local ...
    (microsoft.public.windows.server.active_directory)
  • Re: DDoS to microsoft sites
    ... The primary difference between the two clients is that the first port scan I ... > - netbios (brute force attack on Administrator account) ... I'm guessing that the SQL server is the infection vector in both these ...
    (Incidents)
  • Re: Help need desperately!
    ... Changing from port 80 is not required. ... Inventory information began flowing properly. ... All of the clients seemed to install with the new ... >> found our problem to be in our TCP port configuration on the Server. ...
    (microsoft.public.sms.inventory)
  • Re: adding machine to domain with NATed IPs
    ... sounds that the DCs are not reaching the clients or vice versa? ... weight 100, port 389, target srv5.mydomain.local ...
    (microsoft.public.windows.server.active_directory)
Quantcast