Okay, well... SSH/REMOTE DESKTOP SHARING/HTTP seem not to work, a new redhat 9 install here.

I havent been using linux for a while so go easy on the newb.

Pinging 192.168.0.133 with 32 bytes of data:

Reply from 192.168.0.133: bytes=32 time<10ms TTL=128
Reply from 192.168.0.133: bytes=32 time<10ms TTL=128


That does work.



But ssh says connection refused (even if i use root and type 'ssh localhost', same error message.


Same error message when connecting with remote VNC FOR windows


Guess what?

http://127.0.0.1 on the linux box: connection refused when attempting to connect to 172.0.0.1



Yet, HTTPD is started, (and restarted with the apachectl command) and while its showing all the [ OK ] at startup i see that ssh and ss2 2 are started.

Odd isn't it?

what's wrong?

SSHD needs to be running on the machine you are trying to ssh to. ps aux | grep sshd and see if it is running.

"Yet, HTTPD is started, (and restarted with the apachectl command) and while its showing all the [ OK ] at startup i see that ssh and ss2 2 are started."

Could also be incompatable version to what you are running, as well. I've had that happen, remote server upgrades ssh and you stay on an older version...then no workie.

I would double check sshd to make sure it doesn't die for some reason. Just because you see "ok" during boot for that demon doesn't mean something didn't kill it off for some odd reason. Then check the version/type of ssh (openssh vs ssh) on your system and the system you are trying to connect to. New ssh packages came out that address vulnerablities not to long ago for both the distros you have in your info.

just another thing to point out is that even though you see it fire up in the startup doesn't mean its going to work once you log in, that is until you configure it....i notice your ip above that you pinged which is obvious that you are on a LAN, so first thing is to setup in your httpd.conf file that 192.168.0.133 is the ip it should "Listen" to...then if you use (which i assume you do) a router, then you'll have to forward connections on port 80 to that ip...
so with that said you now see that you have to setup some cfg's before it will actually work, and now you should also see what i meant by the commnent "even though it loads in the startup it may not work"...