[cornerstone]

What I am trying to do to is to have all all three computers in the same
wireless network.
I have two pcs and one notebook. All three are running on XP. Two pcs are in
the same Wired network. The notebook has Wireless network, standalone,
through the wirelss/wired router that is also connected to the above two
desktops via ethernet cables. All three have internet connection and are
working well.

I switched wired desktops to wireless. However internet connection is not
working after this change. Internection connection of the desktops after the
change works through the wired network though.

Here is what I have now.
A wirelss icon appeared at the corner of the screen (menu bar area?) as well
as the icon of wired network( a look of two pcs). Click the wireless icon to
find out the status of connection. It says it is connected. In the actvity
box, the packets of sent is something like 1850, but the packets in received
only 5. But the diagram showing the connection has a small ICON OF A LOCK in
the LOCKED position at the received side. I believe this lock in the locked
position tells the problem. Please help me.

[Ron Lowe]

"cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
news:748D862B-0A4E-4CC0-AE2A-503F840603F2@microsoft.com...
> What I am trying to do to is to have all all three computers in the same
> wireless network.
> I have two pcs and one notebook. All three are running on XP. Two pcs are
> in
> the same Wired network. The notebook has Wireless network, standalone,
> through the wirelss/wired router that is also connected to the above two
> desktops via ethernet cables. All three have internet connection and are
> working well.
>
> I switched wired desktops to wireless. However internet connection is not
> working after this change. Internection connection of the desktops after
> the
> change works through the wired network though.
>
> Here is what I have now.
> A wirelss icon appeared at the corner of the screen (menu bar area?) as
> well
> as the icon of wired network( a look of two pcs). Click the wireless icon
> to
> find out the status of connection. It says it is connected. In the actvity
> box, the packets of sent is something like 1850, but the packets in
> received
> only 5. But the diagram showing the connection has a small ICON OF A LOCK
> in
> the LOCKED position at the received side. I believe this lock in the
> locked
> position tells the problem. Please help me.
>


The lock icon indicates that the firewall is active on that connection.
I would normally expect this to be on.

This should not block Internet connectivity, since the firewall
will always permit return traffic from any connection you initiate.

Since you are behind a router, it is safe enough to turn off the
firewall as a test, to see if anything changes.

The fact that the wireless properties show it is connected suggests that the
wireless card associated with the access point and any WPA or WEP keys are
OK, but it's worth double-checking these.

The first diagnostic test I'd do is to go to a command prompt and issue the
command:

ipconfig /all

and determine that the wireless connection has picked up a correct IP
address, subnet mask, and default gateway from the wireless router.
Compare these to the working laptop.

Is the router doing any MAC filtering, perhaps, and you need to add the new
wireless desktops to the permitted list?

--
Best Regards
Ron Lowe
MVP - Windows Networking

[cornerstone]

"cornerstone" wrote:

> What I am trying to do is to have all all three computers in the same
> wireless network.
> I have two pcs and one notebook. All three are running on XP. Two pcs are in
> the same Wired network. The notebook has Wireless network, standalone,
> through the wirelss/wired router that is also connected to the above two
> desktops via ethernet cables. All three have internet connection and are
> working well.
>
> I switched wired desktops to wireless. However internet connection is not
> working after this change. Internet connection of the desktops after the
> change works through the wired network though.
>
> Here is what I have now.
> A wirelss icon appeared at the corner of the screen (menu bar area?) as well
> as the icon of wired network( a look of two pcs). Click the wireless icon to
> find out the status of connection. It says it is connected. In the actvity
> box, the packets of sent is something like 1850, but the packets in received
> only 5. But the diagram showing the connection has a small ICON OF A LOCK in
> the LOCKED position at the received side. I believe this lock in the locked
> position tells the problem. Please help me.
>

[cornerstone]

Hi, so far the first test suggested, "ipconfig /all " is not working even
after the firewall was removed. Thanks for the reply

"Ron Lowe" wrote:

> "cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
> news:748D862B-0A4E-4CC0-AE2A-503F840603F2@microsoft.com...
> > What I am trying to do to is to have all all three computers in the same
> > wireless network.
> > I have two pcs and one notebook. All three are running on XP. Two pcs are
> > in
> > the same Wired network. The notebook has Wireless network, standalone,
> > through the wirelss/wired router that is also connected to the above two
> > desktops via ethernet cables. All three have internet connection and are
> > working well.
> >
> > I switched wired desktops to wireless. However internet connection is not
> > working after this change. Internection connection of the desktops after
> > the
> > change works through the wired network though.
> >
> > Here is what I have now.
> > A wirelss icon appeared at the corner of the screen (menu bar area?) as
> > well
> > as the icon of wired network( a look of two pcs). Click the wireless icon
> > to
> > find out the status of connection. It says it is connected. In the actvity
> > box, the packets of sent is something like 1850, but the packets in
> > received
> > only 5. But the diagram showing the connection has a small ICON OF A LOCK
> > in
> > the LOCKED position at the received side. I believe this lock in the
> > locked
> > position tells the problem. Please help me.
> >
>
>
> The lock icon indicates that the firewall is active on that connection.
> I would normally expect this to be on.
>
> This should not block Internet connectivity, since the firewall
> will always permit return traffic from any connection you initiate.
>
> Since you are behind a router, it is safe enough to turn off the
> firewall as a test, to see if anything changes.
>
> The fact that the wireless properties show it is connected suggests that the
> wireless card associated with the access point and any WPA or WEP keys are
> OK, but it's worth double-checking these.
>
> The first diagnostic test I'd do is to go to a command prompt and issue the
> command:
>
> ipconfig /all
>
> and determine that the wireless connection has picked up a correct IP
> address, subnet mask, and default gateway from the wireless router.
> Compare these to the working laptop.
>
> Is the router doing any MAC filtering, perhaps, and you need to add the new
> wireless desktops to the permitted list?
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
>

[Ron Lowe]

"cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
news:0A15E185-C133-433B-94EE-33C3B1080F87@microsoft.com...
> Hi, so far the first test suggested, "ipconfig /all " is not working even
> after the firewall was removed. Thanks for the reply
>



What do you mean it's not working?
What happens when you type it?
Do you get an error, if so what error?

You need to do it from a command prompt window, not from start | run.


It should give a report like this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ron.HOMENET>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : rons-pc-2
Primary Dns Suffix . . . . . . . : homenet.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : homenet.local
homenet.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : homenet.local
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-0F-EA-8C-7B-77
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 81.187.191.70
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 81.187.191.65
DHCP Server . . . . . . . . . . . : 81.187.191.78
DNS Servers . . . . . . . . . . . : 81.187.191.78
Primary WINS Server . . . . . . . : 81.187.191.78
Lease Obtained. . . . . . . . . . : 17 June 2005 07:26:07
Lease Expires . . . . . . . . . . : 25 June 2005 07:26:07




--
Best Regards
Ron Lowe
MVP - Windows Networking

[cornerstone]

Hi,
What I mean by "not working"is that internet connection cannot be made
through wireless even though it is connected.

What I got from the command is basically the same as your example.
However,under Windows IP configuration, Primary DNS Suffix is Blank.
Primary Dns Suffix . . . . . . . . :
DNS Suffix Search List . . . . . :WorkGroup
Work Group, repeated

Under Ethernet adapter Wireless;

The difference from your example are:
Two IP addresses listed and in DNS servers, additional addresses follows.
IP address. . . . . : 192.168.0.20
Subnet Mask. . . .:255.255.2555.0
IP address. . . . . :fe80::20d:3aff:fe26:fef9%5
Defualt Gateway . . . . 192.168.0.1
DHCP Server. . . . . . . 192.168.0.1
DNS Servers. . . . . . . 192.168.0.1
fec0:0:0:ffff::1%1

However there is no difference between "Ethernet adapter Wireless" and
"Ethernet adapter MSHOME" which is the working wired network.
Also my working wireless notebook ipconfigure shows the same the blank in
"Primary Dns Suffix".

Another difference from your example is;

There are additional sets of message after "Lease expires";

"Tunnel adapter Toredo Tunneling Pseudo-Interface"

Please response.

Best Regards,
Cornerstone


"Ron Lowe" wrote:

