Network did not assign an address

G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

I upgraded my laptop's windows XP with service pack 2 and I lost my
wireless network. I get an error message

"Limited or no connectivity. You might not be able to access the internet
or some network resources. This problem occurred because the network did
not addign a network address to the computer"

The wireless network still works fine with another computer, a desktop, in
another room.

I tried to have windows "repair" the problem but when I try Windows reports
that it was not successful.

I am using a netgear wireless access point (MA111) and netgear router
(MR814v2)

Can anyone help me get my wireless connection back?
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

Bill Babakian wrote:
> I upgraded my laptop's windows XP with service pack 2 and I lost my
> wireless network. I get an error message
>
> "Limited or no connectivity. You might not be able to access the
> internet or some network resources. This problem occurred because
> the network did not addign a network address to the computer"
>
> The wireless network still works fine with another computer, a
> desktop, in another room.
>
> I tried to have windows "repair" the problem but when I try Windows
> reports that it was not successful.
>
> I am using a netgear wireless access point (MA111) and netgear router
> (MR814v2)
>
> Can anyone help me get my wireless connection back?

This annoyance happened on two of my SP2 updates. Open TCP/IP
properties of the problem connection, navigate to TCP/IP filtering,
change all instances of Permit None to Permit All. Leave Enable
Filtering checked until you know that the connection is fixed.

Q
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

"Quaoar" <quaoar@tenthplanet.net> wrote in news:arOdneDEK-fZUD3cRVn-
2Q@comcast.com:

> Bill Babakian wrote:
>> I upgraded my laptop's windows XP with service pack 2 and I lost my
>> wireless network. I get an error message
>>
>> "Limited or no connectivity. You might not be able to access the
>> internet or some network resources. This problem occurred because
>> the network did not addign a network address to the computer"
>>
>> The wireless network still works fine with another computer, a
>> desktop, in another room.
>>
>> I tried to have windows "repair" the problem but when I try Windows
>> reports that it was not successful.
>>
>> I am using a netgear wireless access point (MA111) and netgear router
>> (MR814v2)
>>
>> Can anyone help me get my wireless connection back?
>
> This annoyance happened on two of my SP2 updates. Open TCP/IP
> properties of the problem connection, navigate to TCP/IP filtering,
> change all instances of Permit None to Permit All. Leave Enable
> Filtering checked until you know that the connection is fixed.
>
> Q
>
>


All three boxes for filtering had "Permit All" checked. However, the
box labeled "Enable filtering" was unchecked. I checked it and
restarted the computer.

The wireless still doesn't work. (My signal strength is excellent)

I uninstalled the wireless adapter software and reinstalled it. Still
no luck.

Any ideas???
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

Bill Babakian <email@att.net> wrote in
news:Xns95A86E3D09410Billbabakianattnet@167.206.3.3:

> I upgraded my laptop's windows XP with service pack 2 and I lost my
> wireless network. I get an error message
>
> "Limited or no connectivity. You might not be able to access the
> internet or some network resources. This problem occurred because the
> network did not addign a network address to the computer"
>
> The wireless network still works fine with another computer, a
> desktop, in another room.
>
> I tried to have windows "repair" the problem but when I try Windows
> reports that it was not successful.
>
> I am using a netgear wireless access point (MA111) and netgear router
> (MR814v2)
>
> Can anyone help me get my wireless connection back?
>

What IP is the machine getting? If the IP has the 169 IP assigned, then you
have an IP that will allow the machine to access the machines on the LAN.
But the IP will not allow the machine to access the Internet. If the 169.IP
is being assigned, then you may have some kind of mis-configuration issue.

Duane :)
 

Avalanche

Distinguished
Oct 30, 2004
66
0
18,630
Archived from groups: alt.internet.wireless (More info?)

On Sun, 21 Nov 2004 10:15:48 -0700, "Quaoar" <quaoar@tenthplanet.net>
wrote:

