|
Home > Archive > VPN > November 2004 > Windows 2003 routing and Cisco VPN client...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Windows 2003 routing and Cisco VPN client...
|
|
| Pradeep 2004-11-01, 7:45 am |
| Hi,
I recently switch from using a Linksys router to a Windows 2003 server
configured as a router. Everything seems to be working as expected. I
am also able to use standard Microsoft VPN client to connect to the
outside world.
The only problem that I am running into is that cisco VPN client does
not work. I can connect to the host and register my machine. However,
I cannot ping to any machine on the host system. This setup used to
work flawlessly with the Linksys router.
Does anyone have any idea on what could be going on? I even tried to
turn Internet Connection Firewall (ICF) off on the WAN connection. But
this did not help.
On the Windows 2003 system, all I had to do was to turn on "Allow
Internet Sharing" on the WAN network card. Very simple. I didn't even
have to install "Routing and Remote Access" Windows component. Now I
am wondering if this is the problem.
Thank you in advance for your help.
Pradeep
| |
| Some One 2004-11-13, 12:58 am |
| Link Sys routers and ciso devices work differently.
You have to config the cisco vpn more.
it needs the default gateway.
also needs the ip/subnet masking.
also check if... the router is allowing SNMP requests.
Standard vpn clients have all the PLUGn PLAY features.
wink3 or other windows needs proper configuration
the gateways
default gateways
local routing
local to externalk routing.
IP/subnetcheck
if u cannot ping then it means
either its not configured properly. is SNMP enabled on the cisco vpn client?????? or its not configured.... properly? IP? submask?
or may be... win3k machine has some problem?
or it is not supporting the current scnerio.
Also do some RFTM to check about the working of win3k routing, internetsharing....
and if u have enabled the internetsharing then it means that the local client needs to be configured to use DHCP of win3k machine to pick the ip addresses? then how it cannot ping? then it means its not configured...
if this autopnp dosent works try to solve it manually...
and then u dont have to ... configure is as a router...
WIN3k by defualt does that feature for you...
so....
re check and state the reall network scnerio if nothing goes well..
.............................................................................
quote:
Originally posted by Pradeep
Hi,
I recently switch from using a Linksys router to a Windows 2003 server
configured as a router. Everything seems to be working as expected. I
am also able to use standard Microsoft VPN client to connect to the
outside world.
The only problem that I am running into is that cisco VPN client does
not work. I can connect to the host and register my machine. However,
I cannot ping to any machine on the host system. This setup used to
work flawlessly with the Linksys router.
Does anyone have any idea on what could be going on? I even tried to
turn Internet Connection Firewall (ICF) off on the WAN connection. But
this did not help.
On the Windows 2003 system, all I had to do was to turn on "Allow
Internet Sharing" on the WAN network card. Very simple. I didn't even
have to install "Routing and Remote Access" Windows component. Now I
am wondering if this is the problem.
Thank you in advance for your help.
Pradeep
| |
| Some One 2004-11-15, 12:29 pm |
| try pinging the same interfaces on the machines.
and then see if its working or ICMP requests are working.
--> If the cisco vpn client can reach the machine and can register then it seems it can reach the machine and understand the requests. but the connection is not complete. Either its just conneceted to the machine but its not registered with the server properly! or its not on the same domain. check if the server can ping cisco clients interface. AND you didnt explained that can you reach the otherside of that gateway? With anyother request? HTTP? FTP?
if so then the ICMP on cisco vpn client is turned off. check if the cisco vpn client can ping its own interface
if the interfaces are on the same network atleast they should ping each other?
one reason can be that the interfaces ips are not known and your connection established on some other protocol
or the vpn connection is not complete.
check the domain and all on cisco machine......
win3k server needs all the desired protocols to be installed.
windows own vp client might not need all the protocols to work.
it might use netbui for the requests. or ecapsulate the connection with some other protocol. but for IP based networks you need to assign IP addresses to the interfaces. And in connection sharing proceedure... either you need that the client machine also make the connection with the server. as your windows clients are doing...
so set the connection on cisco vpn client as well so that it also can reach the world. as you had made vpn connection on the the window machines.
either set the cisco vpn client with approriate ip addresses.
or turn on dhcp on the interface which connects to the server.
the syslink vpn routter and windows connection sharing works differently.
so try checking all of option needed for an appropriate connection. |
|
|
|
|