VPNclient on MacOSX: Could not attach to driver. Is kernel module loaded?

[clwacker]

After installing the VPN client 3.6.2 (same also for 3.6.1) on MacOS X 10.2.1, I try to start the VPN connection and I receive the message

"vpnclient: Command not found."

/usr/local/bin is not in the path(?), so I start the VPN with

/usr/local/bin/vpnclient connect profile-name and I get a

"Could not attach to driver. Is kernel module loaded?"

Any idea why this happen?

If I start the VPN using the graphic freeware VPNConnect it works !

Thanks, Claude

[afakhan]

Hi,

Its a known issue, just a path conflict.

You can go to that folder and execute it, PATH information was not added in the system.

Thanks,

Afaq

[clwacker]

Ok thanks.

But when I execute vpnclient from the /usr/local/bin folder I receive the following error:

"Could not attach to driver. Is kernel module loaded?"

vpnclient could not finish the connection and the VPN doesn't work.

Any further idea?

Claude

[clwacker]

Found why it didn't work.

It seem's that starting with MacOS X 10.2 the path to /usr/local/bin is no more present. Type echo $PATH to check that. You have to edit /etc/csh.login and add /usr/local/bin at the end of the existing setenv PATH to add the path for all users. After that you will be able to start vpnclient without giving the full path.

The message "Could not attach to driver. Is kernel module loaded?" is then shown if ...you don't have any connection to outside (no modem, LAN or WLAN) active...