wireless trouble

I have seen the posts on "limited or no connectivity "

My problem seems alike, yet different!!

For one i dont see that particular message.

I have a desktop at home (Emachines) running Win XP Home Edition, connected to the internet via ADSL

My Laptop (Fujitsu) runs Win XP Professional

When i hook up the two via a crossover cable all is well

Desktop shares its internet connection just fine.

I used to be able to do the same thing wireless

Alas no more.

Desktop has a Dlink wireless PCI card
Laptop has a built in Intersil Prism

both show that they are connected
both send packets, but dont receive any

the ip address on the laptop is in the 269 range (mask 255.255.0.0)

All other addresses (laptop and desktop) are in the 192 range (mask 255.255.255.0)

the laptop wireless adapter says at some stage: acquiring network address
it seems pretty obvious that it doesnt succeed!

so in short: crossover works fine, wireless doesnt

 

269 isn't within a valid TCP/IP address range. I expect the TCP/IP settings on the laptop have got corupted. Try setting the IP addresses for your wireless connection manually. I'd recommend using 10.0.0.0/255.255.0.0 addresses (so 10.0.0.1 and 10.0.0.2 for example) as you are already using the 192.168.0.0 space for the wired connection.

 

As noted, an IP address starting with or containing 269 is impossible/invalid/etc.

If that was a typo and the address starts with 169.x.x.x with a subnet mask of 255.255.0.0 then you have an address assigned by the OS when it looked for a DHCP server to give it an address and failed to find one. An address in that range was assigned so the PC could boot up and run but basically, it didn't see a network.

To save some time and lots of Q&A back and forth, please do the following and paste the contents of the text files you create into a reply here - making sure we can figure out which machine generated what data.

start->run->cmd and OK
ipconfig /all > c:\ipconfig.txt note spaces before /all and before-after >

 

wireless

Thanks Newt,

sorry for not getting back to u earlier. I took the easy way out and bought a new adslmodem/wireless router. Problem therefore solved. U were right abt the address being 169 and right about the laptop not finding the DHCP server.
What i still dont get is why it failed to see the DHCP server.

 

I'm not up to speed on wireless so don't even want to take a stab at why the machine couldn't see the DHCP server. Glad to hear the new router fixed you up though.

 

My experiences has been that when the client cant receive a DHCP managed address over the wireless is when WEP is turned on and an inproper key was entered.

It may also show "Limited or No Connectivity ".

For some unknown reason to me You are Not notified when an improper key is entered.