> "cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
> news:0A15E185-C133-433B-94EE-33C3B1080F87@microsoft.com...
> > Hi, so far the first test suggested, "ipconfig /all " is not working even
> > after the firewall was removed. Thanks for the reply
> >
>
>
>
> What do you mean it's not working?
> What happens when you type it?
> Do you get an error, if so what error?
>
> You need to do it from a command prompt window, not from start | run.
>
>
> It should give a report like this:
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\Ron.HOMENET>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : rons-pc-2
> Primary Dns Suffix . . . . . . . : homenet.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : homenet.local
> homenet.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : homenet.local
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet
> Physical Address. . . . . . . . . : 00-0F-EA-8C-7B-77
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 81.187.191.70
> Subnet Mask . . . . . . . . . . . : 255.255.255.240
> Default Gateway . . . . . . . . . : 81.187.191.65
> DHCP Server . . . . . . . . . . . : 81.187.191.78
> DNS Servers . . . . . . . . . . . : 81.187.191.78
> Primary WINS Server . . . . . . . : 81.187.191.78
> Lease Obtained. . . . . . . . . . : 17 June 2005 07:26:07
> Lease Expires . . . . . . . . . . : 25 June 2005 07:26:07
>
>
>
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
>

[Ron Lowe]

"cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
news:9743302D-FB8C-43C5-A3FA-910FC58A17A9@microsoft.com...
> Hi,
> What I mean by "not working"is that internet connection cannot be made
> through wireless even though it is connected.
>
> What I got from the command is basically the same as your example.
> However,under Windows IP configuration, Primary DNS Suffix is Blank.
> Primary Dns Suffix . . . . . . . . :
> DNS Suffix Search List . . . . . :WorkGroup
> Work Group, repeated
>
> Under Ethernet adapter Wireless;
>
> The difference from your example are:
> Two IP addresses listed and in DNS servers, additional addresses follows.
> IP address. . . . . : 192.168.0.20
> Subnet Mask. . . .:255.255.2555.0
> IP address. . . . . :fe80::20d:3aff:fe26:fef9%5
> Defualt Gateway . . . . 192.168.0.1
> DHCP Server. . . . . . . 192.168.0.1
> DNS Servers. . . . . . . 192.168.0.1
> fec0:0:0:ffff::1%1
>
> However there is no difference between "Ethernet adapter Wireless" and
> "Ethernet adapter MSHOME" which is the working wired network.
> Also my working wireless notebook ipconfigure shows the same the blank in
> "Primary Dns Suffix".
>
> Another difference from your example is;
>
> There are additional sets of message after "Lease expires";
>
> "Tunnel adapter Toredo Tunneling Pseudo-Interface"
>
> Please response.
>
> Best Regards,
> Cornerstone
>




OK, now we have some detail to work with.
'Basically the same' is not good enough, the reason I asked for the results
of the command in the first place is because it's all down to the details.
There's enough detail here to work with.

It seems the machine is picking up correct IP configuration, which is
something.

I see you have IPv6 installed.
Whilst that should not cause a problem, it sometimes appears to.
So I'd simplify your configuration by un-installing IPv6 for the time being.

We need to do some further tests now.

Issuue each of these commands, and report which works and which does not:

ping 127.0.0.1
ping 192.168.0.20
ping 192.168.0.1
ping 66.249.87.104
ping www.google.com

each of these tests a step further, and will point us to what the problem
is.
If you get an error from these tests, we need to know the **exact** error
message.

--
Best Regards
Ron Lowe
MVP - Windows Networking

[cornerstone]

Hi,

I tried to ping all five addresses with WIRELESS connection while it says "
status;connected", "signal strength; excellent".
But none of them were successful.
While searching the sites, at the bottom of the page, it says "opening page
......., and the wireless icon flashes waves periodically. Several minutes
later, the page goes blank. The progress indicator bar shows one or two green
strips at the end.
FYI, also the MSN messenger icon was flashing, indicating an attempt to
connect.

However, with the working wired desktop, the first three addresses
(127.0.0.1, 192.168.0.20, 192.168.0.1) were "not found", and the last two
were successful.

I do not know how to deinstall IPv6. Please let me know.

Best Regards,
Cornerstone.





"Ron Lowe" wrote:

> "cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
> news:9743302D-FB8C-43C5-A3FA-910FC58A17A9@microsoft.com...
> > Hi,
> > What I mean by "not working"is that internet connection cannot be made
> > through wireless even though it is connected.
> >
> > What I got from the command is basically the same as your example.
> > However,under Windows IP configuration, Primary DNS Suffix is Blank.
> > Primary Dns Suffix . . . . . . . . :
> > DNS Suffix Search List . . . . . :WorkGroup
> > Work Group, repeated
> >
> > Under Ethernet adapter Wireless;
> >
> > The difference from your example are:
> > Two IP addresses listed and in DNS servers, additional addresses follows.
> > IP address. . . . . : 192.168.0.20
> > Subnet Mask. . . .:255.255.2555.0
> > IP address. . . . . :fe80::20d:3aff:fe26:fef9%5
> > Defualt Gateway . . . . 192.168.0.1
> > DHCP Server. . . . . . . 192.168.0.1
> > DNS Servers. . . . . . . 192.168.0.1
> > fec0:0:0:ffff::1%1
> >
> > However there is no difference between "Ethernet adapter Wireless" and
> > "Ethernet adapter MSHOME" which is the working wired network.
> > Also my working wireless notebook ipconfigure shows the same the blank in
> > "Primary Dns Suffix".
> >
> > Another difference from your example is;
> >
> > There are additional sets of message after "Lease expires";
> >
> > "Tunnel adapter Toredo Tunneling Pseudo-Interface"
> >
> > Please response.
> >
> > Best Regards,
> > Cornerstone
> >
>
>
>
>
> OK, now we have some detail to work with.
> 'Basically the same' is not good enough, the reason I asked for the results
> of the command in the first place is because it's all down to the details.
> There's enough detail here to work with.
>
> It seems the machine is picking up correct IP configuration, which is
> something.
>
> I see you have IPv6 installed.
> Whilst that should not cause a problem, it sometimes appears to.
> So I'd simplify your configuration by un-installing IPv6 for the time being.
>
> We need to do some further tests now.
>
> Issuue each of these commands, and report which works and which does not:
>
> ping 127.0.0.1
> ping 192.168.0.20
> ping 192.168.0.1
> ping 66.249.87.104
> ping www.google.com
>
> each of these tests a step further, and will point us to what the problem
> is.
> If you get an error from these tests, we need to know the **exact** error
> message.
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
>

[Ron Lowe]

"cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
news:8F7FEFEB-737A-472B-9AE2-72403D14F0F9@microsoft.com...
> Hi,
>
> I tried to ping all five addresses with WIRELESS connection while it says
> "
> status;connected", "signal strength; excellent".
> But none of them were successful.
> While searching the sites, at the bottom of the page, it says "opening
> page
> ......, and the wireless icon flashes waves periodically. Several minutes
> later, the page goes blank. The progress indicator bar shows one or two
> green
> strips at the end.
> FYI, also the MSN messenger icon was flashing, indicating an attempt to
> connect.
>
> However, with the working wired desktop, the first three addresses
> (127.0.0.1, 192.168.0.20, 192.168.0.1) were "not found", and the last two
> were successful.
>
> I do not know how to deinstall IPv6. Please let me know.
>
> Best Regards,
> Cornerstone.
>
>



OK, we need to do this one more time.
I dont think you did the pings right.
'not found' is not a response I've ever seen from a ping.
It looks to me like you typed the numbers into a web browser.
We're not using a browser here, we need a command prompt window.

To open a command prompt window, go to:
Start | Run | type cmd in the box, and hit enter.

In the command prompt window that comes up,
re-enter the ping commands, like this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ron.HOMENET>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Ron.HOMENET>


If the ping works, you get 4 replies like the above.
If the ping fails, you get various errors, like these:

C:\Documents and Settings\Ron.HOMENET>ping 81.187.191.71

Pinging 81.187.191.71 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 81.187.191.71:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

That is a timeout, the machine failed to respond to the ping.

Heres another error:

C:\Documents and Settings\Ron.HOMENET>ping no-such
Ping request could not find host no-such. Please check the name and try
again.

This is a name resolution failure. The computer name "no-such" could not be
resolved to an IP address to ping.

The ping responses to the questions I gave tell us a lot about what is
working and what is not, and where the fault lies.


To un-install IPv6:
R-click My Network places | Properties.
R-click your LAN connection | Properties;
Scroll down the list of items and select MS TCP/IP version 6
Click uninstall.


--
Best Regards
Ron Lowe
MVP - Windows Networking

[cornerstone]

Hi,
Thanks for your patience and kindness.
I did not do the ping command correctly earlier.
Here is the result of ping.

"Reply from 127.0.0.1: bytes=32 time<1ms ttl=128
ping statistices for 127.0.0.1:
packets: sent=4, received=4,lost=0<0% loss>

The same results with 192.168.0.20 as above.

However, the results with 192.168.0.1 and 66.249.87.104 are the same, but no
reply;
"request timed out" repeated four times
packet: sent=4, received=0, lost=4 <100%>

