Sign in with
Sign up | Sign in
Your question

Error 1068 when trying to start DHCP client service

Last response: in Windows XP
Share
Anonymous
October 22, 2004 9:11:38 PM

Archived from groups: microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.network_web (More info?)

I have an odd problem here, and I think I'm on the track to the right
solution. Please advise. Details follow.

Pre-problem system: XP SP2, all fixes. Norton System Works 2003, including
NAV, fully updated. ZAPro 5.1.033. DSL: Actiontec 1520 modem/router, DHCP
server active. DSL router is working properly (second machine on network
is fine.)

Problem occurred when removing NAV 2003 (near end of subscription) and
replacing with AVG 7. After NAV removal via NSW installer, lost network
connection. Attempting to start DHCP client produces Error 1068,
"Dependency service or group failed top start."

After a couple of false starts, I see the following dependencies for the
DHCP client service:
AFD Networking Support Environment
NetBT
SYMTDI (!!!)
TCP/IP Protocol Driver

Configuring a static IP and DNS addresses works, so I'm reasonably sure the
basic TCP/IP services are intact.

A registry search for SYMTDI shows active service and dependency entries
in HKLM/System/ControlSet001/Services. These entries refer to a
now-deleted driver \??\C:\Windows\System32\drivers\SYMTDI.SYS (exact copy
of the driver registry entry). ControlSet002 and CurrentControlSet show
identical sets of entries to those in ControlSet001. There is no
corresponding entry under Manage | Services for SYMTDI.

I suspect SYMTDI.SYS is the hook for the NAV inline network scanner. The
NSW uninstaller removed the system driver, but it appears neither the NSW
uninstaller not Symantec's brute-force NAV remover caught this registry
error.

Proposed resolution:
Backup registry, then manually edit our all references to SYMTDI.

Comments? Suggestions?

TIA,
| George Ruch
Anonymous
October 23, 2004 5:00:19 AM

Archived from groups: microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.network_web (More info?)

Sounds like a game plan to me, and SYMTDI is indeed a leftover from NAV.

--
Richard G. Harper [MVP Shell/User] rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"George Ruch" <george.ruch@3lefties.com> wrote in message
news:l73jn01mmrsio3eu00q7kudhgqb22546c2@4ax.com...
>I have an odd problem here, and I think I'm on the track to the right
> solution. Please advise. Details follow.
>
> Pre-problem system: XP SP2, all fixes. Norton System Works 2003,
> including
> NAV, fully updated. ZAPro 5.1.033. DSL: Actiontec 1520 modem/router, DHCP
> server active. DSL router is working properly (second machine on network
> is fine.)
>
> Problem occurred when removing NAV 2003 (near end of subscription) and
> replacing with AVG 7. After NAV removal via NSW installer, lost network
> connection. Attempting to start DHCP client produces Error 1068,
> "Dependency service or group failed top start."
>
> After a couple of false starts, I see the following dependencies for the
> DHCP client service:
> AFD Networking Support Environment
> NetBT
> SYMTDI (!!!)
> TCP/IP Protocol Driver
>
> Configuring a static IP and DNS addresses works, so I'm reasonably sure
> the
> basic TCP/IP services are intact.
>
> A registry search for SYMTDI shows active service and dependency entries
> in HKLM/System/ControlSet001/Services. These entries refer to a
> now-deleted driver \??\C:\Windows\System32\drivers\SYMTDI.SYS (exact copy
> of the driver registry entry). ControlSet002 and CurrentControlSet show
> identical sets of entries to those in ControlSet001. There is no
> corresponding entry under Manage | Services for SYMTDI.
>
> I suspect SYMTDI.SYS is the hook for the NAV inline network scanner. The
> NSW uninstaller removed the system driver, but it appears neither the NSW
> uninstaller not Symantec's brute-force NAV remover caught this registry
> error.
>
> Proposed resolution:
> Backup registry, then manually edit our all references to SYMTDI.
>
> Comments? Suggestions?
>
> TIA,
> | George Ruch
Anonymous
October 23, 2004 1:05:31 PM

Archived from groups: microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.network_web (More info?)

"Richard G. Harper" <rgharper@email.com> wrote:

>Sounds like a game plan to me, and SYMTDI is indeed a leftover from NAV.

Thanks. Now to somehow pass this on to Symantec.

| George Ruch
Anonymous
October 23, 2004 1:34:59 PM

Archived from groups: microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.network_web (More info?)

"Richard G. Harper" <rgharper@email.com> wrote:

>Sounds like a game plan to me, and SYMTDI is indeed a leftover from NAV.

Follow-up: I wasn't able to remove the LEGACY_SYMTDI driver references,
but I was able to delete the SYMTDI dependency entries. The DHCP client is
now working normally.

| George Ruch
!