LnS and Linksys router question

Discussion in 'LnS English Forum' started by JST1960, Oct 12, 2005.

Thread Status:
Not open for further replies.
  1. JST1960

    JST1960 Registered Member

    Joined:
    Aug 29, 2005
    Posts:
    20
    Location:
    Grapevine, Texas
    I purchased LnS and I must say I really
    like it. I have used the thread here to
    set it up with the enhanced rule set also.

    My question is, I am running a Linksys
    WRT54G wireless router (not using the wireless)
    and I have had no problems at all with LnS, so
    do I need to follow the thread on how to
    setup LnS using a router?

    The main reason I am asking is, every few days
    after running a Speakeasy speed test I am
    getting a Windows error. I did a reformat on
    this box a few days ago, and after I finished,
    thats when I loaded LnS. The reformat went
    just fine, so this isn't a botched Windows XP Pro
    SP2 install.

    I did not document the error message, I will the
    next time it happens. I did, however, look at
    Event Viewer (system) and it showed event # 8032

    I am thinking that maybe running LnS behind the
    Router might be causing this?

    Sorry for the long post, but I'm kind of concerned
    about this.

    Thanks for any help or tips!
     
  2. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Hi,
    No you don't need to apply this post if it already works.

    Not sure this problem is related to Look 'n' Stop.
    Did you try a google search with "event viewer 8032". There may be some interesting results.
    No problem, not so long actually ;)

    Frederic
     
    Last edited: Oct 21, 2005
  3. JST1960

    JST1960 Registered Member

    Joined:
    Aug 29, 2005
    Posts:
    20
    Location:
    Grapevine, Texas
    Thanks Frederic!

    I have done some research on Event ID 8032.
    It has to do with the browser, which in my case
    is IE. After reading and looking at the LnS setup,
    I have found this setting under advanced options.

    Clicking on protocols then into protocols configuration,
    I see that there are two items allowed.
    TCPIP.SYS & NETBT.SYS

    Could the NETBT.SYS be the culprit?
     
  4. Phant0m

    Phant0m Registered Member

    Joined:
    Jun 7, 2003
    Posts:
    3,684
    Location:
    Canada
    You have Network setup there?
     
  5. JST1960

    JST1960 Registered Member

    Joined:
    Aug 29, 2005
    Posts:
    20
    Location:
    Grapevine, Texas
    Network as in file and print sharing? Yes

    One other thing, I had installed the file
    and print share rule when I set up LnS.
    But I did not set up networking in windows
    untill yesterday. Also I have not had the
    windows error since setting up networking
    on this computer.

    Could having the sharing rule in LnS without
    the computer being set up for networking
    have caused this?
     
    Last edited: Oct 13, 2005
  6. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    I suppose NETBT is allowed, so the problem should not be there.

    Frederic
     
  7. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    No I don't think so.

    If Look 'n' Stop is not started at all (but still installed), do you encounter this error event ?

    Frederic
     
  8. JST1960

    JST1960 Registered Member

    Joined:
    Aug 29, 2005
    Posts:
    20
    Location:
    Grapevine, Texas
    Frederic, I have not had the error
    since setting up my network on this
    computer.
    I will post back if the error occurs
    again. Like I said in my previous post,
    I had the file and print sharing rule
    installed in LnS without networking
    configured on this computer. I am
    thinking this might have caused my problem,
    since it has not happend again.
    Only time will tell, I guess!

    Thanks for all of your help, I am very
    happy with this firewall:)
     
Thread Status:
Not open for further replies.