PDA

View Full Version : Client PC can't connect to the web - Part 2!


Trevor Midgley
May 27th 03, 10:39 AM
I hope I'm not contravening etiquette here!

A few days ago, Steve Winograd kindly responded to a problem that I'm
having with Internet access on my home network.

I posted a follow-up, but I think it got lost in the traffic.

Anyway, this is a repeat post of my last message which I hope someone
can help me with.

Thanks.

**************

Steve – thanks for the reply.

I'm pretty sure I'm using XP's ICS – Intel's help desk sort of took
over when I first installed the system and removed their ISS software.

I'm not connected via the Local Area Connection, but via a connection
called Wireless Network Connection 3 immediately below LAC in the
Network Connections list. (This relates specifically to my Intel
Anypoint II Wireless system.)

The readings for the WNC3 on my XP server (host) are:

Physical Address: 00-90-4B-05-5F-D9
IP Address: 169.254.57.22
Subnet Mask: 255.255.0.0
Default Gateway:
DNS Server:
WINS Server:

These are the Winipcfg details from my Me client machine:

Host Name: FRONT-COMPUTER
DNS Servers:
Node Type: Broadcast
NetBIOS Scope ID:
IP Routing Enabled (unchecked)
WINS Proxy Enabled (unchecked)
NetBIOS Resolution Uses DNS (unchecked)
Adapter Address: 00-90-4B-05-51-B5
IP Autoconfiguration Address: 169.254.74.65
Subnet Mask: 255.255.0.0
Default Gateway:
DHCP Server: 255.255.255.255
Primary WINS Server:
Secondary WINS Server:
Lease Obtained: 05 25 03 10:43:24 AM
Lease Expires:

Pinging each machine from the other is fine using the respective
169.254.57.22 and 169.254.74.65 IP addresses.

Pinging 216.239.39.100 and www.google.com from the XP HOST (server) is
also OK.

However, pinging 216.239.39.100 and www.google.com from the Me CLIENT
produces the respective responses "Destination host unreachable" and
"unknown host".

Network-wise, I have complete file access both ways. It's only
internet access (and of course, the e-mail facility) that's
unavailable to the Me client.

I hope this is helpful to you, and that you can suggest how and where
my client machine is wrongly configured.

Thanks again for replying.

**************


Steve Winograd > wrote in message >...
> In article >,
> (Trevor Midgley) wrote:
> >Hi!
> >
> >I have an Intel Anypoint II Wireless network system connecting my two
> >computers. The server is an XP and the client is Me.
> >
> >Everything worked fine for nine months until three days ago.
> >
> >Suddenly, although the signal quality and strength between machines
> >remained strong, neither machine would recognise the other.
> >
> >Through loads of trial and error and burning of midnight oil, I've now
> >managed to get both boxes back happily chattering to each other. It
> >seems that, basically, the problem was that something knocked out my
> >instructions to "share" files.
> >
> >However, no matter what I try, I can't get my Me client machine to
> >access the internet. No problem from the XP server - hence this
> >posting! - but I obviously need net (and e-mail) access from both
> >machines.
> >
> >Intel in their wisdom have shut down their phone help for the
> >Anypoint Wireless II networking system, and their "web help" facility
> >isn't much use.
> >
> >(I don't have the ISS software installed, by the way. Apparently this
> >was causing some problems with XP in the early days and, with Intel's
> >guidance, it was left off when my network was set up those nine months
> >ago.)
> >
> >Any advice or help appreciated. This is probably a simple problem to
> >anyone but a novice.
> >
> >Sadly, it's proving beyond me!
>
> What program are you using to share the Internet connection?
>
> If it's XP's built-in Internet Connection Sharing, run these tests to
> help find the problem:
>
> 1. On the XP host computer, right click the local area network
> connection and click Status | Support | Details. It should show:
>
> IP Address: 192.168.0.1
> Subnet Mask: 255.255.255.0
> Default Gateway: none
> DNS Server = none
>
> 2. On the Me client computer, go to Start | Run | Winipcfg, select the
> network adapter, and click More Info. It should show:
>
> IP Address: 192.168.0.x (1<x<255)
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.0.1
> DNS Server = 192.168.0.1 or your ISP's DNS server
>
> 3. If #1 and #2 are right, open a command prompt window on the client
> and enter these lines. Each one should get four replies:
>
> ping 192.168.0.1
> ping 216.239.39.100
> ping www.google.com
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com

Steve Winograd
May 27th 03, 12:39 PM
In article >,
(Trevor Midgley) wrote:
>I hope I'm not contravening etiquette here!
>
>A few days ago, Steve Winograd kindly responded to a problem that I'm
>having with Internet access on my home network.
>
>I posted a follow-up, but I think it got lost in the traffic.
>
>Anyway, this is a repeat post of my last message which I hope someone
>can help me with.
>
>Thanks.

I've flagged your previous message, Trevor, but I just haven't had
time to get back to it.

>**************
>
>Steve – thanks for the reply.
>
>I'm pretty sure I'm using XP's ICS – Intel's help desk sort of took
>over when I first installed the system and removed their ISS software.
>
>I'm not connected via the Local Area Connection, but via a connection
>called Wireless Network Connection 3 immediately below LAC in the
>Network Connections list. (This relates specifically to my Intel
>Anypoint II Wireless system.)
>
>The readings for the WNC3 on my XP server (host) are:
>
>Physical Address: 00-90-4B-05-5F-D9
>IP Address: 169.254.57.22
>Subnet Mask: 255.255.0.0
>Default Gateway:
>DNS Server:
>WINS Server:
>
>These are the Winipcfg details from my Me client machine:
>
>Host Name: FRONT-COMPUTER
>DNS Servers:
>Node Type: Broadcast
>NetBIOS Scope ID:
>IP Routing Enabled (unchecked)
>WINS Proxy Enabled (unchecked)
>NetBIOS Resolution Uses DNS (unchecked)
>Adapter Address: 00-90-4B-05-51-B5
>IP Autoconfiguration Address: 169.254.74.65
>Subnet Mask: 255.255.0.0
>Default Gateway:
>DHCP Server: 255.255.255.255
>Primary WINS Server:
>Secondary WINS Server:
>Lease Obtained: 05 25 03 10:43:24 AM
>Lease Expires:
>
>Pinging each machine from the other is fine using the respective
>169.254.57.22 and 169.254.74.65 IP addresses.
>
>Pinging 216.239.39.100 and www.google.com from the XP HOST (server) is
>also OK.
>
>However, pinging 216.239.39.100 and www.google.com from the Me CLIENT
>produces the respective responses "Destination host unreachable" and
>"unknown host".
>
>Network-wise, I have complete file access both ways. It's only
>internet access (and of course, the e-mail facility) that's
>unavailable to the Me client.
>
>I hope this is helpful to you, and that you can suggest how and where
>my client machine is wrongly configured.
>
>Thanks again for replying.

The TCP/IP information that you gave shows no evidence of Internet
Connection Sharing being used. The Me client machine isn't configured
for Internet access at all.

If the Anypoint software has its own Internet sharing capability, you
can either attempt to get that to work, or un-install Anypoint's
Internet sharing software and use ICS.

To do the latter, enable ICS on the host computer's Internet
connection and configure the other computer as an ICS client.

Details here:

Windows XP Internet Connection Sharing
http://www.practicallynetworked.com/sharing/xp_ics
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Trevor Midgley
May 28th 03, 11:47 AM
Steve – thanks for the posting. I didn't mean to hassle, and I'm very
grateful for the support.

I've installed ICS on both my XP Host and Me client machines.
Everything went fine, but I still can't access the internet from the
Me client.

The good news however is that as well as the computers being able to
successfully ping each other with their new IP Addresses (192.168.0.1
and 192.168.0.76), I CAN now satisfactorily ping 216.239.39.100 from
the Me client. Google however still shows as "unknown host".

These are the new readings for LAN and Wireless Network Connection 3
on my XP host:

LAN:

Physical Address: 00-D0-59-EA-19-67
IP Address: 80.4.109.54
Subnet Mask: 255.255.255.0
Default Gateway: 80.4.109.254
DHCP Server: 62.252.64.21
Lease Obtained: 28/5/03 9:14:20 AM
Lease Expires: 28/5/03 10:56:59 PM
DNS Servers: 194.168.4.100, 194.168.8.100
WINS Server:

WNC3:

Physical Address: 00-90-4B-05-5F-D9
IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway:
DNS Server:
WINS Server:

The new Winipcfg details from my Me client are:

Host Information

Host Name: FRONT-COMPUTER.mshome.net
DNS Servers: 192.168.0.1
Node Type: Mixed
NetBIOS Scope Id:
IP Routing Enabled: (checked)
WINS Proxy Enabled: (unchecked)
NetBIOS Resolution Uses DNS: (unchecked)

Ethernet Adapter Information

AT76C503A USB 11Mps Network Adapter
Adapter Address: 00-90-4B-05-51-B5
IP Address: 192.168.0.76
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DHCP Server: 192.168.0.1
Primary WINS Server:
Secondary WINS Server:
Lease Obtained: 05 28 03 11:07:57 AM
Lease Expires: 06 04 03 11:07:57 AM

As before, I still have complete file access both ways.

I think we're getting a bit nearer, but any further thoughts or advice
will be very welcome.

Thanks again.


****************


Steve Winograd > wrote in message >...
> In article >,
> (Trevor Midgley) wrote:
> >I hope I'm not contravening etiquette here!
> >
> >A few days ago, Steve Winograd kindly responded to a problem that I'm
> >having with Internet access on my home network.
> >
> >I posted a follow-up, but I think it got lost in the traffic.
> >
> >Anyway, this is a repeat post of my last message which I hope someone
> >can help me with.
> >
> >Thanks.
>
> I've flagged your previous message, Trevor, but I just haven't had
> time to get back to it.
>
> >**************
> >
> >Steve ? thanks for the reply.
> >
> >I'm pretty sure I'm using XP's ICS ? Intel's help desk sort of took
> >over when I first installed the system and removed their ISS software.
> >
> >I'm not connected via the Local Area Connection, but via a connection
> >called Wireless Network Connection 3 immediately below LAC in the
> >Network Connections list. (This relates specifically to my Intel
> >Anypoint II Wireless system.)
> >
> >The readings for the WNC3 on my XP server (host) are:
> >
> >Physical Address: 00-90-4B-05-5F-D9
> >IP Address: 169.254.57.22
> >Subnet Mask: 255.255.0.0
> >Default Gateway:
> >DNS Server:
> >WINS Server:
> >
> >These are the Winipcfg details from my Me client machine:
> >
> >Host Name: FRONT-COMPUTER
> >DNS Servers:
> >Node Type: Broadcast
> >NetBIOS Scope ID:
> >IP Routing Enabled (unchecked)
> >WINS Proxy Enabled (unchecked)
> >NetBIOS Resolution Uses DNS (unchecked)
> >Adapter Address: 00-90-4B-05-51-B5
> >IP Autoconfiguration Address: 169.254.74.65
> >Subnet Mask: 255.255.0.0
> >Default Gateway:
> >DHCP Server: 255.255.255.255
> >Primary WINS Server:
> >Secondary WINS Server:
> >Lease Obtained: 05 25 03 10:43:24 AM
> >Lease Expires:
> >
> >Pinging each machine from the other is fine using the respective
> >169.254.57.22 and 169.254.74.65 IP addresses.
> >
> >Pinging 216.239.39.100 and www.google.com from the XP HOST (server) is
> >also OK.
> >
> >However, pinging 216.239.39.100 and www.google.com from the Me CLIENT
> >produces the respective responses "Destination host unreachable" and
> >"unknown host".
> >
> >Network-wise, I have complete file access both ways. It's only
> >internet access (and of course, the e-mail facility) that's
> >unavailable to the Me client.
> >
> >I hope this is helpful to you, and that you can suggest how and where
> >my client machine is wrongly configured.
> >
> >Thanks again for replying.
>
> The TCP/IP information that you gave shows no evidence of Internet
> Connection Sharing being used. The Me client machine isn't configured
> for Internet access at all.
>
> If the Anypoint software has its own Internet sharing capability, you
> can either attempt to get that to work, or un-install Anypoint's
> Internet sharing software and use ICS.
>
> To do the latter, enable ICS on the host computer's Internet
> connection and configure the other computer as an ICS client.
>
> Details here:
>
> Windows XP Internet Connection Sharing
> http://www.practicallynetworked.com/sharing/xp_ics
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com

