From: "Geo." 

I don't believe you can block it and still have the server function as a
print/file server. Web server yes but print/file I think has to be exposed.

Geo.

"Chris Robinson"  wrote in
message news:3E894E00.1E12E628{at}NOSPAMtotalise.co.uk...
> great - so if you want to protect your NT boxes, you're gonna have to lose
some
> functionality - I use this a lot to send messages to users when we're
about to
> take a server offline or something.
>
> Chris.
>
> "Geo." wrote:
>
> > On NT4 I believe it's either port 135 or 139 and yes if it's blocked
then
> > net send fails.
> >
> > Geo.
> >
> > "Chris Robinson"
 wrote in message
> > news:3E883348.5281C7E1{at}NOSPAMtotalise.co.uk...
> > > Here's another thought - doesn't the Windows messenger service listen
on
> > Port
> > > 135?  If so then would blocking this port on all your NT systems
> > effectively
> > > prevent administrators from sending out messages using NET SEND?
> > >
> > > Chris.
> > >
> > > "Geo." wrote:
> > >
> > > > That would stop functionality, like remote backups. A
second trivial
fix
> > > > would be to allow anyone holding an NT4 license upgrade
to W2K free.
> > Don't
> > > > want to fix it then at least take care of your customers who are
still
> > > > running it. This would cost MS nothing out of pocket,
just honor an
NT4
> > > > license as if it were a W2K license.
> > > >
> > > > Geo.
> > > >
> > > > "Tony Ingenoso"
 wrote in message
> > > > news:3e82f42b{at}w3.nls.net...
> > > > > A trivial "fix" could be to simply
disable port 135 in the TCP/IP
> > options.
> > > > What would that take?  Maybe 50 lines of code
> > > > >
> > > > >
> > >
>

--- BBBS/NT v4.01 Flag-4