Workgroup Mess

Assistance PLEASE!
I have workgroups that have workstations (all 98) that
disappear at times and then reappear later. On some, when
I try to enter Network Neighborhood they can't access the
network and gives me a red X error message. If I try again
on the same machine a little later, there's no problem.
There are about 32 stations all together.
In the beginning, (not knowing that i was NOT suppose to
do this) I included them ALL in the same workgroup -
that's when these occurances started happening. SO I
thought that once they were put into groups of ten,
everything would be OK. But these things are still
happening.

Is this a lingering effect from me messing up in the
beginning or does this sound like something that's not
related at all.
These are all older IBM's (P2's) that are accessing the
Internet in a wireless LAN using Cisco series 350 cards.
Could someone tell me what it is that I need to do to
correct this mess that I've created. THANX N
ADVANCE Wayne B.

PS- There are two that have lost the ability to get the
internet. Everything is fine in D Manager, cards are
firmly in place on the motherboard and both are very short
distances from their respective access points. BOTH -
cannot ping out nor be pinged, BUT can ping themselves.

In article <03aa01c39e74$49c29630$(E-Mail Removed)>, "Wayne B."
<(E-Mail Removed)> wrote:
> Assistance PLEASE!
>I have workgroups that have workstations (all 98) that
>disappear at times and then reappear later. On some, when
>I try to enter Network Neighborhood they can't access the
>network and gives me a red X error message. If I try again
>on the same machine a little later, there's no problem.
>There are about 32 stations all together.
> In the beginning, (not knowing that i was NOT suppose to
>do this) I included them ALL in the same workgroup -
>that's when these occurances started happening. SO I
>thought that once they were put into groups of ten,
>everything would be OK. But these things are still
>happening.
>
>Is this a lingering effect from me messing up in the
>beginning or does this sound like something that's not
>related at all.
>These are all older IBM's (P2's) that are accessing the
>Internet in a wireless LAN using Cisco series 350 cards.
>Could someone tell me what it is that I need to do to
>correct this mess that I've created. THANX N
>ADVANCE Wayne B.
>
> PS- There are two that have lost the ability to get the
>internet. Everything is fine in D Manager, cards are
>firmly in place on the motherboard and both are very short
>distances from their respective access points. BOTH -
>cannot ping out nor be pinged, BUT can ping themselves.

Network Neighborhood and the network browsing function that it depends
on are trouble-prone when there are as many computers as you have. It
can take several minutes after a computer joins or leaves the network
for everything to settle down and act normally.

When Network Neighborhood is acting up, you can access another
computer directly by typing its name in the Start | Run box preceded
by two backslash characters:

\\computer
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm