[LouDogg]

Okay, first off let me say thx to any help anyone decides to give.

That being said...

I have access to a WinXP LAN, and on some of the puters I am easily able to use the "Net Send" service command with no problems. However, on some of the computers this happens: I will run the command, the commad prompt window will flash up, and instead of going away, and executing the command, it hangs there indefinetly until I click the "X". Now, I read as much as I could find, and was able to diagnose that the Messenger service was disabled on these computers. So, I of course enabled it. Also, I noticed that the Messenger Service stated that it was dependent on other services, so I checked those, just to find out that they were running fine.

So my question is this, if all of the services are running properly, what could cause this hang up?

Thank you again for any and all help...
Lou_Dogg

BTW - there are no other programs running so I don't think it is hanging due to anything like that. Besides this happens on more than one computer so it seems to be something bigger than just having a computer glitch.

 

[GICodeWarrior]

It is a networking thing... I can reproduce the probelm on some of my computers sometimes... Only guarantee I can think of is if you use the IP instead of the NetBIOS name. Also Firewalls could shut something like that down pretty quick.

Bottom line its the network in general and not the windows services that are running or anything like that.

~GICodeWarrior :trnsfrm:

 

[johnwill]

I'm confused, you say messenger service was disabled, that would cause the problem. Did you start it, or did you change the properties of it to automatic and reboot? If it worked when you enabled it, what exactly is the issue?

 

[Pseudocyber]

Bottom line its the network in general and not the windows services that are running or anything like that.

~GICodeWarrior :trnsfrm:

I have to disagree with that - and as a network engineer, it's a personal pet peeve.

It's clearly an application issue. The network doesn't care what app it is - the network sends the traffic. If it's addressed correctly and the transport protocol is functioning correctly it will get it there. It's up to the app to listen and pick up and act on the traffic.

This is generally speaking. There are "network" devices such as firewalls and routers with Access Control Lists (ACL's) which can block traffic - but assuming you don't have any of these devices set up, it sounds strongly like an application/configuration issue.

 

[GICodeWarrior]

I think we are saying the same thing... I am just saying that it isn't the messenger itself. If he has a software firewall running it could wreak havoc on a Windows based network if improperly configured. It could also be a number of other windows things like if there are different OS's I have seen a tendancy for them to dislike each other.

I understand what you are saying, I think, but I also think I let myself open to misinterpretation.

I hope that I have correctly explained myself.

~GICodeWarrior :angel:

 

[Pseudocyber]

Ok. No prob.