[4052] in WWW Security List Archive
Re: FW: NT4 bug? Or bug in my hardware?
daemon@ATHENA.MIT.EDU (Matthew Patton)
Thu Jan 23 21:14:42 1997
Date: Thu, 23 Jan 97 19:00:36 -0400
From: Matthew Patton <patton@sysnet.net>
To: <noah@vayuweb.com>, <www-security@ns2.rutgers.edu>
Errors-To: owner-www-security@ns2.rutgers.edu
>Yep, this takes down NT Server 4.0, as well. Anyone know of
>a work-around or fix? Anyone know what service is on port 135?
real simple, delete/deinstall/remove every stinking shred of microsucks
networking from you internet accessible sites. There is no need for the
garbage to be running. Port 135 and ones around it are for m$'s
networking junk. Block them at the router or localhost. There's
absolutely no need for the RPC Server service either (RPCSS) except for
NT4.0 and it's equivalent in win95 since the explore.exe thread which
powers the desktop is so braindead it can't figure out RPC isn't there.
Unless you like to wait more than a minute for every inane window
(explorer, control panels etc, etc) to time out before you can do
anything leave the service running. Such stupidity wasn't evident in NT
3.51. Also instead of the "universal desktop browser" in NT4 use
winfile.exe for good ol' filemanager. Works like a charm and is much
faster at doing stuff. Wish there was an option to run the old program
manager while we're at it.
