Re: XP Home and local area network

headch_at_bellsouth.net
Date: 12/21/04 

Date: Tue, 21 Dec 2004 17:59:39 GMT

Thanks Carey and Chuck,

I am glad to give anything a shot once at least. I looked over the patch
and am having some difficulty deciding what the purpose of the patch is.
What is it meant to achieve? And from the notes I sent last night do you
get a feel for why machines that previously shared files no longer do. Why
does the browstat not allow an election if the services are running
correctly?

Had I been able on the 1st visit to locate a handy XP CD I'd have installed
NetBEUI and gone on my way. Do you think this might bypass the problem?

I could not help but think the problem ultimately came about when 2 machines
that had previously found one another via a host XP box no longer had the
host box available. I mentioned in an earlier post I'd been able to ping an
IP, that machine (the one I could ping) is the new box, the one that had not
been in the workgroup before. All the systems are running XP Home-SP2.

In answer to your question Chuck about my experience in the registry I do
have a reasonable amount of experience there and in most aspects of the
system hardware and software, and a fair amount of training in Microsoft OS
back as far as DOS 3.0 and rarely run across one I can't effectively
troubleshoot. I certainly did not expect this to be more than about a 30-40
minute wireless router setup and a quick sharing of resources and connecting
a printer. Now here I am 5 days later with some amount of egg dripping off
my chin.

>From looking over the text in the reg patch Carey is supplying it appears
that the anonymous access is corrected but I am unclear about the purpose of
the rest of it.
-------------------------------------------------------------------------
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]

"NodeType"=-
"DhcpNodeType"=-
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]

"restrictanonymous"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"IRPStackSize"=-
--------------------------------------------------------------------------
If when I install the patch on each box I still don't get the desired
results would it be a fair assumption that I might be better off
uninstalling the network completely and setting it up from scratch? In 98SE
environments this has worked wonders in the past. Is XP as cooperative or
will it simply put everything back like it was?

Thanks again
Chris

Relevant Pages

  • Re: Atyfb questions and issues
    ... The purpose of this patch is to get the xlinit working for non-i386 ... machines, such as the MIPS processor board I'm currently working with. ... In the 2.4 kernel I'm using as a reference with the 'xlinit' code ...
    (Linux-Kernel)
  • Automatically patching machine with hotfix KB824146 using mbsafu.
    ... I didn't want to spend as many hours patching machines with KB824146 exploit ... Mbsafu is an automatic remote patching tool that applies Security updates ... Download and install mbsa. ... Setup a network share with full privileges for the account you will patch ...
    (NT-Bugtraq)
  • Re: Event ID 6161 for HP 6840
    ... patch related to an exposure via the print spooler service. ... download which offers the option of a local port. ... >> There were no problems with the install and the printer works find so long ... >> 3) All machines on the network can connect to the printer via Internet ...
    (microsoft.public.windowsxp.print_fax)
  • Re: [fw-wiz] terminal services
    ... >> pointing out the danger of opening extra holes in your firewall. ... >that a VPN is a hole in the firewall, albeit generally a mitigated hole, ... >people didn't patch their machines. ...
    (Firewall-Wizards)
  • Re: 5.3-RELEASE TODO
    ... I haven't tested the last one (memory tuning on 4GB machines) ... * There may be a problem with swapping: ... >> He suggested a patch, but it did not fix the problem. ...
    (freebsd-current)