Steve Winograd
May 28th 03, 12:06 PM
In article >,
(Trevor Midgley) wrote:
>Steve – thanks for the posting. I didn't mean to hassle, and I'm very
>grateful for the support.
>
>I've installed ICS on both my XP Host and Me client machines.
>Everything went fine, but I still can't access the internet from the
>Me client.
>
>The good news however is that as well as the computers being able to
>successfully ping each other with their new IP Addresses (192.168.0.1
>and 192.168.0.76), I CAN now satisfactorily ping 216.239.39.100 from
>the Me client. Google however still shows as "unknown host".
>
>These are the new readings for LAN and Wireless Network Connection 3
>on my XP host:
>
>LAN:
>
>Physical Address: 00-D0-59-EA-19-67
>IP Address: 80.4.109.54
>Subnet Mask: 255.255.255.0
>Default Gateway: 80.4.109.254
>DHCP Server: 62.252.64.21
>Lease Obtained: 28/5/03 9:14:20 AM
>Lease Expires: 28/5/03 10:56:59 PM
>DNS Servers: 194.168.4.100, 194.168.8.100
>WINS Server:
>
>WNC3:
>
>Physical Address: 00-90-4B-05-5F-D9
>IP Address: 192.168.0.1
>Subnet Mask: 255.255.255.0
>Default Gateway:
>DNS Server:
>WINS Server:
>
>The new Winipcfg details from my Me client are:
>
>Host Information
>
>Host Name: FRONT-COMPUTER.mshome.net
>DNS Servers: 192.168.0.1
>Node Type: Mixed
>NetBIOS Scope Id:
>IP Routing Enabled: (checked)
>WINS Proxy Enabled: (unchecked)
>NetBIOS Resolution Uses DNS: (unchecked)
>
>Ethernet Adapter Information
>
>AT76C503A USB 11Mps Network Adapter
>Adapter Address: 00-90-4B-05-51-B5
>IP Address: 192.168.0.76
>Subnet Mask: 255.255.255.0
>Default Gateway: 192.168.0.1
>DHCP Server: 192.168.0.1
>Primary WINS Server:
>Secondary WINS Server:
>Lease Obtained: 05 28 03 11:07:57 AM
>Lease Expires: 06 04 03 11:07:57 AM
>
>As before, I still have complete file access both ways.
>
>I think we're getting a bit nearer, but any further thoughts or advice
>will be very welcome.
>
>Thanks again.

Those settings all look right to me, Trevor. I think that we're
getting close. Everything except DNS name resolution seems to be
working.

On the client, run Internet Explorer and go to Tools | Internet
Options | Connections | LAN Settings. If there are any boxes checked,
clear them, reboot, and try Internet access again.

If that doesn't help, try configuring the client's TCP/IP settings
manually:

IP Address: 192.168.0.x (1<x<255)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Servers = Your ISP's DNS servers, which the host shows as
194.168.4.100 and 194.168.8.100
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Trevor Midgley
May 29th 03, 12:09 PM
Steve – thanks again for your thoughts.

There were a couple of boxes checked on my Me client's IE / Tools /
Internet Options / Connections / LAN Settings. I unchecked them,
rebooted, but no joy I'm afraid.

I've configured manually as you suggested. Again, unfortunately, it
didn't seem to make any difference. I still can't get online from my
Me client. However, I can still ping 216.239.39.100!

These are the new readings for LAN and Wireless Network Connection 3
on my XP host (only the "Lease Obtained" and "Lease Expires" details
have changed):

LAN:

Physical Address: 00-D0-59-EA-19-67
IP Address: 80.4.109.54
Subnet Mask: 255.255.255.0
Default Gateway: 80.4.109.254
DHCP Server: 62.252.64.21
Physical Address: 00-D0-59-EA-19-67
IP Address: 80.4.109.54
Subnet Mask: 255.255.255.0
Default Gateway: 80.4.109.254
DHCP Server: 62.252.64.21
Lease Obtained: 29/5/03 9:43:40 AM
Lease Expires: 30/5/03 7:11:26 AM
DNS Servers: 194.168.4.100, 194.168.8.100
WINS Server:

WNC3:

Physical Address: 00-90-4B-05-5F-D9
IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway:
DNS Server:
WINS Server:

The updated Winipcfg details from my Me client are:

Host Information

Host Name: BACK-COMPUTER.mshome.net
(was FRONT-COMPUTER.mshome.net. I've changed this because my XP (host)
machine is BACK-COMPUTER. I assume that this should be the "Host Name"
that shows up under "Host Information" on the Me client?)
DNS Servers: 194.168.4.100 (with a secondary as 194.168.8.100)
Node Type: Broadcast
NetBIOS Scope Id:
IP Routing Enabled: (checked)
WINS Proxy Enabled: (unchecked)
NetBIOS Resolution Uses DNS: (NOW CHECKED)

Ethernet Adapter Information

AT76C503A USB 11Mps Network Adapter
Adapter Address: 00-90-4B-05-51-B5
IP Address: 192.168.0.76
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DHCP Server: NOW BLANK (was 192.168.0.1)
Primary WINS Server:
Secondary WINS Server:
Lease Obtained:
Lease Expires:

One other thing: when I review the LAN Status on both machines, I see
0 Packets Sent, with just over 7300 Packets Received as I write. Is
the "0 Packets Sent" significant? (My Wireless NC3 connection shows
thousands of packets sent and received each way.)

