Re: [sentinix-list] (no subject)

You've got some communication problems... check routing table... default 
gateway... if NIC's IP address is duplicate.  If that appears to be OK, what 
hardware do you use? NIC?, etc...  Once I experienced some weird TCP/IP 
problems with a weird unknown NIC, occasionally no outbound connections would 
establish, and other weird stuff.

You do *not* need to touch /etc/hosts.allow, has nothing to do with this.

	Michel

On Thursday 18 March 2004 20:03, RichardKebo-JdlnA/[email protected] wrote:
> Hello All again,
> Not sure why adding sshd: ALL to the /etc/hosts.allow file would make the
> difference, but gave it a try anyway. Still no workie.
>
> Let me restate: port 22 SSH is the only port that appears to be listening
> when a remote client NMAP's the Sentinix server.
>
> I am trying to connect to the Sentinix server with a web browser via port
> 443 SSL. I can occassionally connect to the server via SSL. Other times I
> get a connection refused.
>
> We set up Sentinix on another server to try to duplicate the problem.
> After installed, a remote client that NMAP this test Sentinix server shows
> all the necessary ports listening; 22/ssh, 80/http, 443/https, 199/smux,
> 3306/mysql. These ports do NOT show up listening on my production Sentinix
> server from a remote host. These ports do show up if I NMAP the production
> Sentinix server from the console of the Sentinix server and NMAP local
> host.
>
> Any ideas?
>
> Richard
>
>
>
>
> Date: Wed, 17 Mar 2004 12:50:17 -0500 (EST)
> From: [email protected]
> Subject: Re: [sentinix-list] Remotely Accessing Sentinix Box
> To: The SENTINIX Mailing List <[email protected]>
> Message-ID: <Pine.LNX.4.58.0403171248210.32739-pPEfdzAmgTHiB9QmIjCX8w@public.gmane.org>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Add:
>
> sshd : ALL
>
> to the /etc/hosts.allow file and see if you can connect then.  You can
> change the all to an ip address.
>
> On Wed, 17 Mar 2004 RichardKebo-JdlnA/[email protected] wrote:
> >    I wrote before regarding this issue.
> >
> >    I am having diff= iculty connecting to the Sentix box. I am often,
>
> not
>
> >    always, getting a conn= ection refused. Occassionally, I will
>
> connect,
>
> >    but often times I am not abl= e to keep the connection going. When I
> >    first posted this issue, I was told = to check my gateway, IP
>
> addresss
>
> >    etc. Which I have done. We are on the same= sub-net anyway. When I
> >    Nmap the box, only SSH shows open. When I nmap loca= lhost, all the
> >    services show up.
> >
> >    I checked IPtables and all defa= ult policies are set to ACCEPT.
> >
> >    I have tried reinstalling a coup= le of times with both Openmossix
>
> SMP
>
> >    and plain Linux SMP kernels.
> >
> >    Is it possible there is a problem with the NIC module? This is a
> >    Broadcomm= Gigabit Ethernet card. lsmond shows the tg3 module being
> >    loaded. I have us= ed the tg3 mod on other boxes with Debian and have
> >    not had this type of tro= uble.
> >
> >    The box is a IBM x335 with twin P-4 Xeon 2.4 and 1.5 GB RAM= .  eth0
> >    has the IP address statically set. eth1 has no IP address assi= gned.
> >    eth1 is the interface snort is listening on.
> >
> >    Any ideas?
> >
> >    Thanks,
> >
> >    Richard
>
> _______________________________________________
> SENTINIX mailing list
> [email protected]
> http://elevenprospect.com/mailman/listinfo/sentinix