RE: [SLE] Problems with susefirewall2

From: Stephen Furlong (stephen_at_freemail.servebeer.com)
Date: 02/26/05

  • Next message: Mike Dewhirst: "[SLE] Assigned IP Address"
    To: "'Suse Mailing List'" <suse-linux-e@suse.com>
    Date: Sat, 26 Feb 2005 09:13:55 -0000
    
    

    That's where my problem is. I can open them up on the linux box, but the
    moment I put the forwarding rule in they close again. I know the
    program/server on the other side is listening to the connections because I
    plugged it directly into my router and port forwarded on that and it worked,
    it just doesn't work through my suse machine

    -----------------------------------------------
    Sent by freemail.servebeer.com
    Signup for your free 100mb Mail account today!
    Full pop3/smtp accounts available!!
    -----------------------------------------------

    -----Original Message-----
    From: Carlos E. R. [mailto:robin1.listas@tiscali.es]
    Sent: 26 February 2005 02:27
    To: 'Suse Mailing List'
    Subject: RE: [SLE] Problems with susefirewall2

    The Saturday 2005-02-26 at 00:07 -0000, Stephen Furlong wrote:

    > Needs another bump up as ive had no reply yet :(

    I'm no firewall expert, but I'll try.

    > Im running suse9.2 on my server box connected via wireless to my desktop
    > machine. Im trying to poke through certain ports from my suse box onto my
    > desktop machine. When I use the firewall wizard in yast and use the
    "expert
    > options" to open the ports (4000:4200) shields up! Lists them as "closed".

    Opening a port in the firewall is not enough; there must be a service or
    daemon behind responding on that port. Till that moment, they should show
    up as "closed".

    Also, if your intention is that another (2nd) machine answers on those
    ports, simply opening them up in the firewall is not enough.

    --
    Cheers,
           Carlos Robinson
    --
    Check the headers for your unsubscription address
    For additional commands send e-mail to suse-linux-e-help@suse.com
    Also check the archives at http://lists.suse.com
    Please read the FAQs: suse-linux-e-faq@suse.com
    -- 
    Check the headers for your unsubscription address
    For additional commands send e-mail to suse-linux-e-help@suse.com
    Also check the archives at http://lists.suse.com
    Please read the FAQs: suse-linux-e-faq@suse.com
    

  • Next message: Mike Dewhirst: "[SLE] Assigned IP Address"

    Relevant Pages

    • Re: [SLE] port 25 only accepts connections from localhost
      ... Allen Seelye wrote: ... I just had the bright idea to shut the firewall off and try to send ... The port is still only accessible by the localhost even with ... Please read the FAQs: suse-linux-e-faq@suse.com ...
      (SuSE)
    • [SLE] gnutella firewalled on 6346
      ... I have SuSEfirewall2 configured with port 6346 open but ... gtk-gnutella tells me that I'm firewalled and no one can ... Here is my firewall: ... Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com ...
      (SuSE)
    • Re: keeping ports open
      ... If a port is open, it means that 1) a software or service is running on your ... and 2) you're not using a firewall or your firewall isn't ... Use firewall software and hardware and antivirus software that is ... Follow the instructions for hardening Windows and IIS at ...
      (microsoft.public.security)
    • Re: How to Maintain an IIS Server?
      ... > server running on a Windows 2000 server. ... before a firewall and antivirus have been installed]. ... open ports; however, this will not identify which program is using the port. ...
      (microsoft.public.inetserver.iis.security)
    • Re: CEICW fails at firewall config
      ... ISA Server prevents connection to a remote desktop when you connect through ... Remote Web Workplace on a Windows Small Business Server 2003-based computer ... Acceleration Server as a firewall. ... connection uses TCP port 4125. ...
      (microsoft.public.windows.server.sbs)