Failure to assign IP address

[mesonism]

Hi all,

I have two laptop computers and am using wireless router.

Suddenly laptop A has problem to try to assign IP address from
wireless router. On the contrary, laptop B get ip address very quickly
and easily. Finally, laptop A fail to get ip address from wireless.
However, it could work well when I reboot it for the first time and
clicking repair in network properties shows the same problem.

Wireless Network adapter is Intel PRO/Wireless 2200BG and it uses last
version of its driver.
Signal is enough strong and I have tested all the ranges, which means
signal is not a problem. I have tried several routers but never works
well and the same problem has happened.

Also, I turned off the firewall and antivirus moniting as well,
neither does it.

Is there anybody who shows solution and reason about this trouble?

 

[R. McCarty]

Have you checked the Advanced (TAB) properties of the NIC
in Network Adapters. There are specific settings that might be
the cause for a inability to get settings from the DHCP server.
Check the "Locally Administered Address Field" and make
sure the "Not Configured" radio check box is selected.

Also if a Repair operation works ( albeit temporarily ) I'd be
suspicious of a Service not running or timing out. You should
check;/run Services.Msc and also examine the System Event
log for errors. This is best done by clearing the log and then
do an immediate reboot. Then check the logs so you can see
errors/warnings from a boot sequence.
To view Events:
Click Start, Run (Type) EventVwr.Msc [Enter]

 

[Guest]

Hi all,

I have two laptop computers and am using wireless router.

Suddenly laptop A has problem to try to assign IP address from
wireless router. On the contrary, laptop B get ip address very quickly
and easily. Finally, laptop A fail to get ip address from wireless.
However, it could work well when I reboot it for the first time and
clicking repair in network properties shows the same problem.

Wireless Network adapter is Intel PRO/Wireless 2200BG and it uses last
version of its driver.
Signal is enough strong and I have tested all the ranges, which means
signal is not a problem. I have tried several routers but never works
well and the same problem has happened.

Also, I turned off the firewall and antivirus moniting as well,
neither does it.

Is there anybody who shows solution and reason about this trouble?

Set up a wireless network
http://www.microsoft.com/windowsxp/using/networking/setup/wireless.mspx
Wireless by Barb Bowman
http://www.microsoft.com/windowsxp/using/security/expert/bowman_wirelesssecurity.mspx
Charlie Russel,Using a Wireless Laptop at Work and at Hom
http://www.microsoft.com/windowsxp/using/tabletpc/expert/russell_tabletlaptop.mspx

Try this:
= Click Start >> Control panel >> Network and Internet Connections >> Double
click Network connections, then right your LAN Icon and select Properties.
On the LAN properties under General make sure the Internet Protocol TCP/IP
is selected and click Properties.
There make sure the Machine Get assigned Automatically IP address and Renter
the Encryption Key and the Network SSID then click
[OK].

= Click start >> Control Panel >> Double Click Network and Internet
Connections >> Double click Internet Options, on the IE Properties window
you will see these Options:
General | Security | Privacy | Content | Connections | Programs
| Advanced.
Click on Connections tab and make sure the Connection is listed there then
click on LAN settings button and uncheck Automatically detect settings.
Click [OK] and close Hit F5 and open a run command and type in:
ipconfig /flushdns click [OK]
ipconfig /renew click [OK]
netsh winsock reset click [OK]

Download the winsock fix from here:
http://www.nasstec.co.uk/tools.html
Reboot your machine.

Also do you have a Wireless Utility that Handle the wireless connection as
some built-in can have this Capability from some Vendors so try to look for
it, Disable it and Let Windows Configure it for you or Vice Versa ( enable
WCZ to handle the Wireless Connection).
HTH.
Regards,
nass

 

[Tom Park]

Have you checked the Advanced (TAB) properties of the NIC
in Network Adapters. There are specific settings that might be
the cause for a inability to get settings from the DHCP server.
Check the "Locally Administered Address Field" and make
sure the "Not Configured" radio check box is selected.

Also if a Repair operation works ( albeit temporarily ) I'd be
suspicious of a Service not running or timing out. You should
check;/run Services.Msc and also examine the System Event
log for errors. This is best done by clearing the log and then
do an immediate reboot. Then check the logs so you can see
errors/warnings from a boot sequence.
To view Events:
Click Start, Run (Type) EventVwr.Msc [Enter]

Hi all,

I have two laptop computers and am using wireless router.

Suddenly laptop A has problem to try to assign IP address from
wireless router. On the contrary, laptop B get ip address very quickly
and easily. Finally, laptop A fail to get ip address from wireless.
However, it could work well when I reboot it for the first time and
clicking repair in network properties shows the same problem.

Wireless Network adapter is Intel PRO/Wireless 2200BG and it uses last
version of its driver.
Signal is enough strong and I have tested all the ranges, which means
signal is not a problem. I have tried several routers but never works
well and the same problem has happened.

Also, I turned off the firewall and antivirus moniting as well,
neither does it.

Is there anybody who shows solution and reason about this trouble?- Hide quoted text -

- Show quoted text -

Thanks for your suggestion, I checked event viewer and just be able to
see the warning message regarding dhcp failure. Any other failure or
warning about this could not be found.

I cannot find 'Locally Administered Address Field' option you
mentioned. For your information, my operating system is XP.
Additionally, I tested another wireless lan MINI pci card, neither
does it.

I could not resolve this problem and I finally decide my mind to
install o/s again.

Thanks!