What Module Manages DHCP Leases in XP?

  • Thread starter Thread starter JCW
  • Start date Start date
J

JCW

In Windows XP (both SP2 and SP3) I often lose the TCP/IP connection with my
LAN (a 4-port cable/DSL router that acts as the local DHCP server) over
night, apparently because I use "Internet Lock" in ZoneAlarm Security Suite
when I'm away from my computers. In Windows 2000 SP4 with ZASS vs.
7.0.483.000 I was able to obviate this problem by allowing "Pass-Lock"
privilages to "Services and Controller app"
("C:\WINDOWS\system32\services.exe" vs. 5.0.2195,7035 in W2K SP4), which I am
therefore pretty sure was the module that renewed DHCP leases.

In XP with ZASS 8.0.298.035, however, "Services and Controller app" (still
"C:\WINDOWS\system32\services.exe", now vs. 5.1.2600.3520 in SP2 or vs.
5.1.2600.5755 in SP3) does not appear (from the ZASS "Program Control" page)
to access the Internet at all -- at least not directly. In any case,
granting it Pass-Lock privilages does not prevent the connection's being
dropped, apparently when the 24 hr. DHCP lease expires during Internet Lock.

Does anyone have a solution to this problem in Windows XP (other than
avoiding Internet Lock altogether)? -- JCW
 
I think I found the answer, in case anybody cares: At least as far as
ZoneAlarm Security Suite is concerned, it seems to be "Generic Host Processes
for Win32 Services" (C:\WINDOWS\system32\svchost.exe) that must have "Pass
Lock" privilages -- no longer "Services and Controller app" (services.exe).
Granting these privilages to svchost.exe permits my XP machines (both SP2 and
SP3) to renew their local DHCP leases from the cable/DSL router during
"Internet Lock." Nor is "Internet Server" access required by this program;
"Trusted Server" access is sufficient!

A side benefit of this procedure is apparently the solution to another
vexing problem that I posted in this forum (see "Unexplained Delay Launching
Applications"): I no longer experience occasional delays in launching
applications on these machines I had suspected some kind of XP peculiarity
or software incompatibility, but it now appears that they were just waiting
for svchost.exe tried to get in touch with my router, for whatever reason.

Any further explanation of this peculiar difference between W2K and XP (or
of what the underlying issue might be) is hoped for but not expected. -- JCW
 
Back
Top