While I understand the intent of the accepted answer, the reality is that Windows server OS is used by many as its more closely mimics deployment environments. For me, it provides many more tools OOTB than the workstation OS...so I successfully installed (hacked) Cisco VPN on windows 2003 (sp1). Note that I only have a single nic and rather vanilla server I tested with but it does work...but like everything else, there are so many variables that this solution may not work for you. (note too that this solution may open up a security hole on the server...but then again, Windows is full of them so just keep a watchful eye on your firewall logs...)
VPN Software version is 4.6.02
Background:
The default configuration of the server resulted in an error during the installation of the Cisco VPN Software, but not a fatal one so it basically performed a partial install. I then rebooted when prompted. On startup, the server reported a service failure. Upon inspection of the event logs (Service) it was noted that the Cisco’s IPSec driver could not run due to a DNE failure. DNE (Deterministic Network Enhancer) is a protocol that Cisco’s VPN service requires.
So, I found the DNE install, drivers, etc under %system/Program Files/Common Files/DNE. I attempted to install those manually by installing the .inf files I found. On reboot I receive additional failures; the service failure as described above, and (Application) event errors indicating that DCOM security for a CLSID object was insufficient for a provider (a registry provider id) was preventing an application for running. Upon further inspection of the registry (the CLSID was provided in the error) I found that the application was netman…, and the provider id was %system/Documents and Settings/NetworkServices…h
The Fix:
I opened the Component Services module on the server and drilled into the DCOM service entries. I opened the properties on the netman component, and added the “NETWORK SERVICES” AND “NETWORK” security objects the security for netman, and allowed local access to both.
I then ran the Cisco installation process again and, as expected, it complained that the software was already installed so I let it remove and restart the system.
I then re-ran the Cisco installation and viola, no errors during the install. The install rebooted the system as expected and upon login, I successfully vpn’d.
In Summary:
Your installation experience may be completely different than mine…so, print this on soft paper and use it for what it is worth :)
Main Topics
Browse All Topics
by: lrmoorePosted on 2005-01-31 at 10:31:15ID: 13185198
The Cisco VPN client is not supported on Windows 2003 server. Period.
The 2003 server is simply not designed or meant to be anyones personal workstation. The VPN client is designed for mobile/remote users.
"VPN Client Not Supported on Windows NT Servers
The VPN Client is not supported on any Windows NT server version (including Windows 2000 and Windows XP/.NET/2003 servers). Only Windows NT 4.0 Workstation and Windows 2000 Workstation are the supported platforms. "
http://www.cisco.com/en/US