I intend to look into that, but first I need to get other things I fouled up
back to "normal" again -- i.e.., see my posting of "Problem Comparing Shared
Files." I do have to get some work done in between tests and experiments.
You probably have a good reason for it, but when you respond and the bottom
instead the top of a posting, it makes it clumsy for the reader to respond.
Not so much criticizing as wondering why you do that. After passing the age
of 75, people sort of feel they earned the privilege of making comments
like this.)
"Chuck" <none@example.net> wrote in message
news:s47vm15b9l4h0un2dqqfpe20hma93q2o73@4ax.com...
> On Mon, 7 Nov 2005 00:44:07 -0800, "greyboomer"
> <greyboomer@discussions.microsoft.com> wrote:
>
>>"Joseph Carrier" wrote:
>>
>
>>> "greyboomer" <greyboomer@discussions.microsoft.com> wrote in message
>>> news:2343F314-CB65-47FB-90E7-9299A0BFCBE0@microsoft.com...
>>> >I have a 2 computer workgroup through a D-Link DI 624c router. All was
>>> >just
>>> > fine untill about 2 weeks ago when one machine suddenly stopped being
>>> > able
>>> > to
>>> > access the other in the workgroup. The WAN access never changed and
>>> > it
>>> > works
>>> > fine.
>>> > I have been through every diag. tool and technique I can find and
>>> > everything
>>> > reports back that I should not be having this problem, however I am.
>>> > The
>>> > only flaw I can find is when I use the Net View command. It searches
>>> > for
>>> > a
>>> > while and then reports back with a 121 error (semaphore). Anybody
>>> > have a
>>> > clue for me on this one?
>>>
>>>
>>> I can't offer much help, but am intrigued that we experienced almost
>>> the
>>> exact same thing at about the same time. There are some differences: I
>>> use
>>> XP (home edition) and I use a NetGear WGR614 v4 router.
>>>
>>> I don't know if these are different: my connection to the router is
>>> cable
>>> for the desktop and wireless for two laptops; the two laptops continue
>>> to
>>> see each other but so not see the desktop, and vice versa.)
>>>
>>> I can't say I've tried every diagnostic and technique, but I did try a
>>> lot
>>> of them without luck.
>>>
>>> Could our common problem have anything to do with Window XP Security
>>> Updates
>>> that were installed about two weeks ago? (I'm far from being a
>>> technician,
>>> so I don't know if such a thing is possible.)
>>>
>>> Six security updates were downloaded and installed on my desktop machine
>>> On
>>> October 16:
>>>
>>> KB896688 (a previous attempt to download this had failed on failed
>>> on
>>> October 14)
>>> KB900725
>>> KB905749
>>> KB905414
>>> KB901017
>>> KB902400
>>>
>>> Did you install one or more of these just before you lost your workgroup
>>> access?
>>>
>>>
>>I Thought that same thing at first about the Windows updates so I backed
>>them
>>all out and uninstalled and reinstalled Service Pac 2 all to no avail.
>>Both
>>my machines are hardwired to the router. I have uninstalled and
>>reinstalled
>>the network card with a new set of drivers downloaded from Dell, updated
>>the
>>firmware on the router, and said a novena to the god of Windows, and
>>worked
>>my way through PChucks sheets and nothing works. What I do know is
>>something
>>keeps resetting my node to unknown from Hybrid in my resistry and the Net
>>commands show the machine is not part of the workgroup.
>>
>>I continue to suspect it was something in the updates but I am baffled why
>>it only effected that one machine. I have installed all the updates on
>>the
>>other machine and it still works like a charm.
>>
>>If I stumble on the answer, I will be sure to post it here.
>
> Having worked your way thru PChucks sheets, did you run "browstat status"
> and
> "ipconfig /all" from each computer? Try and diagnose the problem, and
> help
> others to help you. If you're Catholic, maybe a novena will help you.
> I'm
> Methodist, so a casserole might help me. ;-)
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My email is AT DOT
> actual address pchuck mvps org.