ICS clients cannot connect

[Peter]

Hi

Windows XP pro (ICS Host)
Windows 2000 pro (ICS client)
Windows XP pro (ICS client)

Everything was working smoothly. Today I turned the
machines on. I dialled up and connected. The clients
did not want to connect. When I opened the Internet
browser on the clients machines, "Page cannot be
displayed" appears. I hit F5 and the same page
reappears. I also did what the following KB says:

http://support.microsoft.com/?id=311070

But it did not correct the problem.

Can anyone please help ?

Thanks a lot

 

[Peter]

Thanks Ashleigh

I tried to ping from the one of my ICS client using
192.168.0.1 . The reply I received is "Desitination
host unreachable".

You said if it fails at the 192.168.0.1 then the issue is
with that. I don't understand what you mean by "the
issue is with that".

The rest of your reply is not traightforward to me as I
am not as technical as you are. Also I am not sure as to
how I can do "tracerouting to cisco.com" or "telnet".
You would be helpful if you can help me carry out these
tests step-by-step.

I appreciate it.

Regards

-----Original Message-----
Try pinging from one of the ics client computers to the

ics host, if that works try tracerouting to cisco.com
(tracert cisco.com) and see where it fails you should
have something like : -

Tracing route to cisco.com [198.133.219.25]
over a maximum of 30 hops:

1 1ms 1ms 1ms 192.168.0.1 (ics host computer)
2 1ms 1ms 1ms isp.router
3 1ms 1ms 1ms isp.router
4 1ms 1ms 1ms isp.router
5 1ms 1ms 1ms isp.router
6 1ms 1ms 1ms cisco.com

If it fails at the 192.168.0.1 then the issue is with

that, if it cant find an ip address for cisco.com try
using the cisco.com ip address (see above) and see if
that works. if that does work then you have a dns issue
with the client machines, either manually configure the
dns on the machines to point to your isp's dns server (do
ipconfig /all on the host machine for that information)
it should then work, and so should IE.

If it's all working at an ICMP level (traceroute) then

it's an issue most likely on the host machine, try typing
from a command prompt on one of the clients "telnet
www.microsoft.com 80" and press enter twice, if you get a
400 error message from an iis server then it should work
in IE, make sure there is no proxy configuration in the
IE machines.

Anything else let me know, or let me know what is / isnt

working and maybe I can help further.

 

[Guest]

No problems, try keep it simple.

On the host machine goto a command prompt (start / run / cmd.exe)

Type "ipconfig /all" and you should get something similar (not exactly the same though as this is from longhorn) as

Windows IP Configuration

Host Name . . . . . . . . . . . . : LH-AGFVA03ECR8T
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : corp.pg.eon.net
powergen.int
retail.pg.eon.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : corp.pg.eon.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network Connection
Physical Address. . . . . . . . . : 00-02-A5-7D-AF-6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::202:a5ff:fe7d:af6c%2
IPv4 Address. . . . . . . . . . . : 10.80.97.175
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 June 2004 15:58:58
Lease Expires . . . . . . . . . . : 29 June 2004 15:58:58
Default Gateway . . . . . . . . . : 10.80.97.1
DHCP Server . . . . . . . . . . . : 10.80.96.12
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
10.80.96.11
10.80.96.12
Primary WINS Server . . . . . . . : 10.80.96.11
Secondary WINS Server . . . . . . : 10.82.3.11
NetBIOS over Tcpip. . . . . . . . : Enabled

Your looking to make sure that your IP address is 192.168.0.1

After you have made sure that this is in fact correct goto one of the client machines and do the same, the ip address on this machine should be 192.168.0.x where x is a number between 2 and 253. Also on the client machine make sure the default gateway is 192.168.0.1.

