LnS...small problem (new user)

Discussion in 'LnS English Forum' started by ron spencer, Nov 17, 2007.

Thread Status:
Not open for further replies.
  1. ron spencer

    ron spencer Registered Member

    Joined:
    Nov 17, 2007
    Posts:
    9
    I have just installed this program and REALLY like it so far. Thanks. I have one issue (I am just using the standard rules/enhanced rules). I run a linux based server (NASLite) in our home...I can ftp to it and telnet no problem. I have also mapped some network drives as well to the server.

    Now, the ftp and telnet ALWAYS work....but for some reason the mapped network drives are not accessible....the server is also not seen via network neighbourhood; nothing is there....but ftp and telnet STILL work!!!!

    The IP of the server is static. Now is this an Explorer problem for LnS rule note setup? I think it is LnS because if I quit the program the mapped drives come back right away...and if then reload LnS they will remain. This is weird but I can reproduce this everytime....any ideas how to get LnS to work right away with our server?

    thanks
     
  2. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Hi

    For file sharing, yes, you need to import additional rules because ports 137-139 are blocked by default.
    Here are the rules:
    http://www.looknstop.com/En/rules/rules.htm#Partage

    If your sub-network is different from 192.168.x.y, you have to edit the rules to replace 192.168 by your sub-network address.

    Regards,

    Frederic
     
  3. ron spencer

    ron spencer Registered Member

    Joined:
    Nov 17, 2007
    Posts:
    9
    works!!!!

    thanks....

    curious though....why would have ftp and telnet worked and network mapped drives not without the rules in place?

    good proggy!!!
     
  4. nuser

    nuser Registered Member

    Joined:
    May 31, 2007
    Posts:
    105
    Location:
    Singapore
    ftp or telnet are 'standard' client applications, so they are allowed by the default rule 'Allows programs to communicate to remote servers." (below the 'blocking Syn' rule, which is the delimitation of server rules and client rules.)
    But for file or printer sharing, the local ports (137-139) are blocked by default, so user has to allow them explicitly.
     
  5. ron spencer

    ron spencer Registered Member

    Joined:
    Nov 17, 2007
    Posts:
    9
    thanks for the info.....and the help. This firewall is different, but very flexible and no overhead. If all goes well over my 30 days trial I think it will be a purchase.

    I have seen the "Phantom rules" to buy...are they worth it?
     
Thread Status:
Not open for further replies.