Messenger Service Partially Non-Functional

[J. L. Miller]

I just built a new system (Asus Maximus Extreme MB, Intel E8400 CPU, 4GB DDR3 RAM) and installed Windows XP Pro SP3. Everything is swell except that Windows Messenger service is only partially functional. (I need it only because my APC SmartUPS 1500 UPS provides power event notifications via the Windows Messenger service).

Doing a NET SEND 127.0.0.1 produces (after a fair delay) the message, "An error occurred while sending a message to 127.0.0.1. The message alias could not be found on the network. More help is available by typing NET HELPMSG 273." The help message essentially reiterates the same error condition.

However, doing a NET SEND 192.168.2.100 (my system's local network IP address) yields a successful result.

My hosts file contains only the single entry "127.0.0.1 localhost".

Any thoughts on what I might have done to cause this goof?

Thanks.

- John

[GrofLuigi]

There was a change in SP3 (or maybe SP2) - the mess service was changed to manual. See if it is. Also there may be other "security fixes" (cleaning their own mess).

GL

[J. L. Miller]

Nope, Messenger service is set to "automatic" and is running. It would have to be in order for me to be able to successfully broadcast a messaage to my local network IP address, as I noted is the case. I am only unable to broadcast to IP address 127.0.0.1.

- John