-=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
- From: "tempting2taanzaa" <tempting2taanzaa@xxxxxxxx>
- To: <pctechtalk@xxxxxxxxxxxxx>
- Date: Thu, 1 Jan 2009 20:27:24 -0600
Ok, I opened network connections and opened the LAN properties, but my LAN
was disabled. Should it be enabled? And just trying out something, I
checked the "allow other network users to connect through this computer's
internet connection." Don't know exactly what that means. Should it be
checked? Just to see what happened, I tried disabling the wireless adapter,
and the infamous BSOD occurred. Here's other information that might be
pertinent (or not). The laptop did not have an internal wireless adapter,
so I used the adapter that came with the router (it fits in the PCMCIA
slot). Included was software to manage the wireless adapter. I installed
the software, but later opted to have Windows manage my wireless adapter.
Could this software be causing conflict? I don't know if the software has
an actual name, it just had "Linksys Wireless-G Notebook Adapter." However,
it is currently not running. The blue screens appear to happen when I
attempt to repair a wireless connection or if I attempt to disable the
wireless adapter. After the blue screen (I attempted to disable the wireless
adapter as a test) I looked in event viewer and noted the following error
message:
The DHCP allocator has detected a DHCP server with IP address 192.168.15.1
on the same network as the interface with IP address 192.168.0.1. The
allocator has disabled itself on the interface in order to avoid confusing
DHCP clients.
I followed the link to the Help and Support Center, but no information was
displayed.
I hope this information is helping!
*********************Reply Separator******************************
Subject: -=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
Re
Date: Wed, 31 Dec 2008 13:28:18 -0500
From: Gman <gman.pctt@xxxxxxxxx>
Every device on a network needs an address that the router or switch can use
in order to 'route' data to and from it. Most networks default to addresses
that start with 192.168.x.x. So, the first device would maybe get
192.168.1.1, the second receives 192.168.1.2, the third is 192.168.1.3,
etc.. The router itself might use an internal address of 192.168.1.0. The
ending numbers fully depend on what range of addresses the router is
designed to provide, so they might look more like 192.168.255.100,
192.168.255.101, 192.168.255.102, etc.. By assigning a different internal
address to each device, it becomes easy for the router to send incoming web
data to the system that requested it without disturbing the rest of the
systems on the network.
In this case, it appears as if your laptop is fighting with the router over
what address it needs to use. Normally, devices are set to simply accept
whatever address is assigned by the router. My guess here is that your
laptop was set up to demand from the router the specific address it wants to
use, but that address has already been assigned to another system before the
router receives that demand. What then occurs is that the laptop refuses to
accept a different internal address, but the router cannot provide that one
and a stalemate occurs where neither side gets what they want. The fix is
to tell the laptop to stop demanding a specific address and let the router
handle things by itself. This requires adjusting the laptop's networking
settings a little.
From within the laptop, go to Start > Network Connections. There are a few
ways that Windows can be set up to present (or not present) this item, so
just let me know if you don't see it there. If it shows you a submenu when
you hover over it or click on it, click on the entry that corresponds to
your network connection (probably the only one there). Once it opens, look
for an entry that says something like "Local Area Network" or LAN. Under
the Status column, you'll see that it's 'Connected'. Right click on it and
select Properties. In the General tab, scroll through the list of items and
double click on the one called "Internet Protocol (TCP-IP)" to open it up.
On this General tab, both areas should be set to "Obtain ... automatically".
In the Alternate Configuration tab, make sure that "Automatic ..." is again
the one selected. When you're done, click OK twice to close both windows
and set the new options in the registry. You should find that the problem
no longer exists following your next reboot of the laptop.
If you find that the settings are already set as above, let me know. If you
find that the instructions above don't correspond to what you see when you
try to follow them, let me know that, too.
Happy Holidays,
Gman
"The only dumb questions are the ones we fail to ask"
---------------------------------------------------------------
Please remember to trim your replies (including this sentence and everything
below it) and adjust the subject line as necessary.
To unsubscribe or change your email settings:
//www.freelists.org/webpage/pctechtalk
To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
//www.freelists.org/archives/pctechtalk/
To contact only the PCTT Mod Squad, write to:
pctechtalk-moderators@xxxxxxxxxxxxx
To join the PCTableTalk off-topic group, send a blank email to:
pctabletalk+subscribe@xxxxxxxxxxxxxxxx
---------------------------------------------------------------
Other related posts: