network failure after ME upgrade to XP

  • Thread starter Thread starter Tim Hayles
  • Start date Start date
T

Tim Hayles

A new provider in town installed a cable modem at my
house today. My HP Pavilion running fully patched XP home
edition would not allow Explorer to see the web through
this cable modem. Typing in the IP address of the cable
modem (or my LinkSys router) also failed. The HP as the
NIC built in. Hooking the cable modem via USB (and after
installing the drivers for this) also did not work and
produced the same lack of results. Installed a different
NIC (3COM compatible) and connected through that and
still nothing. XP recognized it fine. XP responds with
those little tip strips when I unplug and plug back in
the Ethernet cable. Fiddled with all the relevant
settings. Nothing.

Dail-up through this same computer still works fine.

I plugged my wife's laptop, also running XP, into the
cable modem and it worked just fine. Fast surfing
immediately.

The laptop's XP came factory installed by Dell. The HP's
XP was installed by myself as a Quick upgrade over the
factory installed ME. Could that have anything to do with
this?

- thanks, Tim
 
I've just discovered that I cannot start my DHCP Client.
I get error 1068: the dependency service or group failed
to start. I get my IP address via DHCP when using the
ethernet connection. No wonder the IP shown by the
Networks Connections window is 0.0.0.0

The DHCP client depends on these drivers:
AFD Networking Support Environment
NetBT
SYMTDI
TCP/IP Protocol Driver
IPSEC Driver

Anyone know why one of these is failing and how to find
out which one?

- thanks, Tim

- Tim
 
Found out (from elsewhere on Microsoft's site) that the
uninstall of Norton AntiVirus leaves the SYMTDI service
listed as a dependency for the DHCP client service. Since
SYMTDI was removed, it won't start and therefor the DHCP
client won't start. Fix was to edit the registry and
remove the DHCP client's dependency on SYMTDI.

BUT, even though I now have an IP address, my browser
still cannot see the web through the cable modem. I think
it's a DNS problem...

- Tim
 
Back
Top