Closing port 135 and disabling DCOM affect Task Scheduler?

  • Thread starter Thread starter updata
  • Start date Start date
U

updata

I recently had a reason to set up a scheduled task for the first time in
quite awhile. However, I couldn't start my Task Scheduler Service.

My operating system is Windows 2000, sp4 with the updated rollup pack v2.

I found that the only way to start the service was to right click on the
mstask.inf file and install. That asked for the SP4 update version of
mstask.exe and mstinit.exe on the original Windows 2000 OS disk.

After successfully starting the service, I now get constant auto updates from
Microsoft asking me to install the Update Rollup SP4, which was already
installed.


http://support.microsoft.com/kb/891861


I decided to install it again and whenever I do (I even intalled another time
in safe mode), I can't open the Task Scheduler service. Each time I have to
reinstall mstask.inf, and that always brings back the MS Auto update icon
asking to reinstall SP4.


Several months ago, I closed port 135 by disabling DCOM and adding a string
to the registry. Could that have disabled the Task Scheduler service, and
if I reverse what I did to close port 135, and reinstall SP4 again, will that
solve both problems (SP4 installation requests and Task Scheduler Service)?
 
All you really needed to do was unbind File And Printer Sharing form the
desired connection. You might ask them here about the other problem.
Click to expand...

I've never installed the file and printing sharing service in my Local Area
Connections properties list. The only items listed are TCP/IP and Client for
MS networks.
 
Back
Top