Re: Home LAN : XP Pro SP2 - passwords ? Master browser ?


"Chuck" <none@xxxxxxxxxxx> a écrit dans le message de news:
hbqh71pdt58sk4hv6t54u5iun7hqm9lbfs@xxxxxxxxxx
> On Wed, 4 May 2005 16:23:06 +0200, "Pete Kennedy"
> <peterkennedy@xxxxxxxxxx>
> wrote:
>
>>
>>"Chuck" <none@xxxxxxxxxxx> a écrit dans le message de news:
>>8ukh715nmsgi4fnltfnj94l0kh76p4q423@xxxxxxxxxx
>>> On Wed, 4 May 2005 15:09:26 +0200, "Pete Kennedy"
>><peterkennedy@xxxxxxxxxx>
>>> wrote:
>>>
>>> >
>>> >"Pete Kennedy" <peterkennedy@xxxxxxxxxx> a écrit dans le message de
>>> >news:
>>> >#AW4HLHUFHA.2056@xxxxxxxxxxxxxxxxxxxxxxx
>>> >>
>>> >> "Pete Kennedy" <peterkennedy@xxxxxxxxxx> a écrit dans le message de
>>news:
>>> >> elnLXFHUFHA.2420@xxxxxxxxxxxxxxxxxxxxxxx
>>> >> >
>>> >> > "Chuck" <none@xxxxxxxxxxx> a écrit dans le message de news:
>>> >> > an5g71t4hfclbllego09jeo6lu6lp06s05@xxxxxxxxxx
>>> >> > > On Tue, 3 May 2005 23:37:30 +0200, "Pete" <no@xxxxxx> wrote:
>>> >> > >
>>> >> > > <BIG SNIP>
>>> >> > >
>>> >> > > >Wow, some reading to do ! And a lot of it in French too although
>>> >> > > >I
>>> >> don't
>>> >> > > >doubt you'll get the meaning of it all.
>>> >> > > >
>>> >> > > >To do all this, I had to change the ICMP setings in the firewall
>>to
>>> >> allow
>>> >> > > >echo request and echo reply : in and out. I hope this doesn't
>>> >> compromise
>>> >> > > >security !
>>> >> > > >
>>> >> > > >Cheers
>>> >> > > >
>>> >> > > >Peter
>>> >> > >
>>> >> > > Peter,
>>> >> > >
>>> >> > > Not hard to read - I've been reading these CDiag logs for a few
>>> >months,
>>> >> > and I've
>>> >> > > memorised the output. Yours was simple. There were no problems
>>> >> > > at
>>> >all
>>> >> > except
>>> >> > > Peter still has ip problems - it can't ping itself, by name, by
>>> >> > > ip
>>> >> > address, or
>>> >> > > by local loop (127.0.0.1). But it can "net view" itself. This
>>points
>>> >> to
>>> >> > a
>>> >> > > firewall problem, or maybe an LSP / Winsock problem.
>>> >> > >
>>> >> > > But how then can Peter "net view" itself. Better yet, how can
>>> >> > > the
>>> >other
>>> >> > two
>>> >> > > ping and "net view" Peter with no problems?? Frequently this
>>> >> > > sort
>>of
>>> >> > problem
>>> >> > > might be caused by extra protocols - some folks install IPX/SPX
>>> >> > > or
>>> >> > NetBEUI,
>>> >> > > neither of which is routable, and neither is subject to problems
>>> >caused
>>> >> by
>>> >> > > firewalls, though adding protocols just causes more problems.
>>> >> > > Your
>>> >> > protocol
>>> >> > > stacks, shown by browstat, are clean on all 3 computers.
>>> >> > >
>>> >> > > Since both AGNES and D7285M1J can ping Peter with no problem, I
>>would
>>> >> bet
>>> >> > that
>>> >> > > Peter has a problem in its outgoing IP stack.
>>> >> > >
>>> >> > > We will solve this by patience and persistence. And you will
>>> >> > > need
>>> >both.
>>> >> > >
>>> >> > > Let's look for an LSP / Winsock problem first. This won't be
>>> >> > > easy.
>>> >> > > http://support.microsoft.com/?id=318584
>>> >> > > http://support.microsoft.com/?id=811259
>>> >> > >
>>> >> > > If XP RTM or Service Pack 1:
>>> >> > > 1. Backup and delete the following registry keys:
>>> >> > > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
>>> >> > > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
>>> >> > > 2. Reboot.
>>> >> > > 3. Open the network connections folder, right click your network
>>> >> > connection, and
>>> >> > > click Properties.
>>> >> > > 4. Click Install | Protocol | Add.
>>> >> > > 5. Click "Have Disk...", type "\windows\inf" in the box, and
>>> >> > > click
>>> >OK.
>>> >> > > 6. Click "Internet Protocol (TCP/IP)", then click OK.
>>> >> > > 7. Reboot.
>>> >> > >
>>> >> > > If XP SP2:
>>> >> > > 1. Start - Run - "cmd".
>>> >> > > 2. Type "netsh winsock reset catalog" into the command window.
>>> >> > >
>>> >> > > Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
>>> >> > > <http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
>>> >> > > <http://www.spychecker.com/program/winsockxpfix.html> a shot.
>>> >> > >
>>> >> > > If no help yet, reset TCP/IP.
>>> >> > > http://support.microsoft.com/?id=299357
>>> >> > >
>>> >> > > Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into
>>the
>>> >> > command
>>> >> > > window.
>>> >> > >
>>> >> > > The problem with repairing LSP / Winsock is that it will
>>> >> > > frequently
>>> >> reset
>>> >> > and
>>> >> > > remove all non-Microsoft components. You may end up re
>>> >> > > installing
>>the
>>> >> > firewall
>>> >> > > software. Maybe you should un install it first. Fortunately,
>>Peter
>>> >is
>>> >> > behind
>>> >> > > Agnes (Agnes is running ICF / ICS IIRC, and effectively Agnes is
>>> >> > > a
>>> >> > software
>>> >> > > based NAT router. So Peter is safe.
>>> >> > >
>>> >> > > --
>>> >> > > Cheers,
>>> >> > > Chuck
>>> >> > > http://nitecruzr.blogspot.com/
>>> >> > > Paranoia is not necessarily a bad thing - it comes from
>>> >> > > experience.
>>> >> > > My email is AT DOT
>>> >> > > actual address pchuck sonic net.
>>> >> >
>>> >> > Thanks Chuck,
>>> >> >
>>> >> > I did this late last night and I was a bit bog-eyed. "Peter", which
>>is
>>> >the
>>> >> > XP Home SP2 laptop has no problems seeing the other two computers -
>>it
>>> >can
>>> >> > see and browse both. The problem is with the XP Pro SP2 host
>>> >> > "Agnes"
>>> >which
>>> >> > can see the old "Peter" laptop but cannot see the new "D7285M1J New
>>> >Dell"
>>> >> > laptop in my network places. Perhaps when I ran cdiag on the old
>>laptop
>>> >> last
>>> >> > night, I incorrecly "released" the ICMP settings - I'll have a look
>>this
>>> >> > evening.
>>> >> >
>>> >> > I can uninstal the firewall no problem on the old laptop - all I
>>> >> > have
>>to
>>> >> is
>>> >> > save the config. file. But do you think the proble is really with
>>> >> > the
>>> >old
>>> >> > laptop ?
>>> >> >
>>> >> > Cheers
>>> >> >
>>> >> > Peter
>>> >>
>>> >> oh, and another thing - I notice that the various fxes you suggest
>>> >> are
>>> >about
>>> >> internet connectivity. But I don't have a problem connecting the the
>>> >'net -
>>> >> my problem is solely with the LAN. Could they also fix this ? Do I
>>> >> run
>>the
>>> >> fixes on each computer or just on the old laptop ?
>>> >>
>>> >> Cheers
>>> >>
>>> >> Pete
>>> >>
>>> >>
>>> >
>>> >Hmm, thinking again, I recall that when I initially installed the
>>> >network
>>on
>>> >the new laptop last week, I had a couple of .dll error messages
>>> >onscreen
>>> >before rebooting.. Can't remember what they were though...
>>> >
>>> >Cheers
>>> >
>>> >Pete
>>>
>>> Pete,
>>>
>>> The "new laptop" being Peter? That's where the tests point as the first
>>problem
>>> to be solved. By "installing the network" do you mean the network setup
>>wizard?
>>> Try running it again, and see exactly what error you're getting. Then
>>we'll dig
>>> deeper.
>>>
>>
>>Chuck,
>>
>>No, the new Dell laptop is "D7285M1J", also known as "New Dell". That was
>>the first test and I see there weren't any problems. The last test was on
>>"Peter" which is my old XP Home laptop, hence the name. This laptop can
>>see
>>the other computers in "My Network Places" and browse their files. The new
>>Dell laptop can as well. Its the XP Pro SP2 desktop "Agnes", which can't
>>see
>>the new Dell in "My Network Places". I think the Ping problem on the old
>>laptop could have been caused by me not fully allowing echo request in/out
>>and allow indentification in/out on the ICMP settings in the firewall.
>>I'll
>>check tonight.
>>
>>By repeatedly running the network wizard, could I not be causing other
>>problems?
>>
>>Cheers
>>
>>Peter
>
> Pete,
>
> What firewall are you talking about when you "had to change the ICMP
> settings in
> the firewall to allow echo request and echo reply : in and out"? Windows
> Firewall, by definition, allows ICMP when you enable the File and Printer
> Sharing exception.
>
> Then back to "the XP Pro SP2 host "Agnes" which can see the old "Peter"
> laptop
> but cannot see the new "D7285M1J New Dell" laptop in my network places".
> If
> restrictanonymous on D7285M1J is set properly, this is probably caused by
> a
> firewall, or whatever was causing the "couple of .dll error messages" when
> running network setup. Anyway, if the network on D7285M1J is a problem,
> you'll
> have to rerun the wizard. And note what the errors are.
>
> WRT the firewall, you have a wired LAN, so everything on the LAN (ie
> D7285M1J
> and Peter) is protected by Agnes, which is running a NAT router (ICS). So
> except for not being protected from Agnes and Peter, if you un install the
> firewall on D7285M1J, it's still safe for the time being.
>
> --
Hi Chuck,

Here I am again ! I'm using Outpost Agnitum Pro firewall. I've stopped the
firewall on my machine and have re-run the wizard and have re-enabled file
and printer sharing. No joy. 1) The new laptop can still see all the my
network places and can happily browse everyone's documents 2) The XP Pro
desktop, and host (Agnes) can see only the new Dell in the workgroup but can
see and browse the old laptop (Peter) in my network places and 3) the old
laptop can see and browse everyone. I've just ran cdiag.cmd on the old
laptop and all pings work. No error messages. There were no errors when I
ran the network wizard. The browser service is still disabled on the new
laptop. Should I enable it. ? Should I run the fixes you suggested in your
earlier posts ?

