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

To: Mark Smith <mark.smith,AT,avcosystems,DOT,co,DOT,uk>
Subject: Re: Win 2000 Cipe Question....
From: Mike Gende <mgende,AT,gendesign,DOT,com>
Date: Thu, 18 Dec 2003 15:45:24 -0600
Cc: cipe-l,AT,inka,DOT,de
Organization: GenDesign Corporation
References: <NCBBJMDMDGNNDPEKGMOMKENEEEAD.mark.smith@avcosystems.co.uk>

Hey Mark,

I had just typed a long dissertation on our set up when we started the 
console' program from the Run screen to include its output. After doing that, 
interface came up. Hallelujah!!

I'm not sure if I feel happy or more like a dummy. But, I'm glad it works.

So, I had thought that since the Win2000 system showed the interface as 
that Win32 Cipe was actually up and working. I don't remembe reading that one 
to run cipsrvr console to get this going, but obviously I need to revisit the
'readme' file.  I was so sure our config had to be in error that I didn't
consider making sure Cipe was started. Duh.

So, now that it's working (grinning like an idiot) any suggestions on how to 
Cipe start automatically when I fire up the Aircard 555 (our modem card) to 

Thanks for the input,


> Mike,
> It's at or before this point that we usually ask for detailed information on
> your configuration (eg routing) and the IP addresses used.  If the public
> addresses cannot be revealed, by all means change them as you see fit, so
> long as it's still obvious what they should be.  Likewise, if you run both
> ends in verbose mode and attach a copy of the messages they print, this
> quite often points us to any problems.
> For the Win32 end:
> cipsrvr console
> For the linux end:
> ciped -o /etc/cipe/options cipe_debug=1
> (change for your config file and any other options you may need)
> Hope this helps,
> --
> Mark Smith - Avco Systems Ltd
> email: mark.smith,AT,avcosystems,DOT,co,DOT,uk
> Tel: +44 (0)1784 430996 Fax: +44 (0)1784 431078

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