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

To: "Chris J. VanderVelde" <cvandervelde,AT,hinesis,DOT,com>
Subject: Re[2]: Problems with Cipe on Windows 2000 Pro
From: Rainbow <dbasko,AT,rainbow,DOT,by>
Date: Thu, 3 Jul 2003 01:19:55 +0200
Cc: cipe-l,AT,inka,DOT,de, "Damion K. Wilson" <dwilson,AT,ibl,DOT,bm>
In-reply-to: <200307021701.21522.dwilson@ibl.bm>
Organization: Rainbow Technologies
References: <F888E9109538AC4295AC3AD44D200E2F03EF0A@exch1.branches.his.hinesis.com><200307021701.21522.dwilson@ibl.bm>
Reply-to: Dmitry Basko <dbasko,AT,rainbow,DOT,by>

Hello,
just small 2 additional hits, may be it can be useful:
1) Do not use encryption at all for testing purposes. The length of
static key in WIN 32 implementation has to be 32 symbols, like this:
<01234567012345670123456701234567>
2) When you successfully started cipdrvr and cipsrvr (as Damion said
before, the best way is running cipsrvr.exe in console mode ), check
ARP table : arp -a. The table will not contain record like
"192.168.7.100 08:00:58:00:00:02" (08:00:58:00:00:01 is MAC of CIPE
virtual adapter). Run "ping 192.168.7.100". It seems, the result will
be negative. Ok check ARP table again - probably you will see the
mentioned record "192.168.7.100 08:00:58:00:00:02". In this case, CIPE
driver and CIPE service work fine and most likely, the reason of
problem with connect is settings (static key must be checked at
first).

Wednesday, July 02, 2003, 10:01:21 PM, you wrote:

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

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

DKW> cipsrvr noservice

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

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

DKW> DKW

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

DKW> --
DKW> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
DKW> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
DKW> Other commands available with "help" in body to the same address.
DKW> CIPE info and list archive: 
<URL:http://sites.inka.de/~bigred/devel/cipe.html>

-- 
Best regards,
 Rainbow                            mailto:dbasko,AT,rainbow,DOT,by


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