Re: Windows XP Internet Connection Sharing (ICS)

Sharon:

Thanks for the helpful tips and the links. The workgroup is already setup
and was actually working fine. I have setup a few of those. This is my
first time using ICS; normally I use a router with built-in hub ports or a
switch/router combination so that all workstations connect to a common
gateway.


I was tempted to use a static IP address for the "client", but was not sure
if it would adversely effect the process.

Thanks again.

--
weyde_one


"Sharon F" wrote:

> On Wed, 15 Jun 2005 13:00:07 -0700, Weyde_one wrote:
>
> > Thanks for the tip. I read at least two versions of instructions for
> > configuring ICS. Each set of instructions specifies that the "client"
> > workstation(s) should be configured to obtain an IP addres and DNS server
> > address automatically.
> >
> > On the first day I setup ICS, I initially configured both the ICS "host"
> > and the client to obtain an IP addresses automatically. This configuration
> > did not work well, as the "client" was assigned a random IP address that was
> > out of the valid range of the ICS"host". I subsequently configured the
> > static IP address 192.168.0.1 and a mask of 255.255.255.0 on the "host'" and
> > left the "client" configured to receive its information automatically. This
> > configuration allowed the workstations to work well together, sharing the
> > Internet connection as well as a local printer.
> >
> > Today, after both workstations were restarted, the "client" workstation
> > again was assigned the random IP address and subnet mask. Now the ICS
> > workstation cannot communicate with the "client", nor can they share the
> > printer, or the Internet connection.
> >
> > By the way, on the first day of connecting them, I did restart both
> > computers several times to verify that could share the Internet connection as
> > well as the local printer.
>
> The "host" computer has to be running for ICS to work. You'll see a 169.*
> address when the client computer fails to obtain an IP number in the
> correct range from the "host." This is an APIPA address or "public IP."
> The cause of the failure can vary. Even if you have everything setup
> correctly, the timing can be off a hair between the various systems when
> the client is seeking its IP and there goes your dynamically assigned
> address. You can restart the client system and hope it succeeds (sometimes
> works since many processes remain in memory for a restart instead of
> loading fresh). Or perform an ipconfig /release and /renew from a command
> prompt window. Or, and probably the simplest, assign static IPs to the
> "clients."
>
> ICS is an optional part of a workgroup structure. Since you are sharing a
> printer, is it possible that there are other resources that you want
> shared? I'm thinking that you may want to delve a little deeper into
> getting a workgroup setup (one that includes ICS).
>
> If all machines in the workgroup run XP, the network wizard is handy and
> effective. It supposedly works well with mixed networks but I find that
> it's better to set those manually instead of using the wizard. There are
> several articles in the Windows XP Expert Zone on setting up a home network
> (including ICS): http://www.microsoft.com/windowsxp/expertzone/default.mspx
>
> I also find the home networking articles at www.practicallynetworked.com to
> be helpful too.
>
> --
> Sharon F
> MS-MVP ~ Windows Shell/User
>
.

Relevant Pages

  • Re: Adding a domaind laptop to my home network
    ... I tried setting up my home network with the same name as my laptop ... Whilst the network setup wizard completes ok, ... but I can alter the home pc workgroup name. ...
    (microsoft.public.windowsxp.network_web)
  • Re: ICS, and file transfer between 2 local computer
    ... Network Configuration ... Workgroup - it is better to setup a same workgroup on all computers ... Client for MS Network - must be enabled to access the network ...
    (microsoft.public.windowsxp.network_web)
  • Client Computers & Users
    ... currently running in Workgroup, with assigned IP Addresses. ... Could someone explain the separation/dependance of setting up Client ... If we setup a Client and then setup its User, ...
    (microsoft.public.windows.server.sbs)
  • Re: WINS server
    ... > workgroup name of OFFICE but running the AD client, ... Each server NIC is connected to it's own ... >>> on their subnet, just move it across another subnet instead. ...
    (microsoft.public.windows.server.networking)
  • 2PCs/crossover problems
    ... LAN/internet setup between just 2 computers at home. ... They mention network adapters, external and internal, ... The next hurdle is to solve the problem that the Client ... Connection" "manually" "using a broadband connection that ...
    (microsoft.public.windowsxp.network_web)