T
Tim Godfrey
Whenever my XP-Prof SP1 system boots, there is a 2 minute delay before
network activity can begin.
Reviewing the event log shows the message: "The Internet Connection
Firewall (ICF) / Internet Connection Sharing (ICS) service hung on
starting."
At this point networking is disabled, and the network icon does not
appear in the tray.
About 2 minutes later, there is a burst of hard disk activity, the
network icon appears and the message "The Internet Connection Firewall
(ICF) / Internet Connection Sharing (ICS) service entered the running
state." appears in the event log.
The other events that appear in the event log between the two ICF/ICS
messages (in sequential order) are:
"The Terminal Services service was successfully sent a start control."
"The NaiAvFilter1 service was successfully sent a start control."
"The Windows Management Instrumentation service was successfully sent
a start control."
"The Terminal Services service entered the running state."
"The Windows Management Instrumentation service entered the running
state."
I have found other threads in the past that address this exact
problem, but nobody has ever posted a diagnosis or solution.
network activity can begin.
Reviewing the event log shows the message: "The Internet Connection
Firewall (ICF) / Internet Connection Sharing (ICS) service hung on
starting."
At this point networking is disabled, and the network icon does not
appear in the tray.
About 2 minutes later, there is a burst of hard disk activity, the
network icon appears and the message "The Internet Connection Firewall
(ICF) / Internet Connection Sharing (ICS) service entered the running
state." appears in the event log.
The other events that appear in the event log between the two ICF/ICS
messages (in sequential order) are:
"The Terminal Services service was successfully sent a start control."
"The NaiAvFilter1 service was successfully sent a start control."
"The Windows Management Instrumentation service was successfully sent
a start control."
"The Terminal Services service entered the running state."
"The Windows Management Instrumentation service entered the running
state."
I have found other threads in the past that address this exact
problem, but nobody has ever posted a diagnosis or solution.