no connectivity after installing Windows XP SP2

[Lido Neikonen]

I installed Windows XP SP2 on my laptop recently. I disabled the
firewall but can't get any form of connectivity (everything worked
fine before installing SP2). No internet, no Outlook (my companies
Exchange server).

When I connect to my DSL line at home, an icon appears saying 'limited
or no connectivity'. When I type ipconfig /all I see that dhcp is
disabled, but I don't nog if it should be enabled or how to enable it.
All my network settings are configured to obtain an IP address
automatically.

Does anyone know what's happing or how to solve this problem?

 

[Lido Neikonen]

Today I noticed that I don't have a default gateway or an DNS server.
I don't know how to configure this (the TCP/IP settings of the
connection are configured to obtain a DNS server automatically).
Anyone?

 

[Lido Neikonen]

still no luck:
my dhcp is enabled (without doing anything), I get a default gateway
assigned, but still no internet connection. Even the ping command
fails with error code 65.
Strangely my Outlook does work, but is incredibly slow and looses the
connection after some time.

Lido

 

[golver1]

still no luck:
my dhcp is enabled (without doing anything), I get a default gateway
assigned, but still no internet connection. Even the ping command
fails with error code 65.
Strangely my Outlook does work, but is incredibly slow and looses the
connection after some time.

Lido

I had the same problem. I used a PPPOE connection from Verizon DSL.
When I installed SP2, I lost connectivity. I was able to ping url's
and the DSL was able to establish a connection, but nothing beyond
that. I could not load any web pages or access POP3/SMTP mail.

Even though my Broadband connection was established and seemed to be
sending bytes, my LAN connection was not connected. I was getting a
No or Low connection status error.

I proceeded to remove the firewall from all the connections; Broadband
DSL, LAN, and even the 1394; but this had no effect.

IPCONFIG /all had all the proper settings for the Broadband
connection, but look a little weak on the Ethernet. DHCP was disabled
(I could not enable), and I had no WINS or gateway address's. I could
not renew or repair either.

After spending some time on the phone with Verizon, their conclusion
was that SP2 had corrupted my OS and they suggested I rebuild the
machine. Instead I went into Add/Remove programs and was able to
remove SP2 from there. Once I had removed SP2 from the machine,
everything worked perfectly.

As a side not, a co-worker of mine has a very similar set up at home
with the same DSL provider and has had no problems since installing
SP2.

 

[Sarc]

I don't have a guaranteed fix for you, but this worked on one machine we
were having this problem on. (getting the "limited or no connectivity"
error)

Log in as Administrator if possible (Home edition does not have a
Administrative log in, just use a account that has administrative
privileges) and open up a command prompt (Start, Run: cmd [ENTER])

Type this command

netsh int ip reset c:\resetlog.txt

Basically what this will do is replace, rewrite, remove or whatever is
needed to restore the TCP/IP stack in Windows by correcting the registry
values back to the original state they were in when the OS was originally
installed.

Good luck.

Microsoft Knowledge Base article number 299357

 

[kenward]

I installed Windows XP SP2 on my laptop recently. I disabled the
firewall but can't get any form of connectivity (everything worked
fine before installing SP2). No internet, no Outlook (my companies
Exchange server).

When I connect to my DSL line at home, an icon appears saying 'limited
or no connectivity'. When I type ipconfig /all I see that dhcp is
disabled, but I don't nog if it should be enabled or how to enable it.
All my network settings are configured to obtain an IP address
automatically.

Does anyone know what's happing or how to solve this problem?

This happened to me. I have also see several reports elsewhere of the
same behaviour.

On investigation, it seemed that the on-board NIC (Asus) was somehow
acquiring an IP address that was not compatible with the LAN. It was
in the wrong range.

I dealt with the issue by installing a PCI NIC card. This is working
flawlessly.

No amount of fiddling around will get the on-board NIC to work.

Setting the I address rather than leaving it to the router/modem
doesn't work.

Funnily enough, I have just discovered that the on-board LAN will
connect to the LANB on my Vaio notebook.

Baffling.




_______________________________________________________________________
Michael Kenward Words for sale