[denimknight]

Hi all,

New to the forum, but it seems pretty good.

I'm having a problem connecting my computer to my network. I have a desktop machine running Windows XP home, it is using a Belkin F5D7000 version 3 wireless card.

I have installed the card and it has detected my network, but I am unable to access the internet. I have 2 laptops on the network which can access fine, the laptops have Network Magic running on them which is not seeing the desktop machine at all. Also the desktop machine has no IP address assigned to it.

But the computer is telling me that is connected fine with an excellent connection strength... I'm so confused! Never had this before, usually once it says it's on the network everything is fine, but not this time!

Hope someone can help!

Cheers

Alex

[Carbon]

Sounds like the router's DHCP just isn't configured correctly, while it's odd that it happens only on the desktop, it doesn't sound like a hardware issue on the desktop if it's not handing out IPs.

[denimknight]

Hi Carbon,

Thanks for the reply.

Would it be the DHCP on the router when the two laptops, the Wii and a notebook can all access fine? How do I check if this is problem (and is it an easy thing to fix?).

Also when I log into the router and go into the DHCP client list doesn't show the desktop machine either. Although it showing everything else. When I go into the LAN settings it has the following config:

IP address: 192.168.2.1
Subnet mask: 255.255.255.0
DHCP server is set to on

IP pool starting address is 192.168.2.2
IP pool ending address is 192.168.2.100
Lease time is set to Forever

The router is a Belkin.

Hope you can help.

Thanks

Alex

[Carbon]

Huh, settings sound fine too. I assume you've done an /ipconfig release then an /ipconfig renew on it?

[denimknight]

Hi Carbon,

I've tried renew / release with the following results:
---------------------------------------------
First I did an ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : AlexDesktop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-0E-A6-57-51-92

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Belkin 802.11g Wireless Card
Physical Address. . . . . . . . . : 00-11-50-66-4F-8C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.29.204
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

then I ran ipconfig /releas:


Windows IP Configuration

No operation can be performed on Local Area Connection while it has its media disconnected.

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.29.204
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

And finally an ipconfig /renew:

Windows IP Configuration

No operation can be performed on Local Area Connection while it has its media disconnected.
An error occurred while renewing interface Wireless Network Connection : unable to contact your DHCP server. Request has timed out.
---------------------------------------------
so it looks like it is some kind of problem with the DHCP, i just don't get why it's working for all the other devices!

Sometimes I hate computers! lol.

[Carbon]

Yep, that's a good question. Possible to rule out the connection by plugging it in via Ethernet temporarily? I have the feeling this is one of those things where it's some obscure router setting and you may have to dig around.

e: also, a ipconfig /all from the machine(s) that are working would be good as well

e2: oh, and it could be a stack issue, try the following in Run:

netsh int ip reset reset.log

netsh winsock reset catalog