ICS and static networking problems



Mon
07-10-2005, 01:52 AM
Hi,
I have 4 computers - 3 are brand new Dell XP Pro SP2 and the other W2k. Two
computers are in one room and the other two in another. The computers are
all networked. In one room 2 XP pro machines, one is the ICS host and the
other a client, so is the other room (they are clients). ISDN is used for
internet.
All computers are connecting to the internet through ICS with no problems
there. But I have problems with all computers viewing the host! we cannot
share anything on the host as the other three PC's cannot view it. Even
though they are using it to connect to the internet
I have tried using static IP addressing, to see if it solved the problem and
got no results. I have also tried putting in the hosts and lmhosts the IP
addresses of two machines to test (the host and the client next to it). I
have disabled the firewalls.
I am at the end of the line here because the network seems fine i.e. all
PC's are using the network and the host to get out onto the internet and that
works fine.
Has anyone come across this problem before? is it a corruption in Windows?
the customer is going to wipe out the two PC's, the host and client in one
room, to see if it solves the problem. I've never come across this and
cannot understand why they can communicate via ICS but cannot share files or
printers (the two PC's in the other room are fine) File and Printer sharing
are enabled on all of them. In fact the host can actually view printers from
the other room and print to them but the other computers cannot see the
printers or shared items on the host!
After I left the customers site, something hit me like lightning. The host
had a 192.168.1.0 address, (while using APIPA), and the others had 169....
addresses (automatically assigned), so if you run the networking wizard and
share out the internet access, does it assign itself a 192 address?
Saying that remember I did try static IP addressing and that didn't work
either.
Strange or what!
Any help would be appreciated.
Thanks in advance,
Mon

Chuck
07-10-2005, 01:52 AM
On Tue, 17 May 2005 01:41:01 -0700, Mon <Mon@discussions.microsoft.com> wrote:

>Hi,
>I have 4 computers - 3 are brand new Dell XP Pro SP2 and the other W2k. Two
>computers are in one room and the other two in another. The computers are
>all networked. In one room 2 XP pro machines, one is the ICS host and the
>other a client, so is the other room (they are clients). ISDN is used for
>internet.
>All computers are connecting to the internet through ICS with no problems
>there. But I have problems with all computers viewing the host! we cannot
>share anything on the host as the other three PC's cannot view it. Even
>though they are using it to connect to the internet
>I have tried using static IP addressing, to see if it solved the problem and
>got no results. I have also tried putting in the hosts and lmhosts the IP
>addresses of two machines to test (the host and the client next to it). I
>have disabled the firewalls.
>I am at the end of the line here because the network seems fine i.e. all
>PC's are using the network and the host to get out onto the internet and that
>works fine.
>Has anyone come across this problem before? is it a corruption in Windows?
>the customer is going to wipe out the two PC's, the host and client in one
>room, to see if it solves the problem. I've never come across this and
>cannot understand why they can communicate via ICS but cannot share files or
>printers (the two PC's in the other room are fine) File and Printer sharing
>are enabled on all of them. In fact the host can actually view printers from
>the other room and print to them but the other computers cannot see the
>printers or shared items on the host!
>After I left the customers site, something hit me like lightning. The host
>had a 192.168.1.0 address, (while using APIPA), and the others had 169....
>addresses (automatically assigned), so if you run the networking wizard and
>share out the internet access, does it assign itself a 192 address?
>Saying that remember I did try static IP addressing and that didn't work
>either.
>Strange or what!
>Any help would be appreciated.
>Thanks in advance,
>Mon

Mon,

If the host was running ICS, it should have an IP address of 192.168.0.1, and
the other computers should have addresses in 192.168.0.n. I'd be very
interested to learn how the clients got Internet service, with the host using
192.168.1.0, and the clients 169.n.n.n.

There are other reasons for the host and clients to not all be able to see or
access shares on each others, but you have to start with a correctly addressed
LAN.

Please rerun the wizard on the host and clients, and get the IP addressing
correct. The host should have 192.168.0.1, and the clients 192.168.0.n (n
between 2 and 254). Once that's done, then we can tackle the real problem.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Mon
07-10-2005, 01:53 AM
Hi Chuck,
Thanks for that; actually the Host had the 192.168.0.1. But doesn't ICS use
APIPA? i.e. 169.x.x.x, because that was what I actually saw on one of the
clients.
Also, when running the wizard, all clients have to be set to obtain IP
address automatically? or could I run the wizard and the host will give
itself 192.168.0.1 and I could give all the clients 192.168.0.n? I have never
had this problem before, I have setup loads of networks, using the wizard and
also using static IP addressing, but this one is driving me up the wall.
Mon

"Chuck" wrote:

> On Tue, 17 May 2005 01:41:01 -0700, Mon <Mon@discussions.microsoft.com> wrote:
>
> >Hi,
> >I have 4 computers - 3 are brand new Dell XP Pro SP2 and the other W2k. Two
> >computers are in one room and the other two in another. The computers are
> >all networked. In one room 2 XP pro machines, one is the ICS host and the
> >other a client, so is the other room (they are clients). ISDN is used for
> >internet.
> >All computers are connecting to the internet through ICS with no problems
> >there. But I have problems with all computers viewing the host! we cannot
> >share anything on the host as the other three PC's cannot view it. Even
> >though they are using it to connect to the internet
> >I have tried using static IP addressing, to see if it solved the problem and
> >got no results. I have also tried putting in the hosts and lmhosts the IP
> >addresses of two machines to test (the host and the client next to it). I
> >have disabled the firewalls.
> >I am at the end of the line here because the network seems fine i.e. all
> >PC's are using the network and the host to get out onto the internet and that
> >works fine.
> >Has anyone come across this problem before? is it a corruption in Windows?
> >the customer is going to wipe out the two PC's, the host and client in one
> >room, to see if it solves the problem. I've never come across this and
> >cannot understand why they can communicate via ICS but cannot share files or
> >printers (the two PC's in the other room are fine) File and Printer sharing
> >are enabled on all of them. In fact the host can actually view printers from
> >the other room and print to them but the other computers cannot see the
> >printers or shared items on the host!
> >After I left the customers site, something hit me like lightning. The host
> >had a 192.168.1.0 address, (while using APIPA), and the others had 169....
> >addresses (automatically assigned), so if you run the networking wizard and
> >share out the internet access, does it assign itself a 192 address?
> >Saying that remember I did try static IP addressing and that didn't work
> >either.
> >Strange or what!
> >Any help would be appreciated.
> >Thanks in advance,
> >Mon
>
> Mon,
>
> If the host was running ICS, it should have an IP address of 192.168.0.1, and
> the other computers should have addresses in 192.168.0.n. I'd be very
> interested to learn how the clients got Internet service, with the host using
> 192.168.1.0, and the clients 169.n.n.n.
>
> There are other reasons for the host and clients to not all be able to see or
> access shares on each others, but you have to start with a correctly addressed
> LAN.
>
> Please rerun the wizard on the host and clients, and get the IP addressing
> correct. The host should have 192.168.0.1, and the clients 192.168.0.n (n
> between 2 and 254). Once that's done, then we can tackle the real problem.
>
> --
> Cheers,
> Chuck
> http://nitecruzr.blogspot.com/
> Paranoia is not necessarily a bad thing - it's a normal response from experience.
> My email is AT DOT
> actual address pchuck sonic net.
>

Chuck
07-10-2005, 01:53 AM
On Fri, 20 May 2005 01:57:26 -0700, Mon <Mon@discussions.microsoft.com> wrote:

>Hi Chuck,
>Thanks for that; actually the Host had the 192.168.0.1. But doesn't ICS use
>APIPA? i.e. 169.x.x.x, because that was what I actually saw on one of the
>clients.
>Also, when running the wizard, all clients have to be set to obtain IP
>address automatically? or could I run the wizard and the host will give
>itself 192.168.0.1 and I could give all the clients 192.168.0.n? I have never
>had this problem before, I have setup loads of networks, using the wizard and
>also using static IP addressing, but this one is driving me up the wall.
>Mon

Mon,

ICS uses 192.168.0.0/24, where the host gets 192.168.0.1, and the clients
192.168.0.n, where "n" is between 2 and 254.

If ICS is enabled, and any computer is not getting 192.168.0.n, there is a
problem with the LAN.

You run the wizard on the host, and select "This computer connects directly to
the Internet. The other computers on my network connect to the Internet through
this computer.". ICS will assign 192.168.0.1 to the network adapter that you
select for sharing the service.

You may run the wizard on the clients, and select "This computer connects to the
Internet through another computer on my network or through a residential
gateway." Or you may set each client, manually, to use DHCP for addresses. On
a properly working LAN, you'll get the same results. You may manually setup
addressing, if you wish, but you should do that consistently.

If you get an APIPA address on any computer, you have a problem. APIPA only
supports communication with other hosts on the same subnet.

If the computers are connecting to the internet, but can't share files, you have
a different problem. If you're using Network Neighborhood / My Network Places
to locate and access shares, but can't, start here:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Mon
07-10-2005, 01:53 AM
Hi Chuck,
Thanks for that. I'm back to the customer next week to see if I can solve
this.
Mon.

"Mon" wrote:

> Hi Chuck,
> Thanks for that; actually the Host had the 192.168.0.1. But doesn't ICS use
> APIPA? i.e. 169.x.x.x, because that was what I actually saw on one of the
> clients.
> Also, when running the wizard, all clients have to be set to obtain IP
> address automatically? or could I run the wizard and the host will give
> itself 192.168.0.1 and I could give all the clients 192.168.0.n? I have never
> had this problem before, I have setup loads of networks, using the wizard and
> also using static IP addressing, but this one is driving me up the wall.
> Mon
>
> "Chuck" wrote:
>
> > On Tue, 17 May 2005 01:41:01 -0700, Mon <Mon@discussions.microsoft.com> wrote:
> >
> > >Hi,
> > >I have 4 computers - 3 are brand new Dell XP Pro SP2 and the other W2k. Two
> > >computers are in one room and the other two in another. The computers are
> > >all networked. In one room 2 XP pro machines, one is the ICS host and the
> > >other a client, so is the other room (they are clients). ISDN is used for
> > >internet.
> > >All computers are connecting to the internet through ICS with no problems
> > >there. But I have problems with all computers viewing the host! we cannot
> > >share anything on the host as the other three PC's cannot view it. Even
> > >though they are using it to connect to the internet
> > >I have tried using static IP addressing, to see if it solved the problem and
> > >got no results. I have also tried putting in the hosts and lmhosts the IP
> > >addresses of two machines to test (the host and the client next to it). I
> > >have disabled the firewalls.
> > >I am at the end of the line here because the network seems fine i.e. all
> > >PC's are using the network and the host to get out onto the internet and that
> > >works fine.
> > >Has anyone come across this problem before? is it a corruption in Windows?
> > >the customer is going to wipe out the two PC's, the host and client in one
> > >room, to see if it solves the problem. I've never come across this and
> > >cannot understand why they can communicate via ICS but cannot share files or
> > >printers (the two PC's in the other room are fine) File and Printer sharing
> > >are enabled on all of them. In fact the host can actually view printers from
> > >the other room and print to them but the other computers cannot see the
> > >printers or shared items on the host!
> > >After I left the customers site, something hit me like lightning. The host
> > >had a 192.168.1.0 address, (while using APIPA), and the others had 169....
> > >addresses (automatically assigned), so if you run the networking wizard and
> > >share out the internet access, does it assign itself a 192 address?
> > >Saying that remember I did try static IP addressing and that didn't work
> > >either.
> > >Strange or what!
> > >Any help would be appreciated.
> > >Thanks in advance,
> > >Mon
> >
> > Mon,
> >
> > If the host was running ICS, it should have an IP address of 192.168.0.1, and
> > the other computers should have addresses in 192.168.0.n. I'd be very
> > interested to learn how the clients got Internet service, with the host using
> > 192.168.1.0, and the clients 169.n.n.n.
> >
> > There are other reasons for the host and clients to not all be able to see or
> > access shares on each others, but you have to start with a correctly addressed
> > LAN.
> >
> > Please rerun the wizard on the host and clients, and get the IP addressing
> > correct. The host should have 192.168.0.1, and the clients 192.168.0.n (n
> > between 2 and 254). Once that's done, then we can tackle the real problem.
> >
> > --
> > Cheers,
> > Chuck
> > http://nitecruzr.blogspot.com/
> > Paranoia is not necessarily a bad thing - it's a normal response from experience.
> > My email is AT DOT
> > actual address pchuck sonic net.
> >


ICS and static networking problems