Channon, Just in case you cannot restart the production server at will, here maybe some hints : 1. do a "netstat -nalp | grep ':22'", see if some process is really listening on port 22, and whether it is listening at IP address "0.0.0.0" instead of just "127.0.0.1". 2. restart ssh by "service sshd restart" 3. do a "telnet <127.0.0.1> 22" and a "telnet <eth0 IP address> 22" and see if the socket connection can be made. If the first telnet failed while the second one can, and that sshd is listening from IP address "0.0.0.0" (from step 1), it is obviously caused by your iptables rules. I would do a "rmmod iptables" and retry. 4. you may also try to restart the LAN by "ifconfig eth0 down" then "ifconfig eth0 up" and see if it makes any difference Regards, Raymond. On Thu, 2003-03-20 at 02:23, Michael Smith wrote: > Sound like you're not at the server... if you know someone who is I'd > try re-booting. > On Wed, 2003-03-19 at 09:14, Quillen, Channon wrote: > > I am able to ping the server. I am also able to login at the console > > and ping out, ssh to localhost, and ftp to localhost. The telnet > > service is disabled. > > > > I thought it might be a problem with iptables becoming corrupt (that > > has happened before on another server), so I tried to flush 'em > > (#iptables -F) and was given the dreaded "...can't initialize iptables > > table 'filter': iptables who? (do you need to insmod?)" So, I stopped > > the service (#service iptables stop) and then flushed 'em again. That > > flush was successful. > > > > However, I'm still not able to ssh to the server from my workstation. > > It times-out whereas before it would connect with no problem. When I > > try to ftp, I get the same problem - it times-out. I am able to run a > > service scan from my workstation and see port 21 but not port 22. > > > > -Channon > -- > Michael Smith <msmith@xxxxxxxxxxxx> > Custom87.net -- Raymond Fung <raymondf@xxxxxxx> -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/psyche-list