The answer is probably staring me in the face. What to do, a system restore
and start from scratch ?

Cheers

Pete


.

Relevant Pages

  • Re: New Printer problem--Help please!
    ... I was able to successfully turn off all firewalls on the laptop, and I believe I also was successful with turning off all firewalls, virus protection, etc on the desktop. ... I have re-set up the network using the home network wizard. ... Following the suggestion I found elsewhere, I set up the network "wrong" (chose incorrect connection method), then set it up again "right". ... the presence of the Symantec VPN driver raises the possibility that the laptop has a Symantec firewall installed. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Printer sharing
    ... Then I have a laptop which connects wirelessly to the router. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ... If you need Pro's ability to set fine-grained permissions, turn off Simple File Sharing and create identical user accounts/passwords on all computers. ...
    (microsoft.public.windowsxp.general)
  • Re: simple solution!
    ... >To filter network access, use a software or hardware ... Sygate is a software firewall that will let you ... laptop a static IP ...
    (microsoft.public.security)
  • Re: File sharing - why is it so difficult?
    ... I am having the same file sharing symptoms as lots of other people though the usual solution of switching off firewalls, enabling Netbios or starting programmes sevices folder. ... I also have a laptop also running windows XP but running the free AVG anti-virus software. ... The strange thing is the laptop can ping the PC once the firewall has been turned off but it can't access any files through windows. ... They are both part of the same workgroup and if you view that workgroup in network places on the PC you can see the laptop and on the laptop you can only see the laptop. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Simple networking?
    ... New laptop using XP Media Centre/SP2. ... I have turned off XP firewall on both since I'm using Zone ... Run the Network Setup Wizard on both computers, ... Simple File Sharing and create identical user ...
    (microsoft.public.windowsxp.general)