Limited or no Connectivity SP2

Ralph Parker wrote:
*That is a great solution to the problem that Nate had, but
I have the same issue with SP2 on my desktop (with XP-PRO) that
is connected to the internet via a wireless G router going into a
Comcast
cable modem. In my case the message is
associated with zero
internet connectivity, despite turning off the XP firewall.
Bypassing
the router straight to the cable modem provides no relief. I
backed out of SP2 and normal internet connectivity was immediately
restored. Now I am looking for some additional clues before trying
the "upgrade" again.

Update: Here is the information from another forum that fixed the
problem:
You'll find if you uninstall SP2 your connection will run perfectly
as before. Limited or no connectivity warning
If you see a "limited or no connectivity" warning and a yellow
exclamation mark in Device Manager, this only means that the
computer's network port is set to automatically obtain an IP address
through DHCP (Dynamic Host Configuration Protocol), but a DHCP server
could not be found. Windows then generates an APIPA address in the
169.254.x.y range (see chapter APIPA Addresses in Private IP
Addresses). This means that all computers in the LAN (Local Area
Network) can communicate with each other, if the others also gave
themselves APIPA addresses, but you cannot have any Internet
connectivity that way.

Try the following as I did:

1) Always with a broadband connection, do these steps first: Shut
down modem - remove power. Shut down router - remove power. Shut
down computers. After one minute, restart modem. When it has fully
booted, start the router. When the modem has fully booted, start all
the computers.

2) Go to Start / Run at the command box enter: netsh int ip reset
C:\resetlog.txt ( When you run the reset command it rewrites
pertinent registry keys that are used by the Internet Protocol
(TCP/IP) stack to reach the same result as the removal and the
reinstallation of the protocol.)

3) Go to Local Area Connection and right click on Properties.
Uncheck the QoS Packet Scheduler. Hopefully this will get you
connected.
*



--
Ralph Parker
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message985965.html

"Steve Winograd [MVP]" wrote:

In article , "Nate"
wrote:
Now that I've installed Service Pack 2 I get a warning
message on my LAN connection that I have limited or no
connectivity? I haven't had a problem and DSL connection
seems fine? Any ideas why its warning me suddenly?

There's probably nothing wrong. That message is new in Service Pack
2, and it means that:

1. The LAN connection is configured to obtain an IP address
automatically, and:

2. It can't communicate with a DHCP server to obtain an IP address.

That's the normal situation when a DSL connection uses PPPoE. The
PPPoE connection gets an IP address, and the LAN connection doesn't.

You can disable the message in the LAN connection's properties. A
better solution would be to assign a private static IP address, like
10.0.0.1, to the LAN connection, so that it won't even try to obtain
an IP address from DHCP.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

"Steve Winograd [MVP]" wrote:

In article , "Nate"
wrote:
Now that I've installed Service Pack 2 I get a warning
message on my LAN connection that I have limited or no
connectivity? I haven't had a problem and DSL connection
seems fine? Any ideas why its warning me suddenly?

There's probably nothing wrong. That message is new in Service Pack
2, and it means that:

1. The LAN connection is configured to obtain an IP address
automatically, and:

2. It can't communicate with a DHCP server to obtain an IP address.

That's the normal situation when a DSL connection uses PPPoE. The
PPPoE connection gets an IP address, and the LAN connection doesn't.

You can disable the message in the LAN connection's properties. A
better solution would be to assign a private static IP address, like
10.0.0.1, to the LAN connection, so that it won't even try to obtain
an IP address from DHCP.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
I have looked at many suggestions and yours in on target for my situation, could you explain how I can assign a private static IP address to the LAN connection, thanks.