Re: Net Send Error

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jonathan Kay [MVP] (msnewsreplies_at_jonathankay.com)
Date: 03/09/04 

Date: Tue, 9 Mar 2004 03:30:11 -0500

Greetings,

None of the current updates should break this functionality (yet, Service Pack 2 will if not
configured otherwise). However, all the Windows XP PCs must have the 'Messenger Service'
running and the Windows XP Internet Connection Firewall disengaged in order for this to work.

To check to make sure the Messenger Service is running, click Start, then Run, type
"services.msc" and click OK. Scroll down to Messenger, right-click it and choose Properties.
Verify that the Startup type is set to Automatic and that the Service status is Running (if
it's not, click the 'Start' button).

To check to make sure that the Internet Connection Firewall isn't engaged, click Start, then
All Programs, then Accessories, then Communications and then Network Connections. Right click
your network/internet connection, then click Properties. Click the Advanced Tab, and verify
that the Internet Connection Firewall is unchecked.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

"dawnbringer" <dawnbringer@z6.com> wrote in message
news:AC1897DD-3AE7-49A4-AE19-C6E583D5679F@microsoft.com...
>I recently set up a a small wireless home network that consists of 3 desktops and a laptop.
>Two of these computers are running XP Professional, one is running XP Home, and the other is
>running 98se. My problem is this: I want to be able to exchange messages between the XP
>systems using the "Net Send" function out of the command prompt, but the computer running XP
>Home is unable to do so. I checked around, and apparently one of the Windows Updates
>disabled the "Net Send" command. However, I have been unable to find out which update so
>disabled my system. If anyone has encountered this problem and/or knows which update
>modified my command options in this way, I would appreciate a heads-up so that I might
>uninstall the guilty update.

Quantcast