>I have four systems that I'd like to be able to share information between. 
>Not using a "server" approach, but a "workgroup" approach.  However, there is
>a twist.
>
>Specifically:
>1) Using a four port router to permit internet access for three systems.
>2) Using internet sharing on one PC to permit internet access for the fourth
>system (don't have location of 4th PC wired, with no plans to wire it or use
>wireless.)
>
>Now, the problem:
>1) Three of the systems can map easily to the shared folders of each other
>and the primary home system (i.e. \\<sysName>\<sharedFolder>).
>2) The fourth system (connected to 2nd eithernet card on third system, and
>it using internet sharing) cannot use the same method to access the primary
>system.  It must use the IP address to map to the folder (i.e.
>\\<ipAddr>\<sharedFolder>).
>3) The IP address is not always consistant after powerdown/restart, so the
>fixed map of the fourth system must be reentered (at times.)
>4) All firewalls are turned off for all systems.
>
>Question:
>How can I have the "network" (workgroup) recognize the fourth system
>(although it is directly connected to the third system using an eithernet
>patch cable) to permit sharing of information with that system?
>
>Thank you for your help.

"Chuck" wrote:

> On Tue, 2 Jan 2007 09:08:00 -0800, Jim <J**@discussions.microsoft.com> wrote:
>
> >I have four systems that I'd like to be able to share information between. 
> >Not using a "server" approach, but a "workgroup" approach.  However, there is
> >a twist.
> >
> >Specifically:
> >1) Using a four port router to permit internet access for three systems.
> >2) Using internet sharing on one PC to permit internet access for the fourth
> >system (don't have location of 4th PC wired, with no plans to wire it or use
> >wireless.)
> >
> >Now, the problem:
> >1) Three of the systems can map easily to the shared folders of each other
> >and the primary home system (i.e. \\<sysName>\<sharedFolder>).
> >2) The fourth system (connected to 2nd eithernet card on third system, and
> >it using internet sharing) cannot use the same method to access the primary
> >system.  It must use the IP address to map to the folder (i.e.
> >\\<ipAddr>\<sharedFolder>).
> >3) The IP address is not always consistant after powerdown/restart, so the
> >fixed map of the fourth system must be reentered (at times.)
> >4) All firewalls are turned off for all systems.
> >
> >Question:
> >How can I have the "network" (workgroup) recognize the fourth system
> >(although it is directly connected to the third system using an eithernet
> >patch cable) to permit sharing of information with that system?
> >
> >Thank you for your help.
>
> If the fourth computer is connected, thru the third computer, as an ICS client,
> it's on a separate subnet and broadcast domain.  So it will never get named
> access to the other computers.  Similarly, the other computers won't be able to
> access it.
>
> ICS is a poor solution for bridging networks.  See if you can make a bridge out
> of the third computer, instead of an ICS server.
> <http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html>
> http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html
>
> Normally, you wouldn't setup a bridge.  My documentation here might give you the
> right clues to make yours work, though.
> <http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge>
> http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge
>
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My        email         is          AT         DOT
>    actual       address    pchuck       mvps        org.
>

>"Chuck" wrote:
>
>> On Tue, 2 Jan 2007 09:08:00 -0800, Jim <J**@discussions.microsoft.com> wrote:
>>
>> >I have four systems that I'd like to be able to share information between. 
>> >Not using a "server" approach, but a "workgroup" approach.  However, there is
>> >a twist.
>> >
>> >Specifically:
>> >1) Using a four port router to permit internet access for three systems.
>> >2) Using internet sharing on one PC to permit internet access for the fourth
>> >system (don't have location of 4th PC wired, with no plans to wire it or use
>> >wireless.)
>> >
>> >Now, the problem:
>> >1) Three of the systems can map easily to the shared folders of each other
>> >and the primary home system (i.e. \\<sysName>\<sharedFolder>).
>> >2) The fourth system (connected to 2nd eithernet card on third system, and
>> >it using internet sharing) cannot use the same method to access the primary
>> >system.  It must use the IP address to map to the folder (i.e.
>> >\\<ipAddr>\<sharedFolder>).
>> >3) The IP address is not always consistant after powerdown/restart, so the
>> >fixed map of the fourth system must be reentered (at times.)
>> >4) All firewalls are turned off for all systems.
>> >
>> >Question:
>> >How can I have the "network" (workgroup) recognize the fourth system
>> >(although it is directly connected to the third system using an eithernet
>> >patch cable) to permit sharing of information with that system?
>> >
>> >Thank you for your help.
>>
>> If the fourth computer is connected, thru the third computer, as an ICS client,
>> it's on a separate subnet and broadcast domain.  So it will never get named
>> access to the other computers.  Similarly, the other computers won't be able to
>> access it.
>>
>> ICS is a poor solution for bridging networks.  See if you can make a bridge out
>> of the third computer, instead of an ICS server.
>> <http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html>
>> http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html
>>
>> Normally, you wouldn't setup a bridge.  My documentation here might give you the
>> right clues to make yours work, though.
>> <http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge>
>> http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#Bridge

>Thank you.  Your suggestion was perfect.  I'd forgotten about Bridges, and as
>soon as I'm able, I shall attempt this solution.