Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

H

habanagold

12 Posts

3343

January 14th, 2004 11:00

NET Send fails on Windows 2000 systems, not on NT Systems

​From my Poweredge server running W2K Server, I can use the net send command to send to NT systems but not to any W2K systems. The following message is returned:​

​An error occurred while sending a message to ​​computername​

​The message alias could not be found on the network.​

​More help is available by typing NET HELPMSG 2273.​

​I have followed up on MS Technet and their solutions don't even come close (typical). The messenger service is running on all systems. This became a problem just recently and I noticed it when I started to get error messages in Veritas Backup Exec when it could no longer send status messages to the systems in question.​

​ ​

​ ​

DELL-MichaelC.

406 Posts

January 14th, 2004 12:00

habanagold,

Thanks for using the Dell Community Forum.

You really need to post this in the Server boards.  I think you would get a better response there.

habanagold

12 Posts

January 14th, 2004 17:00

 As usual, I solved my own issue. I am posting this so that others will benefit from the research.  I should charge Microsoft for solving this problem since no where in the KB did they even remotely come close to a hint on resolving this. At any rate here is the solutions.


I reviewed the Messenger service and found that it had 2 dependant services, Workstation and Remote Procedure Call (RPC). On the 2 manager workstations that I was having problems with, the RPC Locator ( not the RPC) was not running. After activating it on one system I did a test and the NET SEND command worked. On the other system, I still got a failure message. Further investigatio on the failed system revealed that the Messenger service was not set up to interact with the desktop under the Log On properties. Once this was checked, NET SEND worked.


 I don't know why these services were not running or why they were misconfigured.


 


 

habanagold

12 Posts

January 14th, 2004 18:00

 Well so much for my troubleshooting. The problem is back and I don't know why. The only thing I have done was update the virus definition files on the systmes in quesiton including the server.

It was suggested that I post this to the server forum. I don't think this is a server problem.

 

DELL-MichaelC.

406 Posts

January 14th, 2004 19:00

habanagold,

It may not be a server problem but at least it's a NT Server issue and I think you would get a better response if you posted it in the Power Edge section under Windows NT Server.

 

 

Hydralisk00222

2.4K Posts

January 16th, 2004 12:00


@habanagold wrote:

 Well so much for my troubleshooting. The problem is back and I don't know why. The only thing I have done was update the virus definition files on the systmes in quesiton including the server.

It was suggested that I post this to the server forum. I don't think this is a server problem.

Yep, Windows 2000 software problem if I understood this correctly.

Windows NT Server forum only covers 4.0. Windows 2000 is 5.0, so I think posting here is OK.

You definitely need to check the Services running. Maybe take look at services like Remote Registry Services and see if they are properly configured/running?

habanagold

12 Posts

January 16th, 2004 15:00

Is there any way to forward this thread without retyping everything?

View More

View All

No Events found!

Top