I have tried to access my home network from my desktop both with and without wires. Although it can see the wireless connection (USB) and the router can see it, I am unable to connect or to ping the router from the machine. The other machines on the network are all working perfectly.
According to both ipconfig and the status section on the router (accessed through another computer), the failing machine is connected as 192.168.1.68
Any ideas?

ipconfig /all
=============

Windows IP Configuration

Host Name . . . . . . . . . . . . : alexande-cueg3q
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Ethernet adapter Local Area Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit
Ethernet NIC
Physical Address. . . . . . . . . : 00-11-09-CD-75-72

Ethernet adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : D-Link AirPlus G DWL-G122 Wireless U
SB Adapter(rev.C)
Physical Address. . . . . . . . . : 00-1B-11-BF-31-7C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : 22 November 2007 19:39:48
Lease Expires . . . . . . . . . . : 23 November 2007 19:39:48



Detected Devices report from router
==================================

BThomehub 192.168.1.254
Inactive Desktop AMCClaptop 192.168.1.67 Ethernet Interface unknown
Active Desktop AMCClaptop 192.168.1.66 WLAN Interface WLAN
Active Desktop alexande-cueg3q 192.168.1.68 WLAN Interface WLAN
Active Desktop melanie-laptop 192.168.1.65 WLAN Interfacem WLAN


Result of pinging
=================

C:\Documents and Settings\Alexander>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\Alexander>ping 192.168.1.68

Pinging 192.168.1.68 with 32 bytes of data:

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

Ping statistics for 192.168.1.68:
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\Alexander>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:

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

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

Hi Alexander

Welcome to WTT.

Sorry to hear about your network troubles.

If I read it right, the computer that is having the issue has two Network interface connectors. One is Ethernet and is unplugged and the other is a Wireless and shows connected.

You can try disabling the wireless connection and connecting a Ethernet cable and see if you can ping the Gateway then. I already suspect the problem lies with the Wireless adapter. Most likey software/configuration.

You can try uninstalling the wireless adaptor from Device manager and do a reboot and let Windows find it again. Making sure you unplug the Ethernet cable before doing the uninstalling and rebooting.

Once uninstalled and rebooted and windows has found the device, Go ahead and try opening a Browser and see if you get internet connectivity. Or go back and do the ipconfig /all routine from the command line and see what you get.

Regards

Kaz.

The wireless adapter is pulling proper DHCP information from the router.
The wired interface is disconnected, so under Automatic Metrics this would have an infinite cost. It is not a factor here.

A ping failure in almost all cases is a firewall issue.
Check that the router has not been configured to block Ping requests. Some will do this universally, on all subnets. Some only on the WAN interface.
Then it comes down to the firewall on the client.
Even the native XP firewall will block ICMP traffic. It will allow localhost (127.0.0.1) and it will allow its own IP address, but check your ICMP settings. You need to permit all ICMP traffic on your trusted subnet of 192.168.1.1 -- 192.168.1.254

If you ping the IP of other workstations, (e.g. 192.168.1.66) do you get a valid reply?

This post has been edited by Bill Castner: Nov 23 2007, 01:29 PM

Greetings Bill

Yes I do agree something is not allowing packets to go out to the gateway here. I was intending to see if the Eithernet Nic was behaving the same way.

If that works, then it would be the Wireless connection/software configuration involved. Looking to divide and conquer. Could be as simple as uninstalling the Wireless and reinstalling letting windows find it and manage the connection.

If that does not work, the next suspect for sure is firewall.

Nice to have you around!

Regards

Kaz