Cannot access workgroup

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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 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?
Click to expand...

That's one symptom of a problem that has exhibited many symptoms in the past.
Try these troubleshooting guides, in this order:
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
 
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.
 
I was about to send you an "ignore my last message" note when I saw your
reply to it.

You're right, the security updates had no role in the problem.

This morning I discovered that my Work Group had spontaneously (apparently)
restored itself! I deeply regret that I can't think of what I might
possibly have done to restore it.

I hadn't checked out the status of my Work Group for a couple of days so I
don't even know exactly when it restored itself. I had been doing many
things in the interim to undo problems I created on my computer in the
process of running tests, experiments, and exercises while looking for a
solution to the network problem.

At the moment, the only thing I can think of that might have had a role is
my recent resetting of both IE6>Internet Options>Programs and Internet
Options>Advanced. to "default."

I can't think of what the IE6 could have to do with a file-sharing network,
though.

I will try very hard to recall changes I made in the past few days might
possibly have revived the network and will post any I can think of.
 
I was about to send you an "ignore my last message" note when I saw your
reply to it.

You're right, the security updates had no role in the problem.

This morning I discovered that my Work Group had spontaneously (apparently)
restored itself! I deeply regret that I can't think of what I might
possibly have done to restore it.

I hadn't checked out the status of my Work Group for a couple of days so I
don't even know exactly when it restored itself. I had been doing many
things in the interim to undo problems I created on my computer in the
process of running tests, experiments, and exercises while looking for a
solution to the network problem.

At the moment, the only thing I can think of that might have had a role is
my recent resetting of both IE6>Internet Options>Programs and Internet
Options>Advanced. to "default."

I can't think of what the IE6 could have to do with a file-sharing network,
though.

I will try very hard to recall changes I made in the past few days might
possibly have revived the network and will post any I can think of.
Click to expand...

Joseph,

Did you restart any computers just before your workgroup spontaneously restored
itself? Or did any computers lose contact (even briefly) with the others? What
you're describing is symptomatic of a browser (no I'm not talking about Internet
Explorer) problem.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

I think it's a great pity that you were not able to run browstat. What you
learned might have helped you, and it might have others too. Please reconsider
your earlier decision to give up diagnosing your problem. Help us to help you,
and to help others.
 
:

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.
Click to expand...

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. ;-)
 
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.)
 
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.)
Click to expand...

Joseph,

In tech forums like this one, the serious helpers prefer bottom posting. I work
with maybe a dozen or more different threads like yours at any time, some with
multiple exchanges / day, others multiple days between exchanges. Sometimes the
different details from multiple threads gets confusing, so I've found it a VERY
good idea to intentionally review the history of each thread to prevent making
embarrassing and useless posts.

Reviewing from the top down is way easier, and allows me to help you better.
Sometimes I do that, and the person asking for help figures out how to respond
properly. And, if you leave the trimming (of prior posts) to me, I can trim
details when they become non-relevant. Being able to find details, by scanning
downward, is way easier than having to search thru the thread in another window.
You might find it more productive too - and after all, the object here is to
help you resolve your problem.

You're using Lookout Express though. That's one of the problems of OE, it
encourages folks to top post.
A: Maybe because some people are too annoyed by top-posting.
Q: Why do I not get an answer to my question(s)?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Because it changes the order you read a conversation.
Q: Why is top-posting so annoying?
A: Top-posting!
Q: What is the most annoying thing in newsgroups?

Now you've got 2 threads open, and I keep thinking that your 2 are related in
some way. Having to switch back and forth between the two, to review the
problem, isn't easy. One person with 2 threads is almost as annoying as 2
people with one thread (ie hijacked thread).
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#Hijacking>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#Hijacking
 
Thanks you. I now understand why you respond at the bottom. You've
convinced me to return to using Google for UseNets..

Sorry about the two threads. And, I hadn't intended to 'hijack'
greyboomer's thread, if that's what your referring to. This will be my
last posting here unless greyboomer returns with news or an issue.

The reason I opened more that one thread under my own name is that the
nature of my networking problem changed dramatically. MY File-sharing
network spontaneously reappeared just after I booted up two computers
in few mornings ago (first the laptop then desktop.) I have no idea
why.

But I was thrilled until I discovered the new problem: I can view, side
by side, only one of my old shared folders, so I started a thread on
that issue. My hope was that I could get my systems to work together
again so as not to risk losing ground before going back to the browser
issue.

Cheers..
 
Yes, I have run IPConfig and Browstat sta on both machines, and I have run
cdiag but it's not putting the output into a notepad file for some reason so
I have not been able to post it here.

Browstat Sta on the machine which has unrestriced workgroup access says the
master browser is running on the other machine. Browstat sta on the second
machine show master browser problem and resorts to the back-up browser.

I am not particulary good at DOS code so I really don't know for sure how to
get those exact ourputs into a notepad file for posting here.

The only thing different other than IPaddress on the IPCONFIG output is the
node type, Hybrid on the good machine and unknown on the bad one. Also the
bad one is showing a shared internet connection on the Network Connections
page. The good machine is not. My Lan connects to the internet through
D-Link 624c (firmware updated) via a Speedstream 5100 DLS modem, all hard
wire.

Additionally, I have reset winsock and TCP/IP on the bad machine.

Greenbean or Tuna & potato chip casserole? :)
 
Yes, I have run IPConfig and Browstat sta on both machines, and I have run
cdiag but it's not putting the output into a notepad file for some reason so
I have not been able to post it here.

Browstat Sta on the machine which has unrestriced workgroup access says the
master browser is running on the other machine. Browstat sta on the second
machine show master browser problem and resorts to the back-up browser.

I am not particulary good at DOS code so I really don't know for sure how to
get those exact ourputs into a notepad file for posting here.

The only thing different other than IPaddress on the IPCONFIG output is the
node type, Hybrid on the good machine and unknown on the bad one. Also the
bad one is showing a shared internet connection on the Network Connections
page. The good machine is not. My Lan connects to the internet through
D-Link 624c (firmware updated) via a Speedstream 5100 DLS modem, all hard
wire.

Additionally, I have reset winsock and TCP/IP on the bad machine.

Greenbean or Tuna & potato chip casserole? :)
Click to expand...

So whadda wanna do? Maybe you post the complete and unedited output "browstat
status" and "ipconfig /all" from each computer, as a start? Just maybe there's
something in there that you didn't see? Better than me trying to read your
mind.

Or you could post the CDiag code that you tried to run.

And either casserole sounds scrumptious. :-)
 
This is the cdiag code I ran:

Start CDiag Base Code@echo offset FullTarget1=bob 192.168.0.150 set
FullTarget2= gsb 192.168.0.151 set FullTarget3=set FullTarget4=set
FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%set
FullTargets=%FullTargets% 127.0.0.1set PingTargets=www.yahoo.com 66.94.230.32
Set Version=V1.33@echo CDiagnosis %Version% >c:\cdiag.txt@echo Start
diagnosis for %computername% >>c:\cdiag.txt@echo. >>c:\cdiag.txt@echo
Enumerate Shares >>c:\cdiag.txt@echo. >>c:\cdiag.txtnet share
The machine which has workgroup access is bob, the bad machine is gsb.
 
Back
Top