<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: "Chris J. VanderVelde" <cvandervelde,AT,hinesis,DOT,com>
Subject: Re: Problems with Cipe on Windows 2000 Pro
From: "Damion K. Wilson" <dwilson,AT,ibl,DOT,bm>
Date: Wed, 2 Jul 2003 17:01:21 -0300
Cc: cipe-l,AT,inka,DOT,de
In-reply-to: <F888E9109538AC4295AC3AD44D200E2F03EF0A@exch1.branches.his.hinesis.com>
References: <F888E9109538AC4295AC3AD44D200E2F03EF0A@exch1.branches.his.hinesis.com>
Reply-to: dwilson,AT,ibl,DOT,bm

That all looks correct to me. Were the old Linux settings the same as the 
CIPE-Win32 settings now ?

You can stop the service and then run cipsrvr from the console with

cipsrvr noservice

Also, you can run DbgView to capture the log messages.

Lastly, run tcpdump on the Linux side to see if tunnel packets are travelling 
back and forth.

DKW

On Wednesday 02 July 2003 04:44 pm, you wrote:
> I'm having problems with connecting Windows 2000 clients to my Linux CIPE
> server.  I can connect Linux clients just fine with no problems, but
> Windows will just not connect.
>
> I've downloaded and installed the newest Windows Client for CIPE.
>
> Here is my configuration:
>
> Windows 2000 Pro Client (SP4):
> Physical NIC Address:  192.168.16.8 255.255.255.0     GW: 192.168.16.1
> Virtual NIC Address:  192.168.7.101 255.255.255.0     GW: none
>
> CIPE Settings from Control Panel
> LAN IP Settings>
>       Local IP Address: 192.168.16.8  Port 7777
>       Peer IP Address:  192.168.16.1 Port 7777
> PTP IP Settings>
>       Local PTP Address: 192.168.7.101
>       Peer PTP Address: 192.168.7.100
> Status>
>       Enabled
> Key Settings>
> Static Key:  XXXXXXXXXXXXXXXXXXXXXXXX
> Cipher:       Blowfish
> Time Out:  600
>
> Linux Server:
> Eth0:  192.168.16.1 255.255.255.0
>
> CIPE Tunnel
> Device: cipcb0
> Tunnel Through Device: eth0(192.168.16.1)
> Local Port: 7777
> Remote Peer Address: 192.168.16.8
> Remote Peer Port:  7777
> Remote Virtual Address:  192.168.7.101
> Local Virtual Address:  192.168.7.100
> Security Key:  XXXXXXXXXXXXXXXXXXXXXXXX
>
> The CIPE service appears to be running on my Windows PC, the device & CIPE
> settings appear to be correct, but I don't know what else to change to
> establish the connection.
>
> Do you have any ideas?  Is there something I'm missing?  Setting up the
> Linux client was pretty simple.
>
> Thanks for the help.
>
> Chris VanderVelde, MCSE
> cvandervelde,AT,hinesis,DOT,com
>
> Hines Information Solutions
> 1218 E. Pontaluna Rd.
> Spring Lake, MI 49456
> Phone: (231)799-6263
> Fax: (231)799-6200


<< | Thread Index | >> ]    [ << | Date Index | >> ]