IT-DISCUSS Archives

January 2006

IT-DISCUSS@LIST.UVM.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Technology Discussion at UVM <[log in to unmask]>
Date:
Fri, 20 Jan 2006 17:07:42 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (57 lines)
Some bright sunny day, the Cisco VPN will be gone, and the world will live in 
the peace and prosperity of standards-based, reliable software.

Quoting Philip Plourde <[log in to unmask]>:

> The only additional thing we've seen from Cisco was the recommendation 
> to disable all network adapters before doing a clean install, then turn 
> them back on after.  Don't turn on the Cisco virtual adapter though, it 
> does that for you when needed.
> 
> Phil
> 
> Victor Rossi wrote:
> > That was the first thing I tried.
> >
> >> Victor,
> >>
> >> I think the VPN client may be confused and/or corrupted.
> >> Try uninstalling and reinstalling the client; that often fixes this 
> >> kind of problem.
> >>
> >> Lynne
> >>
> >> Victor Rossi wrote:
> >>
> >>> Scott Dellinger wrote:
> >>>
> >>>> On Jan 20, 2006, at 11:26 AM, Victor Rossi wrote:
> >>>>
> >>>>> Would anyone have insight into the error message
> >>>>>
> >>>>> 'VPN cannot connect to the underlying subsystem'
> >>>>>
> >>>>> This machine has McCaffe security systems running.  The Windows  
> >>>>> firewall shows the required port exceptions activated.   Wireless  
> >>>>> connectivity is good.   I have installed the latest UVM vpn 
> >>>>> client  and it is enabled.  I can do some configuration steps 
> >>>>> through the  Network applet, but cannot get the client to boot up.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> If the client is saying that and not starting up, I think the  
> >>>> "underlying subsystem" it's referring to is the VPN client's 
> >>>> network  driver.  You said "connectivity is good" -- I'm assuming 
> >>>> you mean  wireless signal -- but do you actually have an IP 
> >>>> address?  The  client won't start up if you don't already have one.
> >>>>
> >>>>
> >>> yep - i do have an ip address via wireless.  vpn service is running 
> >>> in services.  if mcaffe asks, i grant access to anything vpn.  mucho 
> >>> confuso..   how does one test access from the vpn client to the vpn 
> >>> network driver?  perhaps it is some kind of block by mcaffe at the 
> >>> transport layer?
> >>
> 

ATOM RSS1 RSS2