Re: Norton VS: my LAN

From: Lars M. Hansen (badnews_at_hansenonline.net)
Date: 02/29/04


Date: Sun, 29 Feb 2004 11:48:50 GMT

On 28 Feb 2004 23:58:35 -0800, Paul spoketh

>I'm using NIS 2004 on my home lan. I thought it was easy to configure
>and all that, but it kills the network protocol when I use it! Both
>machines have access to each other (2000 Pro and XP Pro) just fine if
>I disable NIS on them...but neither machine can see the other one if
>it is enabled.
>
>Suggestions greatly appreciated. I have used Norton Security both
>WITH firewall enabled and without.

Configure your other computer(s) as a trusted source.

Lars M. Hansen
www.hansenonline.net
Remove "bad" from my e-mail address to contact me.
"If you try to fail, and succeed, which have you done?"



Relevant Pages

  • Re: XP Network Browse Problems
    ... If the Win2000 machines boot first, ... >sharing on the local subnet. ... When you say "boot first", do you actually shut ALL computers down ... On the XP Pro computer, check to see if Simple File Sharing (Control Panel - ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem with After Update (and other) events
    ... to the other machines. ... Decompile etc. had no effect. ... new database, nothing in it except a form with a combo ... Win XP Pro En, ...
    (microsoft.public.access.forms)
  • Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... I have two machines. ... I know that this has something to do with the network. ... the BSOD only occurs on XP Pro. ... Use .symfix to have the debugger choose a symbol path. ...
    (microsoft.public.windowsxp.help_and_support)
  • Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... I have two machines. ... I know that this has something to do with the network. ... the BSOD only occurs on XP Pro. ... Use .symfix to have the debugger choose a symbol path. ...
    (microsoft.public.windowsxp.network_web)
  • Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... I have two machines. ... I know that this has something to do with the network. ... the BSOD only occurs on XP Pro. ... Use .symfix to have the debugger choose a symbol path. ...
    (microsoft.public.windowsxp.hardware)