2 things to try if both machines are setup like this, then try turning ICS off (right click the dialup/internet connection from the network control panel icon. then advanced and untick the ICS tick. Ok that then right click and turn it back on, go through the wizard and it will reset the ICS settings back to there defaults.

After you have done that try typing "ipconfig /release" then "ipconfig /renew" on the client machine, this should then get a network address from the ics host machine (192.168.0.x). If you dont get an IP address or the address starts with 169.x.x.x then there is a network problem, does the router/hub work? (try using a crossover cable between the host and one of the clients and repeat the above steps), or it may be a dodgy driver/card on the host machine or the firewall is enabled (see 3 steps below).

Now from a command prompt on the client machine type "tracert cisco.com" and see if it A-Finds the IP address for cisco.com, and B-traces to the ip address (make sure there are no *'s in the trace). If that works, then try internet explorer on the client.

If all this works then either reboot all the client machines, or "ipconfig /renew" on them, they should all then work.

If you still have problems, there are a few things to check, from a command prompt on the client machines type "ping 192.168.0.1" and make sure that works, if it does then type "telnet www.microsoft.com 80" and press enter twice and see if you get a 400 error.

If you cannot ping 192.168.0.1 make sure the firewall is turned off on the network card for the local connection, goto network control panel icon, right click the network card, select advanced and make sure the firewall is not enabled. if this is allready not enabled, try pinging one of the client machines from the host type "ping 192.168.0.x" (where x is the address you got from above) and see if that works.

If you are still struggling, on one of the client machines goto control panel / network and select the network card, click properties, Internet Protocol (tcp ip) properties, then in the field fill in

Use the following Ip Address (selected)

IP Address 192.168.0.10
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1

Use the following DNS server (selected)
Preferred DNS server 192.168.0.1
Alternate DNS server 158.152.1.58 (demon in the UK)

Click OK all the way out, now try pinging cisco.com / 192.168.0.1 if this works then the DHCP seems to be failing on the host, you can manually configure all the clients this way (change the 192.168.0.10 to 11, then 12 etc), or check to see if your router/switch is blocking the traffic (dependant on what your using).

Have a flick through and shout if something makes no sense.

Ashleigh

Thanks Ashleigh

I tried to ping from the one of my ICS client using
192.168.0.1 . The reply I received is "Desitination
host unreachable".

You said if it fails at the 192.168.0.1 then the issue is
with that. I don't understand what you mean by "the
issue is with that".

The rest of your reply is not traightforward to me as I
am not as technical as you are. Also I am not sure as to
how I can do "tracerouting to cisco.com" or "telnet".
You would be helpful if you can help me carry out these
tests step-by-step.

I appreciate it.

Regards

-----Original Message-----
Try pinging from one of the ics client computers to the

ics host, if that works try tracerouting to cisco.com
(tracert cisco.com) and see where it fails you should
have something like : -

Tracing route to cisco.com [198.133.219.25]
over a maximum of 30 hops:

1 1ms 1ms 1ms 192.168.0.1 (ics host computer)
2 1ms 1ms 1ms isp.router
3 1ms 1ms 1ms isp.router
4 1ms 1ms 1ms isp.router
5 1ms 1ms 1ms isp.router
6 1ms 1ms 1ms cisco.com

If it fails at the 192.168.0.1 then the issue is with

that, if it cant find an ip address for cisco.com try
using the cisco.com ip address (see above) and see if
that works. if that does work then you have a dns issue
with the client machines, either manually configure the
dns on the machines to point to your isp's dns server (do
ipconfig /all on the host machine for that information)
it should then work, and so should IE.

If it's all working at an ICMP level (traceroute) then

it's an issue most likely on the host machine, try typing
from a command prompt on one of the clients "telnet
www.microsoft.com 80" and press enter twice, if you get a
400 error message from an iis server then it should work
in IE, make sure there is no proxy configuration in the
IE machines.

Anything else let me know, or let me know what is / isnt

working and maybe I can help further.

.

 

[Peter]

I've got this from the ICS host:

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : My name
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek
RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-C0-49-D5-
A2-D1
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

PPP adapter {E79B87ED-3382-4865-8E3D-B88972C8C4AF}:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN
(PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-
00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.64.207.26
Subnet Mask . . . . . . . . . . . :
255.255.255.255
Default Gateway . . . . . . . . . : 62.64.207.26
DNS Servers . . . . . . . . . . . : 213.235.53.17
213.235.53.19


This is from one of ICS clients:


C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : 2ndname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek
RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-C0-49-D5-
A2-F1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfuguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.164.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


I turned off ICS host and then enabled it. The Wizard
did not appear to take me through any process. I went to
the client and entered "ipconfig /release". It looked
ok. But when I renewed it, I received: "An error
occurred when renewing interface Local Area Connection:
unable to contact your DHCP server. Request has timed
out."

The DHCP on my ICS host is not enabled. Why should it be
enabled since ICS which automatically assigns IP
addresses when enabled ?

Also the Default Gateway are blank at both host and
client ?

Regards

Peter

-----Original Message-----
No problems, try keep it simple.

On the host machine goto a command prompt (start / run / cmd.exe)

Type "ipconfig /all" and you should get something

similar (not exactly the same though as this is from
longhorn) as

Windows IP Configuration

Host Name . . . . . . . . . . . . : LH-AGFVA03ECR8T
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : corp.pg.eon.net
powergen.int
retail.pg.eon.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : corp.pg.eon.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network Connection
Physical Address. . . . . . . . . : 00-02-A5-7D-AF-6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::202:a5ff:fe7d:af6c%2
IPv4 Address. . . . . . . . . . . : 10.80.97.175
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 June 2004 15:58:58
Lease Expires . . . . . . . . . . : 29 June 2004 15:58:58
Default Gateway . . . . . . . . . : 10.80.97.1
DHCP Server . . . . . . . . . . . : 10.80.96.12
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
10.80.96.11
10.80.96.12
Primary WINS Server . . . . . . . : 10.80.96.11
Secondary WINS Server . . . . . . : 10.82.3.11
NetBIOS over Tcpip. . . . . . . . : Enabled

Your looking to make sure that your IP address is 192.168.0.1

After you have made sure that this is in fact correct

goto one of the client machines and do the same, the ip
address on this machine should be 192.168.0.x where x is
a number between 2 and 253. Also on the client machine
make sure the default gateway is 192.168.0.1.

2 things to try if both machines are setup like this,

then try turning ICS off (right click the dialup/internet
connection from the network control panel icon. then
advanced and untick the ICS tick. Ok that then right
click and turn it back on, go through the wizard and it
will reset the ICS settings back to there defaults.

After you have done that try typing "ipconfig /release"

then "ipconfig /renew" on the client machine, this should
then get a network address from the ics host machine
(192.168.0.x). If you dont get an IP address or the
address starts with 169.x.x.x then there is a network
problem, does the router/hub work? (try using a crossover
cable between the host and one of the clients and repeat
the above steps), or it may be a dodgy driver/card on the
host machine or the firewall is enabled (see 3 steps
below).

Now from a command prompt on the client machine

type "tracert cisco.com" and see if it A-Finds the IP
address for cisco.com, and B-traces to the ip address
(make sure there are no *'s in the trace). If that works,
then try internet explorer on the client.

If all this works then either reboot all the client

machines, or "ipconfig /renew" on them, they should all
then work.

If you still have problems, there are a few things to

check, from a command prompt on the client machines
type "ping 192.168.0.1" and make sure that works, if it
does then type "telnet www.microsoft.com 80" and press
enter twice and see if you get a 400 error.

If you cannot ping 192.168.0.1 make sure the firewall is

turned off on the network card for the local connection,
goto network control panel icon, right click the network
card, select advanced and make sure the firewall is not
enabled. if this is allready not enabled, try pinging one
of the client machines from the host type "ping
192.168.0.x" (where x is the address you got from above)
and see if that works.

If you are still struggling, on one of the client

machines goto control panel / network and select the
network card, click properties, Internet Protocol (tcp
ip) properties, then in the field fill in

Use the following Ip Address (selected)

IP Address 192.168.0.10
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1

Use the following DNS server (selected)
Preferred DNS server 192.168.0.1
Alternate DNS server 158.152.1.58 (demon in the UK)

Click OK all the way out, now try pinging cisco.com /

192.168.0.1 if this works then the DHCP seems to be
failing on the host, you can manually configure all the
clients this way (change the 192.168.0.10 to 11, then 12
etc), or check to see if your router/switch is blocking
the traffic (dependant on what your using).

Have a flick through and shout if something makes no sense.

Ashleigh

Thanks Ashleigh

I tried to ping from the one of my ICS client using
192.168.0.1 . The reply I received is "Desitination
host unreachable".

You said if it fails at the 192.168.0.1 then the issue is
with that. I don't understand what you mean by "the
issue is with that".

The rest of your reply is not traightforward to me as I
am not as technical as you are. Also I am not sure as to
how I can do "tracerouting to cisco.com" or "telnet".
You would be helpful if you can help me carry out these
tests step-by-step.

I appreciate it.

Regards

-----Original Message-----
Try pinging from one of the ics client computers to

the
ics host, if that works try tracerouting to cisco.com
(tracert cisco.com) and see where it fails you should
have something like : -

Tracing route to cisco.com [198.133.219.25]
over a maximum of 30 hops:

1 1ms 1ms 1ms 192.168.0.1 (ics host computer)
2 1ms 1ms 1ms isp.router
3 1ms 1ms 1ms isp.router
4 1ms 1ms 1ms isp.router
5 1ms 1ms 1ms isp.router
6 1ms 1ms 1ms cisco.com

If it fails at the 192.168.0.1 then the issue is with

that, if it cant find an ip address for cisco.com try
using the cisco.com ip address (see above) and see if
that works. if that does work then you have a dns issue
with the client machines, either manually configure the
dns on the machines to point to your isp's dns server (do
ipconfig /all on the host machine for that information)
it should then work, and so should IE.

If it's all working at an ICMP level (traceroute)

then
it's an issue most likely on the host machine, try typing
from a command prompt on one of the clients "telnet
www.microsoft.com 80" and press enter twice, if you get a
400 error message from an iis server then it should work
in IE, make sure there is no proxy configuration in the
IE machines.

Anything else let me know, or let me know what is /

isnt
working and maybe I can help further.

:

Hi

Windows XP pro (ICS Host)
Windows 2000 pro (ICS client)
Windows XP pro (ICS client)

Everything was working smoothly. Today I turned the
machines on. I dialled up and connected. The clients
did not want to connect. When I opened the Internet
browser on the clients machines, "Page cannot be
displayed" appears. I hit F5 and the same page
reappears. I also did what the following KB says:

http://support.microsoft.com/?id=311070

But it did not correct the problem.

Can anyone please help ?

Thanks a lot

.

.

 

[Peter]

I tried to set those addresse manually at the client
machine. I then went to CMD and checked the new IP
configuration using "ipconfig /all". Afterwards, I
pingged the IP address 192.168.0.1. The reply
was: "Request timed out".

What I didn't try is to check "crossover cable". I don't
what is that. I have an Ethernet Hub with 4 ports. The
cables are cat45 I think. Crossover I have no clue what
is it.

Do I have to get a new Hub and a New NIC ?

I very much appreciated your help in this diagnosis.

Peter.

-----Original Message-----
Strange, it looks like the DHCP part of ICS is not

working as it should (if the card has a 169.x.x.x address
then it's failed to get one, and this is an 'emergency'
address that windows gives itself)

Try going to a client machine and inputing the address

manually (detailed in last post, but)

Start / Controll Panel / Network

Dbl click the network card

Select properties

Select Internet protocol, then properties

Select manual address

set ip to 192.168.0.10
set subnet to 255.255.255.0
set default gateway to 192.168.0.1
set dns master to 192.168.0.1
set second dns to 158.152.1.58

Ok, apply

goto cmd.exe type "ipconfig /all" and you should get the

details of what you typed above back.

Try "ping 192.168.0.1" if that works then this pc should

get onto the internet, if not then my guess would be
either a dodgy card in the ics master, or duff
hub/router/switch between the boxes. To check use a
crossover cable between the host and the client and see
if you can then ping the host (192.168.0.1), if not then
probably a bad nic in the host, if you can then almost
definatly an issue with the connectivity between the
boxes (cable / switch / router / hub)

DHCP should not be turned on on the master, just on the

clients as ICS has a DHCP Server built into it. Also make
sure the firewall is disabled on the master.

Give that a go and let me know

Ashleigh

I've got this from the ICS host:

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : My name
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek
RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-C0-49- D5-
A2-D1
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

PPP adapter {E79B87ED-3382-4865-8E3D-B88972C8C4AF}:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN
(PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45- 00-
00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.64.207.26
Subnet Mask . . . . . . . . . . . :
255.255.255.255
Default Gateway . . . . . . . . . : 62.64.207.26
DNS Servers . . . . . . . . . . . : 213.235.53.17
213.235.53.19


This is from one of ICS clients:


C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : 2ndname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek
RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-C0-49- D5-
A2-F1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfuguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.164.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


I turned off ICS host and then enabled it. The Wizard
did not appear to take me through any process. I went to
the client and entered "ipconfig /release". It looked
ok. But when I renewed it, I received: "An error
occurred when renewing interface Local Area Connection:
unable to contact your DHCP server. Request has timed
out."

The DHCP on my ICS host is not enabled. Why should it be
enabled since ICS which automatically assigns IP
addresses when enabled ?

Also the Default Gateway are blank at both host and
client ?

Regards

Peter

-----Original Message-----
No problems, try keep it simple.

On the host machine goto a command prompt (start /

run /
cmd.exe)

Type "ipconfig /all" and you should get something

similar (not exactly the same though as this is from
longhorn) as

Windows IP Configuration

Host Name . . . . . . . . . . . . : LH-AGFVA03ECR8T
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : corp.pg.eon.net
powergen.int
retail.pg.eon.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : corp.pg.eon.net
Description . . . . . . . . . . . : Intel(R)

PRO/100
VM Network Connection

Physical Address. . . . . . . . . : 00-02-A5-7D-AF- 6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::202:a5ff:fe7d:af6c%2
IPv4 Address. . . . . . . . . . . : 10.80.97.175
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 June 2004 15:58:58
Lease Expires . . . . . . . . . . : 29 June 2004 15:58:58
Default Gateway . . . . . . . . . : 10.80.97.1
DHCP Server . . . . . . . . . . . : 10.80.96.12
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
10.80.96.11
10.80.96.12
Primary WINS Server . . . . . . . : 10.80.96.11
Secondary WINS Server . . . . . . : 10.82.3.11
NetBIOS over Tcpip. . . . . . . . : Enabled

Your looking to make sure that your IP address is 192.168.0.1

After you have made sure that this is in fact correct

goto one of the client machines and do the same, the ip
address on this machine should be 192.168.0.x where x is
a number between 2 and 253. Also on the client machine
make sure the default gateway is 192.168.0.1.

2 things to try if both machines are setup like this,

then try turning ICS off (right click the dialup/internet
connection from the network control panel icon. then
advanced and untick the ICS tick. Ok that then right
click and turn it back on, go through the wizard and it
will reset the ICS settings back to there defaults.

After you have done that try

typing "ipconfig /release"
then "ipconfig /renew" on the client machine, this should
then get a network address from the ics host machine
(192.168.0.x). If you dont get an IP address or the
address starts with 169.x.x.x then there is a network
problem, does the router/hub work? (try using a crossover
cable between the host and one of the clients and repeat
the above steps), or it may be a dodgy driver/card on the
host machine or the firewall is enabled (see 3 steps
below).

Now from a command prompt on the client machine

type "tracert cisco.com" and see if it A-Finds the IP
address for cisco.com, and B-traces to the ip address
(make sure there are no *'s in the trace). If that works,
then try internet explorer on the client.

If all this works then either reboot all the client

machines, or "ipconfig /renew" on them, they should all
then work.

If you still have problems, there are a few things to

check, from a command prompt on the client machines
type "ping 192.168.0.1" and make sure that works, if it
does then type "telnet www.microsoft.com 80" and press
enter twice and see if you get a 400 error.

If you cannot ping 192.168.0.1 make sure the firewall

is
turned off on the network card for the local connection,
goto network control panel icon, right click the network
card, select advanced and make sure the firewall is not
enabled. if this is allready not enabled, try pinging one
of the client machines from the host type "ping
192.168.0.x" (where x is the address you got from above)
and see if that works.

If you are still struggling, on one of the client

machines goto control panel / network and select the
network card, click properties, Internet Protocol (tcp
ip) properties, then in the field fill in

Use the following Ip Address (selected)

IP Address 192.168.0.10
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1

Use the following DNS server (selected)
Preferred DNS server 192.168.0.1
Alternate DNS server 158.152.1.58 (demon in the UK)

Click OK all the way out, now try pinging cisco.com /

192.168.0.1 if this works then the DHCP seems to be
failing on the host, you can manually configure all the
clients this way (change the 192.168.0.10 to 11, then 12
etc), or check to see if your router/switch is blocking
the traffic (dependant on what your using).

Have a flick through and shout if something makes no sense.

Ashleigh

:

Thanks Ashleigh

I tried to ping from the one of my ICS client using
192.168.0.1 . The reply I received is "Desitination
host unreachable".

You said if it fails at the 192.168.0.1 then the

issue
is

with that. I don't understand what you mean by "the
issue is with that".

The rest of your reply is not traightforward to me

as
I

am not as technical as you are. Also I am not sure

as
to

how I can do "tracerouting to cisco.com" or "telnet".
You would be helpful if you can help me carry out these
tests step-by-step.

I appreciate it.

Regards


-----Original Message-----
Try pinging from one of the ics client computers

to
the

ics host, if that works try tracerouting to cisco.com
(tracert cisco.com) and see where it fails you should
have something like : -

Tracing route to cisco.com [198.133.219.25]
over a maximum of 30 hops:

1 1ms 1ms 1ms 192.168.0.1 (ics host computer)
2 1ms 1ms 1ms isp.router
3 1ms 1ms 1ms isp.router
4 1ms 1ms 1ms isp.router
5 1ms 1ms 1ms isp.router
6 1ms 1ms 1ms cisco.com

If it fails at the 192.168.0.1 then the issue is with
that, if it cant find an ip address for cisco.com try
using the cisco.com ip address (see above) and see if
that works. if that does work then you have a dns issue
with the client machines, either manually configure the
dns on the machines to point to your isp's dns

server
(do

ipconfig /all on the host machine for that information)
it should then work, and so should IE.

If it's all working at an ICMP level (traceroute) then
it's an issue most likely on the host machine, try typing
from a command prompt on one of the clients "telnet
www.microsoft.com 80" and press enter twice, if you get a
400 error message from an iis server then it should work
in IE, make sure there is no proxy configuration in the
IE machines.

Anything else let me know, or let me know what

is /
isnt

working and maybe I can help further.

:

Hi

Windows XP pro (ICS Host)
Windows 2000 pro (ICS client)
Windows XP pro (ICS client)

Everything was working smoothly. Today I turned the
machines on. I dialled up and connected. The clients
did not want to connect. When I opened the Internet
browser on the clients machines, "Page cannot be
displayed" appears. I hit F5 and the same page
reappears. I also did what the following KB says:

http://support.microsoft.com/?id=311070

But it did not correct the problem.

Can anyone please help ?

Thanks a lot

.


.

.

 

[Ken Blake, MVP]

In

What I didn't try is to check "crossover cable". I don't
what is that. I have an Ethernet Hub with 4 ports. The
cables are cat45 I think. Crossover I have no clue what
is it.

A crossover cable is a special kind of ethernet cable that can be
used on a network with only two computers. It's goes directly
from NIC to NIC, and is used in place of the normal hub and two
cable setup.

It's obviously not applicable in your case, since you have a hub.

 

[Guest]

A crossover cable would allow you to diagnose if it is in fact your hub or cableing as a crossover is almost garanteed to work (as long as the cable is not duff).

Have you got access to another hub? try that, it looks like there is a problem in the connectivity between the various machines.

One thing to try is to give one of the other client machines an IP address (try 192.168.0.11 and set the rest of the settings as before)

Then see if you can ping it from the machine you setup with 192.168.0.10 (ping 192.168.0.11). If you can then your hub is ok and it looks like it is the network card or drivers on the host machine.

If the above works then remove the network card from the machine you gave 192.168.0.11 too, and replace it with the one you had in the host machine (you will probably have to turn ICS back on after this). and see if you can ping 192.168.0.1 then?

Also have you tried running the Network setup wizard (found in control panel) that may work if it's a configuration issue (however I think it's more likely to be a hardware issue).

A crossover cable wont cost you much (couple of quid here in the UK) and it's an invaluble piece of testing equipment when dealing with networks.

Let me know how you get on.

Ashleigh

I tried to set those addresse manually at the client
machine. I then went to CMD and checked the new IP
configuration using "ipconfig /all". Afterwards, I
pingged the IP address 192.168.0.1. The reply
was: "Request timed out".

What I didn't try is to check "crossover cable". I don't
what is that. I have an Ethernet Hub with 4 ports. The
cables are cat45 I think. Crossover I have no clue what
is it.

Do I have to get a new Hub and a New NIC ?

I very much appreciated your help in this diagnosis.

Peter.

-----Original Message-----
Strange, it looks like the DHCP part of ICS is not

working as it should (if the card has a 169.x.x.x address
then it's failed to get one, and this is an 'emergency'
address that windows gives itself)

Try going to a client machine and inputing the address

manually (detailed in last post, but)

Start / Controll Panel / Network

Dbl click the network card

Select properties

Select Internet protocol, then properties

Select manual address

set ip to 192.168.0.10
set subnet to 255.255.255.0
set default gateway to 192.168.0.1
set dns master to 192.168.0.1
set second dns to 158.152.1.58

Ok, apply

goto cmd.exe type "ipconfig /all" and you should get the

details of what you typed above back.

Try "ping 192.168.0.1" if that works then this pc should

get onto the internet, if not then my guess would be
either a dodgy card in the ics master, or duff
hub/router/switch between the boxes. To check use a
crossover cable between the host and the client and see
if you can then ping the host (192.168.0.1), if not then
probably a bad nic in the host, if you can then almost
definatly an issue with the connectivity between the
boxes (cable / switch / router / hub)

DHCP should not be turned on on the master, just on the

clients as ICS has a DHCP Server built into it. Also make
sure the firewall is disabled on the master.

Give that a go and let me know

Ashleigh

I've got this from the ICS host:

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : My name
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek
RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-C0-49- D5-
A2-D1
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

PPP adapter {E79B87ED-3382-4865-8E3D-B88972C8C4AF}:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN
(PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45- 00-
00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.64.207.26
Subnet Mask . . . . . . . . . . . :
255.255.255.255
Default Gateway . . . . . . . . . : 62.64.207.26
DNS Servers . . . . . . . . . . . : 213.235.53.17
213.235.53.19


This is from one of ICS clients:


C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : 2ndname
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek
RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-C0-49- D5-
A2-F1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfuguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.164.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


I turned off ICS host and then enabled it. The Wizard
did not appear to take me through any process. I went to
the client and entered "ipconfig /release". It looked
ok. But when I renewed it, I received: "An error
occurred when renewing interface Local Area Connection:
unable to contact your DHCP server. Request has timed
out."

The DHCP on my ICS host is not enabled. Why should it be
enabled since ICS which automatically assigns IP
addresses when enabled ?

Also the Default Gateway are blank at both host and
client ?

Regards

Peter

-----Original Message-----
No problems, try keep it simple.

On the host machine goto a command prompt (start / run /
cmd.exe)

Type "ipconfig /all" and you should get something
similar (not exactly the same though as this is from
longhorn) as

Windows IP Configuration

Host Name . . . . . . . . . . . . : LH-AGFVA03ECR8T
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : corp.pg.eon.net
powergen.int
retail.pg.eon.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : corp.pg.eon.net
Description . . . . . . . . . . . : Intel(R) PRO/100
VM Network Connection
Physical Address. . . . . . . . . : 00-02-A5-7D-AF- 6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::202:a5ff:fe7d:af6c%2
IPv4 Address. . . . . . . . . . . : 10.80.97.175
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 June 2004
15:58:58
Lease Expires . . . . . . . . . . : 29 June 2004
15:58:58
Default Gateway . . . . . . . . . : 10.80.97.1
DHCP Server . . . . . . . . . . . : 10.80.96.12
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
10.80.96.11
10.80.96.12
Primary WINS Server . . . . . . . : 10.80.96.11
Secondary WINS Server . . . . . . : 10.82.3.11
NetBIOS over Tcpip. . . . . . . . : Enabled

Your looking to make sure that your IP address is
192.168.0.1

After you have made sure that this is in fact correct
goto one of the client machines and do the same, the ip
address on this machine should be 192.168.0.x where x is
a number between 2 and 253. Also on the client machine
make sure the default gateway is 192.168.0.1.

2 things to try if both machines are setup like this,
then try turning ICS off (right click the dialup/internet
connection from the network control panel icon. then
advanced and untick the ICS tick. Ok that then right
click and turn it back on, go through the wizard and it
will reset the ICS settings back to there defaults.

After you have done that try typing "ipconfig /release"
then "ipconfig /renew" on the client machine, this should
then get a network address from the ics host machine
(192.168.0.x). If you dont get an IP address or the
address starts with 169.x.x.x then there is a network
problem, does the router/hub work? (try using a crossover
cable between the host and one of the clients and repeat
the above steps), or it may be a dodgy driver/card on the
host machine or the firewall is enabled (see 3 steps
below).

Now from a command prompt on the client machine
type "tracert cisco.com" and see if it A-Finds the IP
address for cisco.com, and B-traces to the ip address
(make sure there are no *'s in the trace). If that works,
then try internet explorer on the client.

If all this works then either reboot all the client
machines, or "ipconfig /renew" on them, they should all
then work.

If you still have problems, there are a few things to
check, from a command prompt on the client machines
type "ping 192.168.0.1" and make sure that works, if it
does then type "telnet www.microsoft.com 80" and press
enter twice and see if you get a 400 error.

If you cannot ping 192.168.0.1 make sure the firewall is
turned off on the network card for the local connection,
goto network control panel icon, right click the network
card, select advanced and make sure the firewall is not
enabled. if this is allready not enabled, try pinging one
of the client machines from the host type "ping
192.168.0.x" (where x is the address you got from above)
and see if that works.

If you are still struggling, on one of the client
machines goto control panel / network and select the
network card, click properties, Internet Protocol (tcp
ip) properties, then in the field fill in

Use the following Ip Address (selected)

IP Address 192.168.0.10
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1

Use the following DNS server (selected)
Preferred DNS server 192.168.0.1
Alternate DNS server 158.152.1.58 (demon in the UK)

Click OK all the way out, now try pinging cisco.com /
192.168.0.1 if this works then the DHCP seems to be
failing on the host, you can manually configure all the
clients this way (change the 192.168.0.10 to 11, then 12
etc), or check to see if your router/switch is blocking
the traffic (dependant on what your using).

Have a flick through and shout if something makes no
sense.

Ashleigh

:

Thanks Ashleigh

I tried to ping from the one of my ICS client using
192.168.0.1 . The reply I received is "Desitination
host unreachable".

You said if it fails at the 192.168.0.1 then the issue
is
with that. I don't understand what you mean by "the
issue is with that".

The rest of your reply is not traightforward to me as
I
am not as technical as you are. Also I am not sure as
to
how I can do "tracerouting to cisco.com" or "telnet".
You would be helpful if you can help me carry out
these
tests step-by-step.

I appreciate it.

Regards


-----Original Message-----
Try pinging from one of the ics client computers to
the
ics host, if that works try tracerouting to cisco.com
(tracert cisco.com) and see where it fails you should
have something like : -

Tracing route to cisco.com [198.133.219.25]
over a maximum of 30 hops:

1 1ms 1ms 1ms 192.168.0.1 (ics host computer)
2 1ms 1ms 1ms isp.router
3 1ms 1ms 1ms isp.router
4 1ms 1ms 1ms isp.router
5 1ms 1ms 1ms isp.router
6 1ms 1ms 1ms cisco.com

If it fails at the 192.168.0.1 then the issue is with
that, if it cant find an ip address for cisco.com try
using the cisco.com ip address (see above) and see if
that works. if that does work then you have a dns
issue
with the client machines, either manually configure
the
dns on the machines to point to your isp's dns server
(do
ipconfig /all on the host machine for that
information)
it should then work, and so should IE.

If it's all working at an ICMP level (traceroute)
then
it's an issue most likely on the host machine, try
typing
from a command prompt on one of the clients "telnet
www.microsoft.com 80" and press enter twice, if you
get a
400 error message from an iis server then it should
work
in IE, make sure there is no proxy configuration in
the
IE machines.

Anything else let me know, or let me know what is /
isnt
working and maybe I can help further.

:

Hi

Windows XP pro (ICS Host)
Windows 2000 pro (ICS client)
Windows XP pro (ICS client)

Everything was working smoothly. Today I turned
the
machines on. I dialled up and connected. The
clients
did not want to connect. When I opened the
Internet
browser on the clients machines, "Page cannot be
displayed" appears. I hit F5 and the same page
reappears. I also did what the following KB says:

http://support.microsoft.com/?id=311070

But it did not correct the problem.

Can anyone please help ?

Thanks a lot

.


.

.

 

[Alex Nichol]

I tried to ping from the one of my ICS client using
192.168.0.1 . The reply I received is "Desitination
host unreachable".

You said if it fails at the 192.168.0.1 then the issue is
with that. I don't understand what you mean by "the
issue is with that".

192.168.0.1 is the address of the Host machine in an ICS setup. Check
on that one; in its Net connections, r-click the connection to the
Internet, Properties and make sure that the Advanced page has the 'allow
other users to connect to the internet' box checked

Then highlight the connection to the other machines and make sure it
*is* using 192.168.0.1 - if not right click - Properties, highlight
TCPIP and Properties, and tell it to 'Use the following IP address',
filling that in. Also click Advanced and on the WINS page make sure it
has selected 'Enable NETBIOS over TCPIP'