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

Subject: Re: cipsrvr not starting or staying started
From: Phil Scarratt <fil,AT,draxsen,DOT,com>
Date: Mon, 17 Mar 2003 00:05:53 +0100
In-reply-to: <3E720165.50502@draxsen.com>

DOH!!!

Please disregard the last message. Although there is nothing bound to 
10001 already, an nmap scan from the gateway reveals that port 10000 is 
closed. Any ideas on how to "open" ports on Win2k?

Fil-the-red-faced

Damion Wilson wrote:
> Is something else on your box bound to UDP port 10001 already ?
> 
> DKW
> 
> On Friday 14 March 2003 05:26 pm, Phil Scarratt wrote:
> 
>>Yes tried that. Most of the time it gives me messages like
>>
>>[SERVICE_MANAGER] service [CIPE] has already been started
>>[{EDEB51FF-9E90-4767-9BB0-7AD1C631A4FC}] TAP started on
>>[\\.\{EDEB51FF-9E90-4767-9BB0-7AD1C631A4F
>>[cedars] Can't bind to port [10001]
>>
>>abnormal program termination
>>
>>meaning it thinks it is already started even though it is not listed in
>>processes list in Task Manager.
>>
>>In fact, doing a cipsrvr stop directly after the above message produces:
>>
>>[SERVICE_MANAGER] service [CIPE_Daemon] has already been stopped
>>
>>Subsequent starts show the message
>>
>>[SERVICE_MANAGER] Starting service [CIPE_Daemon]
>>
>>waits awhile and then dies coming back to the command prompt (and
>>cipsrvr.exe disappears from process list in task manager). Is it
>>encounting too many errors? Is there a debug output or something?
>>
>>The only reproducable way I can get it to start and stay is if I untick
>>the Enabled box on the Status section of the peer settings. cipsrvr
>>console then starts the service, leaves cipsrvr running and waits for
>>some action. The only output I get is
>>
>>[SERVICE_MANAGER] service [CIPE] has already been started
>>[{EDEB51FF-9E90-4767-9BB0-7AD1C631A4FC}] TAP started on
>>[\\.\{EDEB51FF-9E90-4767-9BB0-7AD1C631A4FC}.tap]
>>
>>That's it. It just sits there. I try and ping and the interface still
>>reports 0 packets sent. Is there a routing issue? My routing tables on
>>the Win2k client is as follows:
>>
>>===========================================================================
>>===========================================================================
>>Active Routes:
>>Network Destination        Netmask          Gateway       Interface  Metric
>>           0.0.0.0          0.0.0.0    192.168.1.200   192.168.1.201      
>>1 127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
>>192.168.0.0    255.255.255.0      192.168.1.1     192.168.1.1       1
>>192.168.0.1  255.255.255.255      192.168.1.1     192.168.1.1       1
>>192.168.1.0    255.255.255.0      192.168.1.1     192.168.1.1       1
>>192.168.1.0    255.255.255.0    192.168.1.201   192.168.1.201       1
>>192.168.1.1  255.255.255.255        127.0.0.1       127.0.0.1       1
>>192.168.1.201  255.255.255.255        127.0.0.1       127.0.0.1       1
>>192.168.1.255  255.255.255.255      192.168.1.1     192.168.1.1       1
>>192.168.1.255  255.255.255.255    192.168.1.201   192.168.1.201       1
>>224.0.0.0        224.0.0.0      192.168.1.1     192.168.1.1       1
>>224.0.0.0        224.0.0.0    192.168.1.201   192.168.1.201       1
>>255.255.255.255  255.255.255.255    192.168.1.201   192.168.1.201       1
>>Default Gateway:     192.168.1.200
>>===========================================================================
>>
>>The remote network is 192.168.0.0/24 with remote cipe node 192.168.0.1
>>
>>Anything you can glean from all this is much appreaciated.
>>
>>Thanx
>>
>>Fil-the -baffled
>>
>>Damion Wilson wrote:
>>
>>>I assume that you have setup the peer information correctly in the CIPE
>>>control panel. So, try running it from a command prompt with:
>>>
>>>cipsrvr console
>>>
>>>DKW
>>>
>>>On Friday 14 March 2003 12:20 pm, Phil Scarratt wrote:
>>>
>>>>Hi people
>>>>
>>>>Just joined the list after having searched through the archives and
>>>>trying different versions of the WIN32 port. I'm a newbie at CIPE
>>>>although it all looks straight forward. My problem is this:
>>>>
>>>>Setup: Linux remote peer with Win2k SP3 client.
>>>>
>>>>CLIENT: I can install CIPE-WIN32 (both 2.0-pre14 and pre15). Seems to
>>>>install OK although the service doesn't start. I can configure the
>>>>network connection and use the CIPE control panel to configure the peer.
>>>>My problem is that usually when I close the CIPE Setting control panel
>>>>cipsrvr stops (ie task manager no longer lists it,etc). In fact I cannot
>>>>get ANYTHING sent out of the device that had been setup.
>>>>
>>>>Hope this makes sense. Been a long day (& night). It's definitely NOT a
>>>>problem with the other end - NOTHING is getting out of the CIPE
>>>>interface on the windows client.
>>>>
>>>>Any suggestions or pointers would be MUCH appreciated.
>>>>
>>>>Fil
>>>
> 
> 
> --
> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive: 
><URL:http://sites.inka.de/~bigred/devel/cipe.html>
> 

-- 
Phil Scarratt
Draxsen Technologies
IT Contractor/Consultant
0403 53 12 71





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