-=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network Repair

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"

----- Original Message ----- 
From: "tempting2taanzaa" <tempting2taanzaa@xxxxxxxx>
To: <pctechtalk@xxxxxxxxxxxxx>
Sent: Wednesday, December 31, 2008 12:48 PM
Subject: -=PCTechTalk=- Windows XP BSOD When Attempting Wireless Network 
Repair


> This is actually an old problem that I did not have time to address during
> the last semester of school.  I am not exactly certain how to copy the 
> blue
> screen message (I know it has something to do with setting the computer 
> not
> to reboot or something like that).  I have accessed the event viewer (is
> that the same as the blue screen error message?) and am looking through 
> the
> list of errors and I think the one I am looking for gives this 
> information:
>
> Date: 12/31/2008 Source: NetBT
> Time: 11:11:17 AM Category: None
> Type: Error Event ID: 4321
> User: N/A
> Computer: Toshiba
>
> Description:
>
> The name "WORKGROUP :1d" could not be registered on the Interface with
> IP address (lists xxx.xxx.xx.102, do I need to list the whole IP here?).
> The machine with the IP address (lists xxx.xxx.xx.103) did not allow the
> name to be claimed by this machine.
>
> I then get a link to Help and Support.
>
> Data:
>
> 0000: 00000000 00560004 00000000 c00010e1
> 0010: 00000010 c0000001 00000000 00000000
> 0020: 00000000 00000000
>
> This machine's specifications are as follows:
>
> Toshiba A15-S1292
> Processor: Celeron 2.4GHz
> RAM: 752MB
> O/S: Windows XP Home Edition SP3
>
> The problems started just after installing SP3, but because I only use 
> this
> laptop rarely (I only start it to update windows, Norton, Comodo, any 
> other
> software updates and use the fax software) that I just did not make the 
> time
> to find out what the problem was.  I am now out of school until the 18th 
> of
> January and am able to do a little maintenance.  I was considering
> uninstalling SP3, but thought something else might be causing the problem,
> so I was going to do the last ditch effort of using the recovery disks, 
> and
> reinstalling all my software.  If you can offer another suggestion, it 
> will
> be appreciated, if not, back to the drawing board.
>
> Sorry for the long post!  :( 

---------------------------------------------------------------
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:
http://www.freelists.org/webpage/pctechtalk

To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
http://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: