Workgroup naming

Hey everyone..
I had setup a small (4) group of systems together to use our T1 line..
I had reset their workgroup name and the old name still shows in the
network group.
Is there a way to get it removed as it then shows the other group (20)
of systems.
Thanks..

Lou

Turn off all computers on the network, then turn them back on one at a time.
Alternatively, wait a few days and the "ghost" workgroup will vanish by
itself.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Lou Farraher" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hey everyone..
> I had setup a small (4) group of systems together to use our T1 line..
> I had reset their workgroup name and the old name still shows in the
> network group.
> Is there a way to get it removed as it then shows the other group (20)
> of systems.
> Thanks..
>
> Lou

I think it might go beyond..
I actually have the systems all in the same range as far as IP
addresses.
The 4 are on the upper scale..in the 200 range..( 192.168.0.200+) so
they can use the T1 line..
I change the IP from 192.168.0.200 to 192.168.1.200 and they loose the
T1..
So I had 4 systems in their own workgroup name and the rest on their
own workgroup name. All within the 192.168.0.+ range..
Now both groups pick up both workgroup names and systems.
I would like to isolate each group from each other. Mask them so to
say.
What would I need to do to hide each group of systems from each other
so not to see drives or other shared resources and still use the T1
for the net?

Thanks again for the help Richard..

On Tue, 4 Oct 2005 17:31:38 -0400, "Richard G. Harper"
<(E-Mail Removed)> wrote:

>Turn off all computers on the network, then turn them back on one at a time.
>Alternatively, wait a few days and the "ghost" workgroup will vanish by
>itself.

Sorry, guess I misunderstood your first post. Let's try again.

What you need is a router to divide computers into different address ranges,
otherwise all workgroups will be able to browse all other workgroups present
on the network. You'd connect the router to the network with the T1 line,
then configure it to provide addresses in the 192.168.1.x range to the
computers that you want isolated from the computers in the 192.168.0.x
address range. Connect the computers you want isolated to the router.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Lou Farraher" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I think it might go beyond..
> I actually have the systems all in the same range as far as IP
> addresses.
> The 4 are on the upper scale..in the 200 range..( 192.168.0.200+) so
> they can use the T1 line..
> I change the IP from 192.168.0.200 to 192.168.1.200 and they loose the
> T1..
> So I had 4 systems in their own workgroup name and the rest on their
> own workgroup name. All within the 192.168.0.+ range..
> Now both groups pick up both workgroup names and systems.
> I would like to isolate each group from each other. Mask them so to
> say.
> What would I need to do to hide each group of systems from each other
> so not to see drives or other shared resources and still use the T1
> for the net?
>
> Thanks again for the help Richard..
>
> On Tue, 4 Oct 2005 17:31:38 -0400, "Richard G. Harper"
> <(E-Mail Removed)> wrote:
>
>>Turn off all computers on the network, then turn them back on one at a
>>time.
>>Alternatively, wait a few days and the "ghost" workgroup will vanish by
>>itself.

Richard G. Harper wrote:
> Sorry, guess I misunderstood your first post. Let's try again.
>
> What you need is a router to divide computers into different address ranges,
> otherwise all workgroups will be able to browse all other workgroups present
> on the network. You'd connect the router to the network with the T1 line,
> then configure it to provide addresses in the 192.168.1.x range to the
> computers that you want isolated from the computers in the 192.168.0.x
> address range. Connect the computers you want isolated to the router.
>
Would that therefore require the static assignments of each
IP address on the router and the computers and not DHCP?

