From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0244_01C332A1.AB3E82F0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Deleting the TCP/IP registry keys is generally a bad idea.  I've not =
known this to fix anything.  It's OK to delete the reg keys for an =
adapter and like the device be recreated but you can use the device =
manager to delete the device without the risk of deleting the wrong =
thing.

Rich
  "Geo."  wrote in message =
news:3eebaead$1{at}w3.nls.net...
  He tried that, I even had him delete the registry keys for tcpip and =
that
  didn't help. He ended up reinstalling.

  Geo.

  "William F. Zachmann" 
wrote in message
  news:3eeb930d$1{at}w3.nls.net...
  > Glenn,
  >
  > Have you tried deleting the LAN connection and then re-creating it?
  >
  > All the best,
  >
  > will
  >
  >
  > "Glenn Meadows"  wrote in message
  > news:3eeb6fa2{at}w3.nls.net...
  > > At a friends house, trying to figure out why the computer will NOT
  connect
  > > to the lan.
  > >
  > > Here are the symptoms:
  > >
  > > Windows XPPro recent re-install.
  > > Norton AV2003 run, shows system is clean.
  > > Computer is Athalon800
  > > 512 meg of ram.
  > > About 3 weeks ago, it just stopped talking to the internet, or the =
other
  > > computer on the lan.
  > > Prior to today, it would at least talk on the local lan, but that =
is
  all.
  > >
  > > Connection in the house was through a Siemen Speedstream router =
with
  > > connection to cable modem.  Her laptop works/worked fine with the =
prior
  > > connection.
  > >
  > > Today, we installed a D-Link wireless router (4 hard ports + =
802.11b).
  > > Connected the laptop via wire, came right up.  Connected my laptop =
with
  my
  > > wireless connection, came right up.  The desktop refuses to get a =
DHCP
  > > address.  Manually assigning an IP address does not take to the OS
  level.
  > > After manually entering all the info, and doing a reboot, an =
IPCONFIG
  > shows
  > > all zeros (0.0.0.0).
  > >
  > > We've put in a NEW NIC, and it responds the same way (D-Link Nic). =
 I've
  > put
  > > back in the old Netgear, and it's still doing the same thing.
  > >
  > > Anyone know of a virus/worm that disables all networking, and if =
so, how
  > > does one find it?  Have not tried booting to safe mode with =
networking
  yet
  > > to see if THAT works.
  > >
  > > This is just plain ODD!!!!
  > >
  > > All thoughts, comments, suggestions welcome (except moving to =
Linux, as
  > > that's not a viable option at this point.  She has dedicated apps =
that
  > have
  > > to run on Windows).
  > >
  > >
  > > --
  > > Glenn M.
  > >
  > >
  > >
  >
  >


------=_NextPart_000_0244_01C332A1.AB3E82F0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Deleting
the TCP/IP =
registry keys is=20
generally a bad idea.  I've not known this to fix
anything.  = It's OK=20
to delete the reg keys for an adapter and like the device be recreated = but you=20
can use the device manager to delete the device without the risk of = deleting the=20
wrong thing.
 
Rich

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3eebaead$1{at}w3.nls.net...He=20
  tried that, I even had him delete the registry keys for tcpip and=20
  thatdidn't help. He ended up =
reinstalling.Geo."William F.=20
  Zachmann" <wfz{at}NOcanopusresearchSPAM.c=">mailto:wfz{at}NOcanopusresearchSPAM.com">wfz{at}NOcanopusresearchSPAM.c=
om>=20
  wrote in messagenews:3eeb930d$1{at}w3.nls.net...=
>=20
  Glenn,>> Have you tried deleting the
LAN connection and =
then=20
  re-creating it?>> All the
best,>>=20
  will>>> "Glenn
Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in=20
  message> news:3eeb6fa2{at}w3.nls.net...>=
 >=20
  At a friends house, trying to figure out why the computer will=20
  NOTconnect> > to the
lan.> >> > Here =
are the=20
  symptoms:> >> > Windows
XPPro recent =
re-install.>=20
  > Norton AV2003 run, shows system is clean.>
> Computer =
is=20
  Athalon800> > 512 meg of ram.>
> About 3 weeks =
ago, it=20
  just stopped talking to the internet, or the other> > =
computer on=20
  the lan.> > Prior to today, it would at least talk on the =
local lan,=20
  but that isall.> >>
> Connection in the house =
was=20
  through a Siemen Speedstream router with> > connection to =
cable=20
  modem.  Her laptop works/worked fine with the
prior> >=20
  connection.> >> > Today,
we installed a D-Link =
wireless=20
  router (4 hard ports + 802.11b).> > Connected the
laptop via =
wire,=20
  came right up.  Connected my laptop
withmy> > =
wireless=20
  connection, came right up.  The desktop refuses to get a =
DHCP>=20
  > address.  Manually assigning an IP address does not take to =
the=20
  OSlevel.> > After manually entering all
the info, and =
doing a=20
  reboot, an IPCONFIG> shows> > all zeros =
(0.0.0.0).>=20
  >> > We've put in a NEW NIC, and it
responds the same way =
(D-Link=20
  Nic).  I've> put> >
back in the old Netgear, and =
it's=20
  still doing the same thing.> >>
> Anyone know of a =

  virus/worm that disables all networking, and if so, how>
> =
does one=20
  find it?  Have not tried booting to safe mode with=20
  networkingyet> > to see if THAT
works.> =
>> >=20
  This is just plain ODD!!!!> >>
> All thoughts, =
comments,=20
  suggestions welcome (except moving to Linux, as> > that's =
not a=20
  viable option at this point.  She has dedicated apps
that> =

  have> > to run on Windows).>
>> =
>> >=20
  --> > Glenn M.>
>> >>=20
 
>>>

------=_NextPart_000_0244_01C332A1.AB3E82F0--

--- BBBS/NT v4.01 Flag-4