Loosing network neighborhood when connecting network to corporate LAN

Greetings: A few weeks ago, I was called down to our
production floor where we have about 150 Windows 2000
professional systems and 100 Windows 98 computers sharing
the VLAN. For some reason, the windows 98 machines can no
longer see each other in network neighborhood. I have
these loaded.
1) Client for Microsoft Networking
2) 3Com adapter
3) TCPIP
4) File and print sharing.

I'm not logging into a domain.
The workgroup for the windows 98 systems is "Basler"
The workgroup for the 2000 systems is "Synquest"

Funny thing:
three PC's in my office are on a shared hub and conected
into my core switch. If I disconnect the cross over cable
between my core switch and this hub, and reboot my 3 PC's
running Windows 98, I will see these systems in network
neighborhood.

Once I connect up this hub again to my core, where the
rest of my 97 Windows 98 machines are, I cannot browse
network neighborhood. I'm asked to check the help index.

I've placed a sniffer on the lone and I see many requests
for a backup browser list, forced announcement requests,
and even an elected local master.

ANy ideas beside what's on the Microsoft knowledge base?
These don't look like the solutions.

Regards
Jeff


Jeff Krawczyk

Hi There

I have no answer for you but I have a similar situation where one
workgroup on a lan will basically disconnect and everyone disconects from
network neighbourhoud in that work group but everyone else in other groups
are fine. I am wondering if it is a browse master issue. I was wondering
also if you could tell me what sniffer you use to see who is the browse
master, backup and announcements being made?? I haven't run into this before
so I have no idea of how to see the requests being made. Maybe I can work
through my problems and help with yours along the way.

Thanks

Chris




"Jeff Krawczyk" <(E-Mail Removed)> wrote in message
news:191b801c41c1f$0f6e7e80$(E-Mail Removed)...
> Greetings: A few weeks ago, I was called down to our
> production floor where we have about 150 Windows 2000
> professional systems and 100 Windows 98 computers sharing
> the VLAN. For some reason, the windows 98 machines can no
> longer see each other in network neighborhood. I have
> these loaded.
> 1) Client for Microsoft Networking
> 2) 3Com adapter
> 3) TCPIP
> 4) File and print sharing.
>
> I'm not logging into a domain.
> The workgroup for the windows 98 systems is "Basler"
> The workgroup for the 2000 systems is "Synquest"
>
> Funny thing:
> three PC's in my office are on a shared hub and conected
> into my core switch. If I disconnect the cross over cable
> between my core switch and this hub, and reboot my 3 PC's
> running Windows 98, I will see these systems in network
> neighborhood.
>
> Once I connect up this hub again to my core, where the
> rest of my 97 Windows 98 machines are, I cannot browse
> network neighborhood. I'm asked to check the help index.
>
> I've placed a sniffer on the lone and I see many requests
> for a backup browser list, forced announcement requests,
> and even an elected local master.
>
> ANy ideas beside what's on the Microsoft knowledge base?
> These don't look like the solutions.
>
> Regards
> Jeff

Chris,

I'll let you know what I find. The Sniffer I used is
called NetXRay. I've bought this 7 years ago and runs
under Windows 5/95. However, there are a ton of evaluation
sniffers (packet and protocol analyzers) out there, such
as Ethereal. Seek and you shall find!

Regards
jeff
>-----Original Message-----
>Hi There
>
> I have no answer for you but I have a similar
situation where one
>workgroup on a lan will basically disconnect and everyone
disconects from
>network neighbourhoud in that work group but everyone
else in other groups
>are fine. I am wondering if it is a browse master issue.
I was wondering
>also if you could tell me what sniffer you use to see who
is the browse
>master, backup and announcements being made?? I haven't
run into this before
>so I have no idea of how to see the requests being made.
Maybe I can work
>through my problems and help with yours along the way.
>
>Thanks
>
>Chris
>
>
>
>
>"Jeff Krawczyk" <(E-Mail Removed)> wrote in
message
>news:191b801c41c1f$0f6e7e80$(E-Mail Removed)...
>> Greetings: A few weeks ago, I was called down to our
>> production floor where we have about 150 Windows 2000
>> professional systems and 100 Windows 98 computers
sharing
>> the VLAN. For some reason, the windows 98 machines can
no
>> longer see each other in network neighborhood. I have
>> these loaded.
>> 1) Client for Microsoft Networking
>> 2) 3Com adapter
>> 3) TCPIP
>> 4) File and print sharing.
>>
>> I'm not logging into a domain.
>> The workgroup for the windows 98 systems is "Basler"
>> The workgroup for the 2000 systems is "Synquest"
>>
>> Funny thing:
>> three PC's in my office are on a shared hub and conected
>> into my core switch. If I disconnect the cross over
cable
>> between my core switch and this hub, and reboot my 3
PC's
>> running Windows 98, I will see these systems in network
>> neighborhood.
>>
>> Once I connect up this hub again to my core, where the
>> rest of my 97 Windows 98 machines are, I cannot browse
>> network neighborhood. I'm asked to check the help index.
>>
>> I've placed a sniffer on the lone and I see many
requests
>> for a backup browser list, forced announcement requests,
>> and even an elected local master.
>>
>> ANy ideas beside what's on the Microsoft knowledge base?
>> These don't look like the solutions.
>>
>> Regards
>> Jeff
>
>
>.
>