LAN yes, Internet no! HELP!!

  • Thread starter Thread starter Charlie
  • Start date Start date
C

Charlie

Reformating the hard drive is not an acceptable solution,
and I doubt that it would work, but it sure would raise
my blood pressure! Your advice will be appreciated!

Internet Access Problem
=======================

Background: A young "bad" WinXP-Pro computer had
operated for several months with a "good" WinXP computer
on a router based LAN with DSL Modem. The "bad" computer
died and a replacement motherboard of the same model but
newer rev. number was installed. Startup problems
lingered for a while as a result of nasty crashes.
The "bad" computer was booted from the WinXP CD
and "repaired". The harddisk was fixed using chkdsk and
defragged. Subsequently it was booted from the WinXP
CD, 'install' elected and then 'repair', with the result
that it got a fresh installation without wipping out my
data and other software. Much effort has been put into
trying to resolve the problem ... The "good" computers
still work normally.

Problem: The "bad" computer refuses to access the
internet via browser or eMail client, be they Microsoft
IE 6 or Netscape 7.1.

Analyses from Testing, etc:
1) When connected to the DSL modem directly, the "bad"
computer's browser can take an IP address and get back
from the DNServer the URL, but it can NOT load the web
page, nor can the eMail client access the mail server.
The web target page can be pinged and the "bad"
computer's IP address can be pinged from outside.
2) When connected to a router and hence to a DSL modem,
and when using a DCHP/auto configuring setup, there is NO
access to the LAN nor the Internet.
3) When connected to a router and hence to a DSL modem,
but with the alternate configuration having a fixed IP
address, then the "bad" computer can access the LAN but
still NOT the Internet.

Further Notes:
1) Configurations have been matched/compared to
the "good" WinXP-Home computer.
2) The Router and DSL modem work as expected with
the "good" WinXP computer.
3) On the "bad" computer (a) NIC drivers have been
deleted and reinstalled, (b) likewise TCPIP software and
configuraions, and (c) likewise the software bridge. IP
addresses have been reset numerous times.
4) The firewall, ZoneAlarm v37.193, was uninstalled with
no improvement following reboot.
5) WinXP Pro includes Serv. Pack 1 as well as most of the
updates until about 7/15/03.
6) "Bad" hardware is Asus A7N8X Deluxe motherboard with
AMD Athlon XP 2200 CPU running 512MB RAM.
7) The last ResetLog.txt file had the following possibly
interesting lines at its end:
"reset Linkage\UpperBind for
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1
\3&13C0B0C5&0&20.
bad value was: REG_MULTI_SZ = PSched
"reset Linkage\UpperBind for
PCI\VEN_10B7&DEV_9201&SUBSYS_80AB1043&REV_40
\4&35344E25&0&0860.
bad value was: REG_MULTI_SZ = PSched
"reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000.
bad value was: REG_MULTI_SZ = PSched
8) The EventLog reports failure to ping the DNServer,
and "... unable to automatically configure the IP
parameters for NIC .. requested server provider could
nopt be loaded or initialized.

---------------------------------------------------------
Event Log shows for 7/29/03 at 17:55 (WinXp reinstall
started at 15:00, probably finished around 17:30-18:00)
an Event ID 1006, Source DHCP:
"Your computer was unable to automatically configure the
IP parameters for the Network Card with the network
address 020C6E678288. The following error occurred
during configuration: The requested service provider
could not be loaded or initialized."
 
Some additional insights ..
After I force DNS server entries, I am able to ping those
servers, BUT Netscape Mail reports "failed to connect to
server pop.earthlink.net". IE also confirms that I have
no usable Internet connection. What is wrong? Where is
the fix?

Charlie L.
 
1) Sadly NO ONE chose to tackle this and offer advice.
2) But reading carefully the message base thankfully I found ..
3) Sam's <[email protected]> reply dates 8/5/03 to a message "DHCP error",
which had the essence of the fix, ie delete from the registry the keys
....Winsock and Winsock2 and then reinstall TCPIP protocol. See his message for
exact details.

Charlie L.
==========================================================
 
Back
Top