![]() |
|
|
|||||||
![]() |
Wireless Networking - Wireless and SP2 Debacle with DHCP services |
|
|
Thread Tools | Search this Thread |
|
|
#1 |
|
My last recourse is to seek guidance fromt this valiant group on a Wireless
Debacle that SP2 has created as follows: Netgear AP MR814 (wireless access point 802.11b with DHCP services) connected to NetStream (Efficient Networks) ADSL modem that is connected to a Desktop running Windows XP Home. Laptop (HP NC4000 WXP Pro w/ internal Atheros WLAN 802.11 A/B and Broadcom Gigabit Ethernet) connects via CAT 5 fine with no issues getting its IP address. When attempitng to use wireless on laptop cannot resolved IP address where Windows assigns the dreaded 169.xxx.xxx address. I have tried using a PCMCIA card to troubkleshoot if it was the Atheros internal module (has been replaced by HP), where it worked for one session until I need to shut down for the end of the day. Next day, boot up laptop thinking the PCMCIA card resolved a bad WLAN module, but the card itself could not negotiate an IP address defaulting back to 169.xxx.xxx address. Try using the NETSH command "netsh winsock reset catalog" as well as "netsh int ip reset resetlog.txt" to no avail. Would be grateful to seek further guidance on this SP2 debacle affecting wireless DHCP IP adddressing. Thanks. -- moerice =?Utf-8?B?bW9lcmljZQ==?= |
|
|
![]() |
| Thread Tools | Search this Thread |
|
|