Re: Anyway to start the "Messenger" service only when connected to
- From: TFS <TFS@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 Dec 2005 08:10:05 -0800
Thanks for your reply.
First of all, it's not always possible to have a router to block it, for
several reasons: They don't necessarily know how to use it or need it (or it
would take me too much time to help everyone of them setup things -- come on,
I'm working for my company, but not for personal stuffs!!). And those
portable PC owners are sent elsewhere in the country and they're most
probably connected to Internet through 56K modem, or WiFi for some lucky guys
and in such case, there's no router.
If you're to tell me to activate the software firewall. Well .... they
can't. Several reasons too:
They're using VPN client to connect back to my corporate network and
unfortunately Microsoft's firewall isn't compatible with it.
And even not talking about VPN, your firewall is blocking a lot of other
things, like Symantec Anti-virus server-push virus definition update. It's
also blocking SMB protocole!! (I can't believe this!)
And to the question why "net send" is preferred to email? One of the
reasons is its reactiveness. When you send out emails, you have to be sure
your addressees have read the mails within a certain amount of time, eg a few
hours (when we're busy, it's not unusual that we're not reading mails for
several hours) But when I've some urgent messages to broadcast, like
shutting down such and such server within 10 minutes (or less), I'd use "net
send' to send it to make sure that those connected locally have received it.
Remotely users aren't affected directly in such circumstances.
So you see the usefulness of "messenger". I'd like to listen to any
comment or suggestion, or even to use alternatives to "net send" (except
email).
Thanks
"Ben Winzenz [Exchange MVP]" wrote:
> There is no way to do that that I know of, but any home router with a
> firewall should prevent net send messages from getting to the computer...
>
> Out of interest, why use Net Send to send important messages? Does e-mail
> not work? I'd argue that it isn't widely used anymore. On my fresh build
> of XP Pro with SP2, it is disabled by default.
>
> --
> Ben Winzenz
> Exchange MVP
> MessageOne
> Read my blog!
> http://winzenz.blogspot.com
>
>
> "TFS" <TFS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A188D205-93DD-45DA-A7CF-843C8959522B@xxxxxxxxxxxxxxxx
> >I use quite a lot of "send net" to broadcast important messages to the
> >whole
> > domain. But the "messenger" service has to be started in order to receive
> > messages. However, more than half of the computers are portables that the
> > owners could bring back home. And when they're home, they're connected to
> > Internet with every mean available to them. And it's better that the
> > Messenger service is stopped to avoid spam messages from Internet or other
> > virus.
> >
> > So, is there a way to start this service when these portables are
> > connected
> > to the AD. And when they're not connected to the AD, the service should
> > be
> > stopped.
> >
> > TIA
>
>
>
.
- Follow-Ups:
- Re: Anyway to start the "Messenger" service only when connected to
- From: Andrew Dadmun
- Re: Anyway to start the "Messenger" service only when connected to
- From: Ben Winzenz [Exchange MVP]
- Re: Anyway to start the "Messenger" service only when connected to
- References:
- Re: Anyway to start the "Messenger" service only when connected to AD?
- From: Ben Winzenz [Exchange MVP]
- Re: Anyway to start the "Messenger" service only when connected to AD?
- Prev by Date: Re: Error 8197
- Next by Date: Re: Deleted Distro group remains in the Global Address book - Help!
- Previous by thread: Re: Anyway to start the "Messenger" service only when connected to AD?
- Next by thread: Re: Anyway to start the "Messenger" service only when connected to
- Index(es):
Relevant Pages
|