RE: [cobalt-users] PortSentry Error - RAQ4r

["John Cordeiro" <jcordeiro@xxxxxxxxxxxxxxx>]

how are you starting the protscanner. Remember only start one Protocol
option per protocol

like
portsentry -atcp
portsentry -audp

dont try starting all of the options that's a common mistake

like

portsentry -tcp
portsentry -stcp
portsentry -udp
portsentry -sudp

this will cause errors cause the scanner is already bound to the ports.
-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Curtis Ross
Sent: Thursday, February 15, 2001 11:39 AM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: [cobalt-users] PortSentry Error - RAQ4r


Hello All,

I'm receiving an error on Port 143 when I start PortSentry. Is this
IMAP? How do I avoid it?

Feb 15 09:22:32 www portsentry[502]: adminalert: Psionic PortSentry 1.0
is starting.
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 1
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 11
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 15
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 79
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 111
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 119
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 143
Feb 15 09:22:32 www portsentry[503]: adminalert: Psionic PortSentry 1.0
is starting.
Feb 15 09:22:32 www portsentry[508]: adminalert: ERROR: could not bind
TCP socket: 143. Attempting to continue
Feb 15 09:22:32 www portsentry[508]: adminalert: Going into listen mode
on TCP port: 540
etc, etc,


Thanks,

Curtis

_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users