Net Send Failure

On a Windows 2000 Server in MYDomain I can do the following
successfully:

Net Send JoeUser "test"

However on a Windows Server 2003 (Standard Edition) in MyDomain I get:

An error occurred while sending a message to JoeUser.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273.

If I enter: net send /DOMAIN:MyDomain joeuser "test"
net send comes back with:

The message was successfully sent to domain MyDomain

BUT... no popups are received.

Is there something common to a Windows Server 2003 server that I need
to configure to get this to work?

How does this relate to SQL Server 2000? I figure that if I can get it
to work via a command prompt that it will work for notification as well
-- which at this point it doesn't.

Thanks for any help.

RBollingerIn article <1114705456.439354.148620@.o13g2000cwo.googlegroups. com>, "robboll" <robboll@.hotmail.com> wrote:
>On a Windows 2000 Server in MYDomain I can do the following
>successfully:
>Net Send JoeUser "test"
>However on a Windows Server 2003 (Standard Edition) in MyDomain I get:
>An error occurred while sending a message to JoeUser.
>The message alias could not be found on the network.
>More help is available by typing NET HELPMSG 2273.

Most likely the messenger service is not enabled by default in Windows 2003.
This is a good thing; there is no authentication with the messenger service,
so that anyone at all can send those "popup" messages to you claiming to be
anyone they want. I rejoiced when I saw SP2 for XP turned that service off.

If you have to use this, you'll need to enable the messager service. It's
probably set to "disabled", so you'll need a reboot once you've set it to
"automatic" for it to start.

>How does this relate to SQL Server 2000? I figure that if I can get it
>to work via a command prompt that it will work for notification as well
>-- which at this point it doesn't.

Hmm. I think the same logic would apply to fixing an SQL server that doesn't
boot because the hard-drive failed; that too would prevent you from using SQL.

But I figured I'd be nice and answer it, anyway :)|||Enabling the "Messenger" service under the Services Applet corrected
the problem. No reboot was necessary. Yes it seems that a lot of the
services previously available by default in previous OS' are locked
down in Windows Server 2003.

It's people like you who make the newsgroups my first source for
finding solutions.

Thank you!

RBollinger

John C. Ring, Jr. wrote:
> In article <1114705456.439354.148620@.o13g2000cwo.googlegroups. com>,
"robboll" <robboll@.hotmail.com> wrote:
> >On a Windows 2000 Server in MYDomain I can do the following
> >successfully:
> >Net Send JoeUser "test"
> >However on a Windows Server 2003 (Standard Edition) in MyDomain I
get:
> >An error occurred while sending a message to JoeUser.
> >The message alias could not be found on the network.
> >More help is available by typing NET HELPMSG 2273.
> Most likely the messenger service is not enabled by default in
Windows 2003.
> This is a good thing; there is no authentication with the messenger
service,
> so that anyone at all can send those "popup" messages to you claiming
to be
> anyone they want. I rejoiced when I saw SP2 for XP turned that
service off.
> If you have to use this, you'll need to enable the messager service.
It's
> probably set to "disabled", so you'll need a reboot once you've set
it to
> "automatic" for it to start.
> >How does this relate to SQL Server 2000? I figure that if I can get
it
> >to work via a command prompt that it will work for notification as
well
> >-- which at this point it doesn't.
> Hmm. I think the same logic would apply to fixing an SQL server that
doesn't
> boot because the hard-drive failed; that too would prevent you from
using SQL.
> But I figured I'd be nice and answer it, anyway :)