Dell Server with Linux and Plesk 7

[James Mendez]

Sorry , but I have not got a clue of what you just said...

thanks

James

-----Original Message-----
From: owner-tlug-lxSQFCZeNF4 at public.gmane.org [mailto:owner-tlug-lxSQFCZeNF4 at public.gmane.org]On Behalf Of Walter
Dnes
Sent: Friday, December 17, 2004 6:54 PM
To: tlug-lxSQFCZeNF4 at public.gmane.org
Subject: Re: [TLUG]: RE: Dell Server with Linux and Plesk 7


On Thu, Dec 16, 2004 at 09:02:05PM -0500, James Mendez wrote
> I need help from anyone wishing to assist.
> 
> I have a Dell server with linux redhat and plesk 7 installed. my
> ports does not seems to work at all. I cant SSH, FTP or call up
> any of my websites. Seems like the ports closes everytime I reset
> them. The server is attached to a linksys AP router and another
> desktop is also attached to this router. The router is attached to
> cogeco cable box. All recieve internet. But the desktop cannot ftp
> or see the website. Please assist even if it means coming over.

  Cogeco territory is a bit outside the range of a Toronto or York
Region bus fare, so my help will have to be remote.  Here's a basic
checklist; hope it doesn't insult you by mentioning some glaringly
obvious things.  I don't know your expertise level, so I'm going to
start from square 1.

  - I assume that the router shows one public IP address and an RFC1918
    IP address internally, like 192.168.0.1 (or something similar)

  - If you want your machines to talk to each other, it becomes much
    easier if you assign static IP addresses to them (e.g. 192.168.0.2,
    192.168.0.3, etc).  Imagine trying to maintain a long-distance
    romance if your girlfriend's phone number changes every day.  While
    you're at it, make sure that all machines on your lan have names in
    /etc/hosts on all machines.

  - Some firewalls have rules to block RFC1918 addresses.  They should
    never be seen coming in from outside.  However, they're perfectly
    OK coming in from your little LAN.  Check for any iptables rules
    blocking the IP address of your desktop.

  - The sshd and ftpd servers I've used require holes to be poked in
    /etc/hosts.allow, regardless of whether or not you're running inetd
    or xinetd.  While you need an entry for sshd in hosts.allow, do *NOT*
    put an entry for sshd in your inetd configuration file.

  - sshd requires an entry in its config file, specifying which IP
    address it is listening on.  ftpd is very nitpicky if you're setting
    up anonymous ftp.  You need the right set of directories with the
    right set of permissions

-- 
Walter Dnes <waltdnes-SLHPyeZ9y/tg9hUCZPvPmw at public.gmane.org>
An infinite number of monkeys pounding away on keyboards will
eventually produce a report showing that Windows is more secure,
and has a lower TCO, than linux.
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml


--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml