795 Posts

January 4th, 2004 11:00

dreampuzz,

The 169.254.xxx.xxx IP address is a Windows Auto Config address.  Windows assigns this when it cannot find a DHCP server on the network.  Your router is the DHCP server.  This indicates your PC is not communicating with the router.  Check the link lights on the PC's NIC and the router to make sure they are illuminated.  If they are not, there is no physical connection between the router and NIC and it need to be resolved.  If they are, the NIC may not be properly negotiating a connection speed with the router.  Open Device Manager and then the properties of the network adapter.  On the Advanced tab select the entry "Link Speed and Duplex" and change the setting from Auto Detect to 100 Full Duplex.  OK out and see if you have connectivity.  If not, try another speed/duplex setting.  Try them all if necessary.

Post back.

7 Posts

January 5th, 2004 12:00

erm .. sorry to bother u but i am using wireless so there is no "Link Speed and Duplex" .. other ways?

thanks for your help :)

795 Posts

January 5th, 2004 13:00

dreampuzz,

My mistake, sorry.

The wireless network adapter in question is not associating with the access point.  First thing to do is make sure you are using the latest available driver for the wireless adapter.  Make sure the adapter is configured for the correct SSID and if you are using encryption, the correct key.  If you are not broadcasting your SSID Windows Zero Config will not associate with the access point.  You can get around this by deselecting WZC and using the management utility that came with the wireless adapter.

It would help if you posted what PC, operating system, wireless adapter and access point we are dealing with. 

7 Posts

January 6th, 2004 13:00

i have two 2.4b P4 PC with quite similar configuration. both using XP. i have a ADSL modem that is connected to a linksys wireless router B. 2 linksys wireless USB to both the PC. And a Dell 600m centrino.

only 1 pc has the problem of not getting the IP. but with cable it just work instantly.

the funny thing is when i 1st receive my Dell last week it don't work as well. but after two days after i disable the wireless, i just turn it back on and it suddenly work fine.

thanks :)

2 Intern

 • 

12K Posts

January 6th, 2004 14:00

Wireless Checkpoints:

  1. SSID names must be the same and they are case sensitive
  2. If encryption is enabled, it must match those setttings on the router (check to see if a space is placed in front of an value causing an incorrect match (I've done that)

Disable the XP firewalls

Primary reasons why Windows XP and Windows 98/ME networks have trouble sharing resources:

1. Make sure all computers are in the same workgroup and have unique names on the network

2. Make sure all firewalls are disabled while setting up the network. In particular make sure that WinXP's built-in firewall is disabled on the local area connection.

3. Make sure NetBIOS over TCP/IP is enabled on all computers.

4. Make sure File and Printer Sharing is bound to only one protocol, preferably TCP/IP.

5. Make sure drives and/or folders have been designated as shared.

6. If the Windows 98/ME computers have Client for Microsoft Networks as the primary network logon, make sure that the proper username and password are entered when these machines boot. If Windows logon is the primary network logon, make sure that either a null password is used or that the correct password is used when booting these computers. Hitting the cancel button at the password prompt may prevent network connectivity.

(Credit goes to Forum Regular volcano11 for developing this check list.)

Message Edited by jmwills on 01-06-2004 12:53 PM

7 Posts

January 6th, 2004 14:00

no no all the wired cables to the PC are working fine ..

only the wireless connection has problem. only 1 particular PC cant locate the IP thru DHCP. no matter how many times i restart the computer and disable and renable the connection

2 Intern

 • 

12K Posts

January 6th, 2004 14:00

Check to see that one of the wired machines is wired into the uplink port on the router.  If so, that would disable the port next to it.  If that is the case, move the cable from the uplink port to another port.

795 Posts

January 6th, 2004 22:00

dreampuzz,

Which PC cannot associate with the router? One of the PCs with the WUSB11 or the 600m? 

I have had better luck using the Linksys control utility for the WUSB11 than WZC.  You can install the control utility separately, it is in the \utility folder on the WUSB11 CD and has its own setup program.  Install it and then configure the properties of the adapter to not use Windows to manage the adapter.  Then use the Linksys utility.

I have also had better luck using the Intel ProSet utility instead of WZC.  Make the same change to the properties if the adapter with the connection problem is Intel 2100.

7 Posts

January 7th, 2004 09:00

thanks for your advice :)

will try troubleshooting it

 

7 Posts

January 7th, 2004 09:00

one of the 2.4 PC with the WUSB11

but i install exactly the same way to the other 2.4 PC and it works

i even interchange it but it dun work ..

just dun understand y this particular PC dun pick up the DHCP IP address

795 Posts

January 7th, 2004 11:00

dreampuzz,

As I see it, you have to choices: you can whine about why two "identical" systems don't run identically, or you can take some advice and get your problem resolved.  The choice is yours.

There have been reports on the networking forums about 2.4 Ghz systems causing interference with 2.4 Ghz wireless adapters (which the WUSB11 is.)  Try moving the WUSB11 as far away from the PC as the USB cale will allow.

Message Edited by _Paladin on 01-07-2004 08:25 AM

7 Posts

January 7th, 2004 14:00

ok sure .. i will try to troubleshoot it

thanks anyway

No Events found!

Top