Mischief in My Network Places

Hi Everyone -

I have a client with a network that seems to hold on to workgroup and domain
names it sees from other computers on the network. For instance, I brought
my laptop in, which belongs to a domain called DOMAIN-A and plugged it into
the network at my client's site over a month ago for just the one day.
Today, I am back and I can still see DOMAIN-A listed when I browse. If I try
to click on it, it says "DOMAIN-A is not accessible. The network path could
not be found." I am running WINS and DNS, but cannot figure out why this
name and others are keeping a residual presence on this network. This is not
the only instance. I have other engineers from my company that service this
client and now I am starting to see our other client networks listed in My
Network Places from when they plugged their laptops in! This network has
multiple sites connected via Cisco PIX VPNs and we are using the
hub-and-spoke WINS architecture, with the site where I am being the hub.

Thanks.

Open the WINS database and sort by name then delete
all instances of the this domain name. There should be
a 1b entry which is producing the domain/workgroup
name you are seeing. Make sure you remove the name
from the hub and all spokes. Next wait at least 51 minutes
for a full browse cycle in order for the name to disappear.
"ARM123" <(E-Mail Removed)> wrote in message news:
> Hi Everyone -
>
> I have a client with a network that seems to hold on to workgroup and
domain
> names it sees from other computers on the network. For instance, I
brought
> my laptop in, which belongs to a domain called DOMAIN-A and plugged it
into
> the network at my client's site over a month ago for just the one day.
> Today, I am back and I can still see DOMAIN-A listed when I browse. If
I try
> to click on it, it says "DOMAIN-A is not accessible. The network path
could
> not be found." I am running WINS and DNS, but cannot figure out why
this
> name and others are keeping a residual presence on this network. This
is not
> the only instance. I have other engineers from my company that service
this
> client and now I am starting to see our other client networks listed
in My
> Network Places from when they plugged their laptops in! This network
has
> multiple sites connected via Cisco PIX VPNs and we are using the
> hub-and-spoke WINS architecture, with the site where I am being the
hub.
>
> Thanks.
>
>

Thanks for the reply. From the WINS Manager on a W2K box, how do I open the
database and sort by name? Is that like right-clicking on Active
Registration and selecting Find?

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:%(E-Mail Removed)...
> Open the WINS database and sort by name then delete
> all instances of the this domain name. There should be
> a 1b entry which is producing the domain/workgroup
> name you are seeing. Make sure you remove the name
> from the hub and all spokes. Next wait at least 51 minutes
> for a full browse cycle in order for the name to disappear.
> "ARM123" <(E-Mail Removed)> wrote in message news:
> > Hi Everyone -
> >
> > I have a client with a network that seems to hold on to workgroup and
> domain
> > names it sees from other computers on the network. For instance, I
> brought
> > my laptop in, which belongs to a domain called DOMAIN-A and plugged it
> into
> > the network at my client's site over a month ago for just the one day.
> > Today, I am back and I can still see DOMAIN-A listed when I browse. If
> I try
> > to click on it, it says "DOMAIN-A is not accessible. The network path
> could
> > not be found." I am running WINS and DNS, but cannot figure out why
> this
> > name and others are keeping a residual presence on this network. This
> is not
> > the only instance. I have other engineers from my company that service
> this
> > client and now I am starting to see our other client networks listed
> in My
> > Network Places from when they plugged their laptops in! This network
> has
> > multiple sites connected via Cisco PIX VPNs and we are using the
> > hub-and-spoke WINS architecture, with the site where I am being the
> hub.
> >
> > Thanks.
> >
> >
>
>