As before, I still have complete file access both ways.

Sorry to be a pain, and thanks again.


********************


Steve Winograd > wrote in message >...
> In article >,
> (Trevor Midgley) wrote:
> >Steve ? thanks for the posting. I didn't mean to hassle, and I'm very
> >grateful for the support.
> >
> >I've installed ICS on both my XP Host and Me client machines.
> >Everything went fine, but I still can't access the internet from the
> >Me client.
> >
> >The good news however is that as well as the computers being able to
> >successfully ping each other with their new IP Addresses (192.168.0.1
> >and 192.168.0.76), I CAN now satisfactorily ping 216.239.39.100 from
> >the Me client. Google however still shows as "unknown host".
> >
> >These are the new readings for LAN and Wireless Network Connection 3
> >on my XP host:
> >
> >LAN:
> >
> >Physical Address: 00-D0-59-EA-19-67
> >IP Address: 80.4.109.54
> >Subnet Mask: 255.255.255.0
> >Default Gateway: 80.4.109.254
> >DHCP Server: 62.252.64.21
> >Lease Obtained: 28/5/03 9:14:20 AM
> >Lease Expires: 28/5/03 10:56:59 PM
> >DNS Servers: 194.168.4.100, 194.168.8.100
> >WINS Server:
> >
> >WNC3:
> >
> >Physical Address: 00-90-4B-05-5F-D9
> >IP Address: 192.168.0.1
> >Subnet Mask: 255.255.255.0
> >Default Gateway:
> >DNS Server:
> >WINS Server:
> >
> >The new Winipcfg details from my Me client are:
> >
> >Host Information
> >
> >Host Name: FRONT-COMPUTER.mshome.net
> >DNS Servers: 192.168.0.1
> >Node Type: Mixed
> >NetBIOS Scope Id:
> >IP Routing Enabled: (checked)
> >WINS Proxy Enabled: (unchecked)
> >NetBIOS Resolution Uses DNS: (unchecked)
> >
> >Ethernet Adapter Information
> >
> >AT76C503A USB 11Mps Network Adapter
> >Adapter Address: 00-90-4B-05-51-B5
> >IP Address: 192.168.0.76
> >Subnet Mask: 255.255.255.0
> >Default Gateway: 192.168.0.1
> >DHCP Server: 192.168.0.1
> >Primary WINS Server:
> >Secondary WINS Server:
> >Lease Obtained: 05 28 03 11:07:57 AM
> >Lease Expires: 06 04 03 11:07:57 AM
> >
> >As before, I still have complete file access both ways.
> >
> >I think we're getting a bit nearer, but any further thoughts or advice
> >will be very welcome.
> >
> >Thanks again.
>
> Those settings all look right to me, Trevor. I think that we're
> getting close. Everything except DNS name resolution seems to be
> working.
>
> On the client, run Internet Explorer and go to Tools | Internet
> Options | Connections | LAN Settings. If there are any boxes checked,
> clear them, reboot, and try Internet access again.
>
> If that doesn't help, try configuring the client's TCP/IP settings
> manually:
>
> IP Address: 192.168.0.x (1<x<255)
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.0.1
> DNS Servers = Your ISP's DNS servers, which the host shows as
> 194.168.4.100 and 194.168.8.100
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com

Trevor Midgley
May 29th 03, 03:12 PM
Steve – excellent news! I've got my internet connection working from
the Me client!

In desperation, I ran the Me Networking Wizard from the CLIENT machine
– lying, I guess, on top of all the manual configurations and the
setup that XP put on the system from the server end. And it worked!!

Many thanks for your patience and advice. Maybe there are lessons in
this somewhere, but I'm going to have to work out what and where!

Thanks again.

(PS: this is coming to you from the erstwhile-errant client!)

Steve Winograd
May 29th 03, 05:23 PM
In article >,
(Trevor Midgley) wrote:
>Steve – excellent news! I've got my internet connection working from
>the Me client!
>
>In desperation, I ran the Me Networking Wizard from the CLIENT machine
>– lying, I guess, on top of all the manual configurations and the
>setup that XP put on the system from the server end. And it worked!!
>
>Many thanks for your patience and advice. Maybe there are lessons in
>this somewhere, but I'm going to have to work out what and where!
>
>Thanks again.
>
>(PS: this is coming to you from the erstwhile-errant client!)

Excellent news, indeed, Trevor. I'm glad that I was able to help and
that you found the final step. Thanks for letting the news group
know.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Google