By the way, I've learned how to do acronym title text in HTML, so anytime you see an acronym and want to know what is stands for, just hover the mouse over it and the spelled-out version will pop up. A perk of using Mozilla Firefox is the fact that acronyms with title text will be highlighted in the page, almost like a link.
Ok, I've been able to determine that my Netgear WG111 adapter is FUBAR. I have purchased a D-Link wireless USB adapter, and it picks up the wireless network fine. However, it won't get an IP address automatically, yet I know the DHCP is working because my computer that I use to configure the router is connected to the router directly through Ethernet and gets a dynamically assigned IP address just fine. It gets better, though. Apparently, it works properly when I statically assign an IP address to the adapter.
Thanks to my buddy Mark, I've determined the solution there. My first clue was that when I specified a static IP address, I had to restart my computer. Now, this is normal...if you are running anything prior to Windows 2000 Professional. Mark proceeded to inform me that this happens in Windows XP (which I have on both machines) when the DHCP Client Service is disabled. And, of course, a machine with that service turned off will not be able to get an IP address through DHCP.
So, tonight, I shall try to re-enable that service on the machine using the wireless to see if that works. If it does, I know I have a bad Netgear adapter and will proceed to RMA it to Newegg for refund (hopefully). Also, this will assure me that my router's DHCP server is fine, despite the fact that I will most likely not use DHCP in my network for security reasons, but I still want to know it works and is there if I want it.
No comments:
Post a Comment