Chiu, PCM (Peter) wrote:
Thanks, Joe,
Maybe a mix-up on terminalogy used.
I did restart firewall by invoking
/etc/init.d/SuSEfirewall2_init restart
and
/etc/init.d/SuSEfirewall2_setup restart
-----Original Message----- From: Joe Morris (NTM) [mailto:Joe_Morris@ntm.org]
Since you seem to indicate it IS a firewall issue, and not a PAM issue, I would suggest doing what many of us are doing (but which seems to be a bug), and that is SuSEfirewall2 stop, then SuSEfirewall2 start, which for me has always worked. For some reasons unknown to me (and since the fix was just as easy) this seems to flush the rules and works better than a restart. YMMV. HTH.
Please do not top post, as it messes up the conversational style of email exchange. I think you misunderstood what I was saying. Since a long time ago (and recently mentioned on the security list), it was my experience that your commands above do not always work, while the ones I gave you (above) do. -- Joe Morris Registered Linux user 231871 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org