No, DHCP can work across a router when properly configured. Or the DHCP
addressing of the first network can be handled by its current DHCP schema
(whether a server or manually configured) and the hidden part of the network
can get addresses from the new router. Or you could configure all addresses
manually if you'd rather. No big hu-hu in any case.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"HAL" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Richard G. Harper wrote:
>> Sorry, guess I misunderstood your first post. Let's try again.
>>
>> What you need is a router to divide computers into different address
>> ranges, otherwise all workgroups will be able to browse all other
>> workgroups present on the network. You'd connect the router to the
>> network with the T1 line, then configure it to provide addresses in the
>> 192.168.1.x range to the computers that you want isolated from the
>> computers in the 192.168.0.x address range. Connect the computers you
>> want isolated to the router.
>>
> Would that therefore require the static assignments of each IP address on
> the router and the computers and not DHCP?

Richard G. Harper wrote:

> No, DHCP can work across a router when properly configured. Or the DHCP
> addressing of the first network can be handled by its current DHCP schema
> (whether a server or manually configured) and the hidden part of the network
> can get addresses from the new router. Or you could configure all addresses
> manually if you'd rather. No big hu-hu in any case.
>
Thank you. I guess the significant element is that there are
TWO routers involved, each with a separate IP identity
(i.e.: 192-168.XXX.yyy and the other 192.168.AAA.bbb). If
the T1 modem only has one Ethernet port, can the two routers
cascade through the other with the different (class c setup)
IP addresses? Just curious as part of my education, not an
urgent question of need.

On Wed, 5 Oct 2005 19:01:26 -0400, "Richard G. Harper"
<(E-Mail Removed)> wrote:

>No, DHCP can work across a router when properly configured. Or the DHCP
>addressing of the first network can be handled by its current DHCP schema
>(whether a server or manually configured) and the hidden part of the network
>can get addresses from the new router. Or you could configure all addresses
>manually if you'd rather. No big hu-hu in any case.

Ok..so I would need another router for the other 4 systems..
I have each system's IP addresses put in manually..I do not let the
router assign them..
I was hoping to just assign a different IP range for the 4 systems and
setup the gateway with the routers IP address in the TCP/IP setup..
But didn't work that way.
As soon as I assigned the range to the 4 systems..they lost the T1..

Lou

Depending on the class of router you get, some configuration may be
necessary. With consumer-grade routers, router #2 will get the
configuration it needs from router #1 to establish an internet connection
for the computers connected to router #2. With more expensive
business-grade routers you may need to set up a route to allow computers on
router #2 to see and use the internet connection on router #1.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"HAL" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Richard G. Harper wrote:
>
>> No, DHCP can work across a router when properly configured. Or the DHCP
>> addressing of the first network can be handled by its current DHCP schema
>> (whether a server or manually configured) and the hidden part of the
>> network can get addresses from the new router. Or you could configure
>> all addresses manually if you'd rather. No big hu-hu in any case.
>>
> Thank you. I guess the significant element is that there are TWO routers
> involved, each with a separate IP identity (i.e.: 192-168.XXX.yyy and the
> other 192.168.AAA.bbb). If the T1 modem only has one Ethernet port, can
> the two routers cascade through the other with the different (class c
> setup) IP addresses? Just curious as part of my education, not an urgent
> question of need.

Yes, that will happen; and without a router to divide the networks there's
no way to prevent either the loss of the T1 connection or for all computers
to see each other.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"NEO" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Wed, 5 Oct 2005 19:01:26 -0400, "Richard G. Harper"
> <(E-Mail Removed)> wrote:
>
>>No, DHCP can work across a router when properly configured. Or the DHCP
>>addressing of the first network can be handled by its current DHCP schema
>>(whether a server or manually configured) and the hidden part of the
>>network
>>can get addresses from the new router. Or you could configure all
>>addresses
>>manually if you'd rather. No big hu-hu in any case.
>
> Ok..so I would need another router for the other 4 systems..
> I have each system's IP addresses put in manually..I do not let the
> router assign them..
> I was hoping to just assign a different IP range for the 4 systems and
> setup the gateway with the routers IP address in the TCP/IP setup..
> But didn't work that way.
> As soon as I assigned the range to the 4 systems..they lost the T1..
>
> Lou