1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

QuickVPN+ cannot ping

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by whomm, Aug 23, 2008.

  1. whomm

    whomm Guest

    Hi,

    I've installed QuickVPNplus version 1.0.6 abd I'm using a config file called config.xml. Config file looks like indicated below. I'm running the command "QuickVPNPlus -f config.xml -v. I get the following output. Can anyone see why I cannot ping at the end? It does give somewhere a Authorization 12045 error, but I believe this has nothing to do with the problem?
    BTW: Greenbow VPN client is working perfect.

    QuickVPNplus_1.0.6>QuickVPNplus.exe -f config.xml -v
    QuickVPNplus ver: 1.0.6
    Flags: 0 (0x0)
    OSver: 5.1
    Local ip address: 192.168.2.51

    Requesting configuration data from X.X.X.X ...
    [T] Uri: https://test:aaaa@X.X.X.X:60443/StartConnection.htm?version=1?IP
    =192.168.2.51?PASSWD=aaaa?USER=test

    using WinInet
    [W] Authorization 12045 - De certificeringsinstantie is ongeldig of onjuist

    SSLsrvCert: 00:16:b6:83:51:04 RV042 "Cisco-Linksys, LLC" US Irvine California
    [T] HttpQueryInfo 401
    [T] Setting HTTP username/password
    [T] HTTP response: 200 - OK

    [T] Server response
    ---------------------------------

    version=1
    msgtype=configuration
    conn test_rw
    presharedkey=201bea6f8dfbfcdc
    rightsubnet=192.168.25.0/24
    remotelanip=192.168.25.254
    dnsserver=192.168.25.254
    domain=test.local

    ---------------------------------
    LocalAddr: 192.168.2.51
    LocalMask: 255.255.255.255
    LocalSubnet: 192.168.2.51/255.255.255.255
    Presharedkey: 201bea6f8dfbfcdc
    DNSserver: 192.168.25.254
    RemoteNet: 192.168.25.0
    RemoteMask: 255.255.255.0
    RemoteSubnet: 192.168.25.0/255.255.255.0

    Deactivating ipsec policy QuickVPNplus ...
    ipseccmd -w REG -p QuickVPNplus -y

    The command completed successfully.
    Removing ipsec policy QuickVPNplus ...
    ipseccmd -w REG -p QuickVPNplus -o

    The command completed successfully.
    Creating ipsec policy QuickVPNplus rule Host-RemoteNet ...

    ipseccmd -w REG -p QuickVPNplus -r Host-RemoteNet -t X.X.X.X -f 192.168.2.
    51/255.255.255.255=192.168.25.0/255.255.255.0 -n ESP[MD5,3DES]3600S/50000KPFS -a
    PRESHARE:"201bea6f8dfbfcdc" -lan -1p

    The command completed successfully.
    Creating ipsec policy QuickVPNplus rule RemoteNet-Host ...

    ipseccmd -w REG -p QuickVPNplus -r RemoteNet-Host -t 192.168.2.51 -f 192.168.25
    .0/255.255.255.0=192.168.2.51/255.255.255.255 -n ESP[MD5,3DES]3600S/50000KPFS -a
    PRESHARE:"201bea6f8dfbfcdc" -lan -1p

    The command completed successfully.
    Activating ipsec policy QuickVPNplus ...

    ipseccmd -w REG -p QuickVPNplus -x

    The command completed successfully.

    Configuration done.

    Activating tunnel...

    Pingen naar 192.168.25.254 met 32 byte gegevens:

    Time-out bij opdracht.
    Time-out bij opdracht.
    Time-out bij opdracht.
    Time-out bij opdracht.

    Ping-statistieken voor 192.168.25.254:
    Pakketten: verzonden = 4, ontvangen = 0, verloren = 4
    (100% verlies).



    <?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
    <quickvpnplus version="1">

    <!-- ******* the following parameters MUST be defined either here or using cmd line switches ******* -->
    <vpnrouter>X.X.X.X</vpnrouter>
    <userid>test</userid>

    <!-- ******* password if not defined here or in the cmd line will be requested during program execution ******* -->
    <password>tester</password>

    <!-- ******* QuickVPNplus by default uses port 443. You may need to use 60443 with some routers ******* -->
    <port>60443</port>

    <!-- ******* if QuickVPNplus is not obtaining a proper localaddr, define it here ******* -->
    <localaddr>Y.Y.Y.Y</localaddr>

    </quickvpnplus>
     

Share This Page