Results with www.google.com
"It says that ping request could not find host www.google.com.
Please check the nand and try again."

Uninstall of IPv6 did not do any good. This morning after reboot, the IPV6
was recheck by itself.

One other thing which is somehting new is that I was not able to "reply"
because of the error message "pages cannot be displayed" when I tried to
"reply" and "sign in".
All other sites have no problems at all. Strange.
Now I write this reply from my notebook.

Thanks a lot.

Best regards,
Cornerstone

"Ron Lowe" wrote:

> "cornerstone" <cornerstone@discussions.microsoft.com> wrote in message
> news:8F7FEFEB-737A-472B-9AE2-72403D14F0F9@microsoft.com...
> > Hi,
> >
> > I tried to ping all five addresses with WIRELESS connection while it says
> > "
> > status;connected", "signal strength; excellent".
> > But none of them were successful.
> > While searching the sites, at the bottom of the page, it says "opening
> > page
> > ......, and the wireless icon flashes waves periodically. Several minutes
> > later, the page goes blank. The progress indicator bar shows one or two
> > green
> > strips at the end.
> > FYI, also the MSN messenger icon was flashing, indicating an attempt to
> > connect.
> >
> > However, with the working wired desktop, the first three addresses
> > (127.0.0.1, 192.168.0.20, 192.168.0.1) were "not found", and the last two
> > were successful.
> >
> > I do not know how to deinstall IPv6. Please let me know.
> >
> > Best Regards,
> > Cornerstone.
> >
> >
>
>
>
> OK, we need to do this one more time.
> I dont think you did the pings right.
> 'not found' is not a response I've ever seen from a ping.
> It looks to me like you typed the numbers into a web browser.
> We're not using a browser here, we need a command prompt window.
>
> To open a command prompt window, go to:
> Start | Run | type cmd in the box, and hit enter.
>
> In the command prompt window that comes up,
> re-enter the ping commands, like this:
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\Ron.HOMENET>ping 127.0.0.1
>
> Pinging 127.0.0.1 with 32 bytes of data:
>
> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
>
> Ping statistics for 127.0.0.1:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> C:\Documents and Settings\Ron.HOMENET>
>
>
> If the ping works, you get 4 replies like the above.
> If the ping fails, you get various errors, like these:
>
> C:\Documents and Settings\Ron.HOMENET>ping 81.187.191.71
>
> Pinging 81.187.191.71 with 32 bytes of data:
>
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for 81.187.191.71:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> That is a timeout, the machine failed to respond to the ping.
>
> Heres another error:
>
> C:\Documents and Settings\Ron.HOMENET>ping no-such
> Ping request could not find host no-such. Please check the name and try
> again.
>
> This is a name resolution failure. The computer name "no-such" could not be
> resolved to an IP address to ping.
>
> The ping responses to the questions I gave tell us a lot about what is
> working and what is not, and where the fault lies.
>
>
> To un-install IPv6:
> R-click My Network places | Properties.
> R-click your LAN connection | Properties;
> Scroll down the list of items and select MS TCP/IP version 6
> Click uninstall.
>
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
>

[Ron Lowe]

> ipconfig /all:
> IP address. . . . . : 192.168.0.20
> Subnet Mask. . . .:255.255.2555.0
> IP address. . . . . :fe80::20d:3aff:fe26:fef9%5
> Defualt Gateway . . . . 192.168.0.1
> DHCP Server. . . . . . . 192.168.0.1
> DNS Servers. . . . . . . 192.168.0.1


> "Reply from 127.0.0.1: bytes=32 time<1ms ttl=128
> ping statistices for 127.0.0.1:
> packets: sent=4, received=4,lost=0<0% loss>
>
> The same results with 192.168.0.20 as above.
>
> However, the results with 192.168.0.1 and 66.249.87.104 are the same, but
> no
> reply;
> "request timed out" repeated four times
> packet: sent=4, received=0, lost=4 <100%>
>
> Results with www.google.com
> "It says that ping request could not find host www.google.com.
> Please check the nand and try again."
>

OK, so here's the core of the problem.

The wireless card has associated with the Access Point.
DHCP has worked, because you have picked up a valid lease.

You can ping your own IP address 192.168.0.20.

However, pings to the router ( 192.168.0.1 ) time out.
Pings to anything beyond the router time out too.
And hence name also resolution fails, because DNS servers are unreachable.

There is no connectivity beyond this machine.
Other clients can use the Access Point without problem.

At this point, I don't really know what the problem is.

It the IP address of 192.168.0.20 definately assigned to the wireless
adapter, not the wired one?
Is the wired cable un-plugged when you did these tests?

Just to be sure of something, can you copy-and-paste the output of the
command 'route print' into a reply?
In the command prompt window, enter the command 'route print'.
Expand the window as necessary to see it all.
Right-click in the window, and select 'Mark'.
Click and Drag the mouse over all the text till it all goes white.
Then hit 'Enter'.

Click the mouse in the reply window, and press Ctrl-V to paste it in.


--
Best Regards
Ron Lowe
MVP - Windows Networking

[cornerstone]

Hi, Ron,

Thanks again,
When I did ping test earlier, the wired cable was disconnected.
Now I did the same with the cable connected. This time the only difference
is that there was a ping with 66.249.87.104, However there is no ping with
192.168.0.1 ("request timed out" and and <100% lost>) which the same as the
cable disconnected.

One other thing is that after the command, there is an error message
"C:\PROGRA~1\sYMANTEC\s32evnt1.dll.
An installable virtual Device driver failed DLL initialization.
(close) (ignore)
I chose ignore and did ping test.
The above error message is not new one.

How do I know that the the IP 192.168.0.20 is assigned to wired or wireless?
And to which one should it be assigned?

Here is a copy of route print out.

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\HANK>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 07 e9 c1 36 74 ...... Intel(R) PRO/100 VE Network Connection -
Packet
Scheduler Miniport
0x30003 ...00 0d 3a 26 fe f9 ...... Microsoft Wireless PCI Adapter MN-730 -
Pack
et Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.20 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.20 192.168.0.20 30
192.168.0.20 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.0.255 255.255.255.255 192.168.0.20 192.168.0.20 30
224.0.0.0 240.0.0.0 192.168.0.20 192.168.0.20 30
255.255.255.255 255.255.255.255 192.168.0.20 2 1
255.255.255.255 255.255.255.255 192.168.0.20 192.168.0.20 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

C:\DOCUME~1\HANK>

While I communicate wtih you, I learned a few new things.

Thank you again,

Best personal regards,

Cornerstone


"Ron Lowe" wrote:

> > ipconfig /all:
> > IP address. . . . . : 192.168.0.20
> > Subnet Mask. . . .:255.255.2555.0
> > IP address. . . . . :fe80::20d:3aff:fe26:fef9%5
> > Defualt Gateway . . . . 192.168.0.1
> > DHCP Server. . . . . . . 192.168.0.1
> > DNS Servers. . . . . . . 192.168.0.1
>
>
> > "Reply from 127.0.0.1: bytes=32 time<1ms ttl=128
> > ping statistices for 127.0.0.1:
> > packets: sent=4, received=4,lost=0<0% loss>
> >
> > The same results with 192.168.0.20 as above.
> >
> > However, the results with 192.168.0.1 and 66.249.87.104 are the same, but
> > no
> > reply;
> > "request timed out" repeated four times
> > packet: sent=4, received=0, lost=4 <100%>
> >
> > Results with www.google.com
> > "It says that ping request could not find host www.google.com.
> > Please check the nand and try again."
> >
>
> OK, so here's the core of the problem.
>
> The wireless card has associated with the Access Point.
> DHCP has worked, because you have picked up a valid lease.
>
> You can ping your own IP address 192.168.0.20.
>
> However, pings to the router ( 192.168.0.1 ) time out.
> Pings to anything beyond the router time out too.
> And hence name also resolution fails, because DNS servers are unreachable.
>
> There is no connectivity beyond this machine.
> Other clients can use the Access Point without problem.
>
> At this point, I don't really know what the problem is.
>
> It the IP address of 192.168.0.20 definately assigned to the wireless
> adapter, not the wired one?
> Is the wired cable un-plugged when you did these tests?
>
> Just to be sure of something, can you copy-and-paste the output of the
> command 'route print' into a reply?
> In the command prompt window, enter the command 'route print'.
> Expand the window as necessary to see it all.
> Right-click in the window, and select 'Mark'.
> Click and Drag the mouse over all the text till it all goes white.
> Then hit 'Enter'.
>
> Click the mouse in the reply window, and press Ctrl-V to paste it in.
>
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
>