Installing Cisco VPN Client on Windows Server 2003
October 7th, 2004
I just installed Win2k3 server on my laptop – everything work just perfect except one thing. Cisco’s VPN client software won’t even install on the machine. It fails saying something about Virtual Adapter couldn’t install or something. Extensive searches of the internet turn up nothing. A visit to the Cisco site reveals that Windows 2003 isn’t supported! How can a company as big as Cisco not support Windows 2003!? Are they making the totally incorrect assumption that people won’t want to use VPN with Windows 2003? They can’t be that dense.
Maybe they just assume that since Windows 2003 has VPN built in I’ll just use that instead of their product all together?
Hi
I have version 4.0.5(A) installed on a w2k3 server – try the exe installer instead of the msi-package.
/Morten
I am trying 4.0.5(B) .. let me see if A works.
I have 4.0.5(C) running on my Win2k3 laptop. The only problem that I have is that if you are trying to use split-tunnel. The add route statment that the VPN client does to the OS does not work. I have not been able to get it to work. Any ideas?
We just discovered this issue today! If you figure anything out please post it back. Cisco’s response was they do not support the client on Windows Server versions. ???
Good News! We found a solution! I have access to both the 3.x and 4.x lines of VPN clients.
The 3.6.6 version of the client seems to work OK with the split DNS setup.
We also have the session initiating with the system startup..not with ctrl-alt-del. I found that the csgina.dll is different between versions and some work for that and some do not…but all versions seem to interoperate with the different client versions.
Notes: We do get a gina error the first time we install a new client version…a reboot fixes that error.
With the 3.6.6 version W2K03 reports it disabled a driver to prevent problems..the client still seems to work OK.
Hope that helps..
I have v. 3.6.3 installed on my Win 2003 server client. The VPN seems to work fine, however when I try to add a web service through my Visual Studio 2003 IDE (client), I can see the web service but cannot actually add a reference to it. I get the following error:
“Invalid URI: The hostname could not be parsed.”
The URL I am using is:
“http://xxx.xxx.xxx.xxx/Common/CustomTags/1800_WS/WSUpdateCallInfo.cfc?wsdl“
Apparently the vsdatant.sys driver being disabled is creating an issue…
how can i get 4.0.5(c) to install on Windows Server 2003 EE?
i get the GetINFClass error
to add to the complexity, the 2003 installation is actually a virtual server, although I don’t think that makes much difference.
i’ve tried both the .exe and the .msi, and have made sure that the server is in ‘install’ mode, not execute.
any help / advise gratefully accepted !!
cheers, kieran
Kieran,
Being a Virtual Server dose make a def. you need to be on the box or using something like VNC to remote to the box. RDP is a good idea but dose not work very well as a system admin tool if you are going to be doing all you install/uninstall and services edit from it.
Also do not use the MSI packed install use the .exe install.
Hi there,
have the same problem with Cisco VPN client under Win 2k3 – client gets connected, but I dont have access/pings to remote network. I agree with above mentioned reason, that cisco client is unable to ADD ROUTE to the remote network. I have found a way how to beat it, but this is not the final solution – after cisco gets connected, add remote server IP as a default gateway. It enables your access to remote network, but you can’t use it for pre-logon connecting to domain (and that is what I need). Any ideas?
Jez – May I request you to please post the URL for downloading the Cisco VPN Client 4.0.5(A) NON-msi install package – Thanks for your help
any further on the add route problem would be appreciated fillchoo@hotmail.com
here is my work around though… create a batch file that contains one command line stating “route add -p x.x.x.x mask y.y.y.y z.z.z.z”
x’s are the new route address,
y’s are the subnet mask,
z’s are the gateway address.
This will create a persistant route.
If anyone has a more permanent solution it would be much appreciated.
any further on the add route problem would be appreciated fillchoo@hotmail.com
here is my work around though… create a batch file that contains one command line stating “route add -p x.x.x.x mask y.y.y.y z.z.z.z”
x’s are the new route address,
y’s are the subnet mask,
z’s are the gateway address.
This will create a persistant route.
If anyone has a more permanent solution it would be much appreciated.
let me know , how u got it. Cisco vpn client 3.6.6. on windows 2003 … U Geek…
Srinivasa dot vissa at gmail dot com
ingresar a directorio de configuracion de network
[root@gateway/]# cd /etc/sysconfig/network-scripts/
crear archivo
[root@gateway/]# vi route-eth0
ADDRESS0=192.168.1.10
NETMASK0=255.255.255.255
GATEWAY0=192.168.1.2 <======= next-hop
subir la ruta
./ifup-route eth0