>Bill Babakian wrote:
>> I upgraded my laptop's windows XP with service pack 2 and I lost my
>> wireless network. I get an error message
>>
>> "Limited or no connectivity. You might not be able to access the
>> internet or some network resources. This problem occurred because
>> the network did not addign a network address to the computer"
>>
>> The wireless network still works fine with another computer, a
>> desktop, in another room.
>>
>> I tried to have windows " repair" the problem but when I try Windows
>> reports that it was not successful.
>>
>> I am using a netgear wireless access point (MA111) and netgear router
>> (MR814v2)
>>
>> Can anyone help me get my wireless connection back?
>
>This annoyance happened on two of my SP2 updates. Open TCP/IP
>properties of the problem connection, navigate to TCP/IP filtering,
>change all instances of Permit None to Permit All. Leave Enable
>Filtering checked until you know that the connection is fixed.
>
>Q
>

Same problem, tho not now. How do I open TCP/IP properties,etc. My
helpful (the Winbook or XP?) HELP search said open Network
Connections, which I did...then Incoming Connections, which I don't
see/can't find.
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

I'm having almost the exact same problem, except I'm using a
non-wireless router, and I've had Windows SP 2 for about 1 month now
with no problems. My IP address does have 169 in front of it, is there
some way to fix this?


--
Mr_Freezie
http://forums.speedguide.net
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

Mr_Freezie <Mr_Freezie.1hs0v7@no-mx.earth.universe.org> wrote in
news:1103904906.ac13a30dd96c2112d758aa6add525046@teranews:

>
> I'm having almost the exact same problem, except I'm using a
> non-wireless router, and I've had Windows SP 2 for about 1 month now
> with no problems. My IP address does have 169 in front of it, is there
> some way to fix this?
>
>

You'll have to reset the TCP/IP stack on XP if you cannot get the 169 IP to
release by doing IPconfig /release and IPconfig /renew or it doesn't
release when doing a re-boot of the machine.

http://support.microsoft.com/kb/299357

You should try to determine what caused the O/S to assign the 169 IP. It
could be a bad NIC, CAT 5 cable, router, mis-configuration of the NIC, etc,
etc.

Duane :)
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

Ok now I'm really confused. After resetting the TCP/IP stack, I still
had the same problem. So to check the cables, I connected my computer
to the router with a cable I knew worked, and it still didn't work. So
I thought it might be the router, so I directly connecting the Windows
to my modem, and it still gives me the same message about the local
area network!


--
Mr_Freezie
http://forums.speedguide.net
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

"Mr_Freezie" <Mr_Freezie.1hs513@no-mx.earth.universe.org> wrote in
message news:1103910296.3e8fa2bf269ca2048213f2a5bd1ad87a@teranews...
>
> Will resetting the TCP/IP stack delete any files or anything
important?
No, just do the ipconfig /release then an Ipconfig /renew at the
command prompt
 
G

Guest

Guest
Archived from groups: alt.internet.wireless (More info?)

Mr_Freezie <Mr_Freezie.1hsba1@no-mx.earth.universe.org> wrote in
news:1103918395.ed1f093325a1a9f449234431bf8fb8a6@teranews:

>
> Ok now I'm really confused. After resetting the TCP/IP stack, I still
> had the same problem. So to check the cables, I connected my computer
> to the router with a cable I knew worked, and it still didn't work. So
> I thought it might be the router, so I directly connecting the Windows
> to my modem, and it still gives me the same message about the local
> area network!
>
>

Well try swapping NIC's (Network Interface Card) with another computer if
you can and see what happens. Make sure you reset the TCP/IP stack if
it's stuck on the 169 IP. The 169 IP will allow the machine to access
other machines on the LAN when connected to the router. You getting the
169 IP when the machine was connected to the modem could mean that the
NIC's MAC is not provisioned with the ISP to use the ISP's network. In
most cases, the MAC of the router or computer's NIC MAC must be
provisioned with the ISP linked to your account, otherwise, you may not
get an IP from the ISP to use and it could defaulted to the 169 IP again.


Duane :)