Chiu, PCM (Peter) wrote: > Restarting firewall (by invokine /etc/init.d/SuSEfirewall2_init and > SuSEfirewall2_setup restart alone) > will NOT reactivate the service. Access is only restored after flushing > the firewall and restarting it. > > Has anyone come across the same problem? > > Any pointers here? > 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.
-- Joe Morris Registered Linux user 231871 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
