New wireless network, but get windows ip address every time 1

[rmhrc]

This is driving me mad!
I am trying to set up wireless internet on my laptop, which incidentally is on a freshly installed Windows XP Professional. I have a cable modem, to which I have connected and configured a DLink G650+ router, and with a Dlink DI-624+ wireless card plugged into my laptops cardbus slot.

I am 90% sure I have configured everything correctly (although this is the first time I've ever done this). The modem assigns the router an IP address fine - 80.*.*.*, but the problem is when the router tries to assign an IP to the laptop. Everytime, it gives it a Windows Ip address 169.*.*.* It seems that they are communicating with eachother, as the card detects the router.

For your information, both are set to WEP, with a network key to log on, and set to DHCP.

This is frustrating, as it's supposed to work 'out of the box' just via the Wizard, but this clearly is a load of codswallop. Please can anyone suggest something I can try?

 

[MTandSAV]

basically your router doesn't give out a ip addresses, otherwise you wouldn't get the 169.254.x.x address.
Best thing is to check the WEP and network key if they are identical, or remove them to see if the works without it.
Have you specified a dhcp pool on the router?

CCNA, CCNP..partly

 

[rmhrc]

I've tried it without the WEP and with, and network keys are definitely identical. The router has a DHCP pool specified on it too.

When I connect to the router via an Ethernet cable, it gives me an IP address fine (192.168.0.100), and I can access the internet no problem. So it's something to do with the routers communication with the wireless card.

 

[manarth]

My experience of trying to configure WiFi is a painstaking process of reinstalling, upgrading firmware, trying different windows configurations (e.g. using the windows Zero Configuration vs the manufacturer's app).

First of all, try it with WEP off. This will give you an indication if there is any connection.

Check also for an ACL (Access Control List) on the router. You may need to add your wireless MAC to the list.

<marc> i wonder what will happen if i press this...[ul][li]please tell us if our suggestion has helped[/li][li]need some help? faq581-3339[/li][/ul]

 

[vipergg]

Also make sure the SSID is identical . XP SP2 has caused all sorts of problems with wireless stuff . Does a wired connection thru the router work ok ? Most laptops have a wired nic builtin too . Most of the info i have seen says to turn off the windows zero config and use the makers nic utility . I wouldn't mess with the mac address filtering until you can connect then you can lock down your wireless network with mac address filtering . Haven't had the joy of using XP on wireless but Windows 2000 had no problem at all setting up wireless had it up in 15 minutes with SSID, 128 WEP and mac address filtering , been in a year now with zero problems . Using netgear "B" router and wireless nic . You might want to see if there is a more up to date driver for your wireless nic and even router . Usually these things do not ship with the later firmware and drivers.

 

[bcastner]

faq779-4625

Your Winsock stack is corrupted.

 

[rmhrc]

For your information, I managed to sort this out over the weekend. I actually discovered the winsock fix on another thread, which has cured it. Hallelujah! That was a most joyous moment - almost as joyous as Liverpool beating Arsenal this weekend.

Thanks for your help guys!

 

[TanTheMan]

Sorry for adding to this thread, but it seems to be the closest one to the problem I'm experiencing.

I've got a newly installed D-link 624+ router and installed a DWL-520+ card in my spare pc. When I use an 'open system' authentification, both pc's can see each other (WEP is enabled). But when I use the shared key option (key's are the same) it's like the connection isn't there. I've been trying to figure this out now for a couple of days and can't seem to get it working. Can anyone help here?

(apologies for adding my problem to this thread )

 

[cookieguy]

Ok, let me in on the secert, What's the link to the winsock fix? I've been messing with this for a week, on a linksys network that already has two PC that will connect. The third always reports a 169.*.*.* address and should be 192.168.1.* address.

Help me, I'm melting!

 

[bcastner]

WinsockFix links:
faq779-4625