Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: Trouble Acquiring network address

Original Message
Name: bicyclekick01
Date: December 7, 2004 at 03:35:57 Pacific
Subject: Trouble Acquiring network address
OS: Win XP Pro SP2
CPU/Ram: p4m 1.7g/512
Comment:
My little wireless icon in the system tray says "acquiring network address" and stays taht way for a very long time, but everything seems to be fine. I have just gong through and tried to weed through the services that I don't need, so I am guessing it's probably something to do with that, but I am not sure which one. if I do a ipconfig /release & /renew it only takes me a couple seconds and it comes up fine. In fact: it's even telling me that I HAVE an IP address while it's trying to acquire it.
Any ideas?

Report Offensive Message For Removal

Response Number 1
Name: bicyclekick01
Date: December 7, 2004 at 03:47:27 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
Alright. I MAY have found it, although I don't understand why so any clarification would be awesome.
i turned the Network Location Awareness service back on and it seems to work fine now.

Report Offensive Follow Up For Removal

Response Number 2
Name: mbrook
Date: December 7, 2004 at 05:08:07 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
Personal computers running Windows often have numerous network connections, such as multiple network interface cards (NIC) connected to different networks, or a physical network connection and a dial-up connection. Windows Sockets has been capable of enumerating available network interfaces for some time, but certain critical information about network connections—such as the logical network to which a Windows computer is attached, or whether multiple interfaces are connected to the same network—was previously unavailable.

The Network Location Awareness service provider, commonly referred to as NLA, enables Windows Sockets 2 applications to identify the logical network to which a Windows computer is attached. NLA enables Windows Sockets applications to identify to which physical network interface a given application has saved specific information. NLA is implemented as a generic Windows Sockets 2 Name Resolution service provider.


Report Offensive Follow Up For Removal

Response Number 3
Name: iamc
Date: December 7, 2004 at 09:40:55 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
Nice to see "copy" and "paste" are working for you, mbrook. Where is that from?

Report Offensive Follow Up For Removal

Response Number 4
Name: mbrook
Date: December 7, 2004 at 09:48:57 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
Sometimes it's so much easier to just do that then say it over and over again. That is from Microsoft web site. Besides I didn't know really how to put that into my own words besides saying "hey you need that service" :).

Report Offensive Follow Up For Removal

Response Number 5
Name: iamc
Date: December 7, 2004 at 10:24:10 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
Very true. And you certainly answered the questions :)

Report Offensive Follow Up For Removal

Response Number 6
Name: waytron
Date: December 8, 2004 at 05:25:44 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
Hey, you answered the question. That is much better than just sending them to another website. Who cares where the information comes from?

Report Offensive Follow Up For Removal

Response Number 7
Name: iamc
Date: December 8, 2004 at 08:06:47 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
"Who cares where the information comes from?"

Someone who wants to read more on the subject?

Someone who wants to verify the trustworthiness of the source?

The original author of the information who wants to be credited for his work?


Report Offensive Follow Up For Removal

Response Number 8
Name: crimini
Date: December 16, 2004 at 13:26:30 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
I have the same issue on my laptop. That answer didn't really mean much to me. Is there something I need to do to correct this? Waht cause it? I ame after the latest auto-update, never seen it before. Thanks!

Tom


Report Offensive Follow Up For Removal

Response Number 9
Name: crimini
Date: December 16, 2004 at 13:28:31 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
Doh! In the time it took to write that, then regiter so I could pot it, the litle ping-pong ball stopped, and it simple says "connected." So in English, what happened? Thx!

Report Offensive Follow Up For Removal

Response Number 10
Name: ac
Date: January 11, 2005 at 13:20:30 Pacific
Subject: Trouble Acquiring network address
Reply: (edit)
"i turned the Network Location Awareness service back on and it seems to work fine now."

I am having the same problem. How do I turn the NLA service on though?


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Trouble Acquiring network address

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC