Wireless Router Connection Problem

Hewlett-packard / 2140
April 10, 2009 at 08:02:03
Specs: Windows XP Home, Atom
I was able to connect a XP Home client with a Belkin N+ wireless router. Although connection is made, the XP Home client cannot browse interent through the Router gateway. It appears that no packet can be received from the router. In addition, I changed the connection of the XP Home client with the router by using a direct wire. Internet can be browsed successfully with this setup. It can be concluded that the problem was not caused by WAN setup of the router.
Please assist.

See More: Wireless Router Connection Problem

Report •


#1
April 10, 2009 at 08:40:13
It sounds like the wireless adapter isn't getting an IP address. Run ipconfig /all from a command prompt & post the results.

Report •

#2
April 10, 2009 at 08:58:23
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\PXM>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : LS-HP2140
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter LAN 2:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Marvell Yukon 88E8072 PCI-E Gigabit
Ethernet Controller
Physical Address. . . . . . . . . : 00-24-81-55-30-CD

Ethernet adapter WiFi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 4322AG 802.11a/b/g/draft-n
Wi-Fi Adapter
Physical Address. . . . . . . . . : 00-21-00-BF-03-D0
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.11.106
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.11.2
DNS Servers . . . . . . . . . . . : 192.168.11.2


Report •

#3
April 10, 2009 at 09:28:32
Now do a ipconfig with just the wired connection that works and post it here.

Report •

Related Solutions

#4
April 10, 2009 at 09:56:05
Windows IP Configuration

Host Name . . . . . . . . . . . . : LS-HP2140
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8072 PCI-E Gigabit
Ethernet Controller
Physical Address. . . . . . . . . : 00-24-81-55-30-CD
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.11.107
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.11.2
DNS Servers . . . . . . . . . . . : 192.168.11.2

Ethernet adapter WiFi:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 4322AG 802.11a/b/g/draft-n
Wi-Fi Adapter
Physical Address. . . . . . . . . : 00-21-00-BF-03-D0


Report •

#5
April 10, 2009 at 10:52:41
excellent. Both look correct and functional.

Did you set up encryption on the wireless? I would suspect this is where the issue resides.

You can test by having no encryption at either end.

The weakness in wireless encryption is getting a common encryption protocol between devices. For example the wireless card may only support wpa whereas the router supports wpa2. Start by finding a protocol that both router and wireless nic have in common.

You also appear to be doing static assignments. Make sure the wireless is not set for dhcp as this can cause issues also.


Report •


Ask Question