Is there a good alternative to NET SEND for Intranet messaging 3

[FoxEgg]

I have used NET SEND on some W2000 networked machines and it worked well... More machines have XP Pro and it is a little less than friendly (ie I can't get it to work properly).

I tried downloading INTERCHAT3 (Freeware)... nope .. didn't like XP (TO be fair, the documentation mentions this)

Hence my question... on a 10 machine company where one party wishes to instantly message another... what alternaives are there ?

Thanks for suggetions.

JF

 

[linney]

Remember that in SP2 the Messenger Service is disabled by default and this may impact adversely on these type of programs.

Other communicators inbuilt in XP.

Winchat.exe
NetMeeting (Conf.exe)
Net Send (From a Command Prompt)
Remote Assistance.

 

[bcastner]

Check:

http://support.microsoft.com/?kbid=878468

Try: Quick Messenger, freeware

http://pages.videotron.com/mmoose/

 

[FoxEgg]

Thanks,

Do you mean that I have to 'enable' the Messenger Service to use NET SEND ?

I so that might prove to be an intellectual challenge for me...

JF

 

[bcastner]

Start, Run, services.msc
Find the Messenger service entry.
Start it.
Set its startup type to enabled.

 

[FoxEgg]

Well thanks... It turns out that the MESSENGER (about which you speak) is NOT related to MSN messenger... and that is about as clear as MUD... ( why couldnt Microsoft think of a different name ? )

I stretched my brain and worked through the CONTROL PANEL to PERFORMANCE AND MAINTENANCE to ADMINITRATIVE TOOLS to SERVICES and double clicked the MESSENGER... activated it and..

Bingo NET SEND WORKS !!!!

Thanks for the tips guys

JF

 

[FoxEgg]

Thanks again guys... and how did you do that ??? I posted my BRILLIANT solution (albeit slightly wrong) and Iwas the only one there... then whooompa BC slps two solutions ahead of me.... I guess whe must somewhat slower down here in the Antipodes...

Thanks BC I could only make STARTUP = Automatic, I will have to resume that is OK, cos that was all that was offered.

*************

Question about Winchat.exe... It runs and finds the other computers on the system BUT It tells me "the other computer did not respond" I tried calling from another computer... the same

Is there some flag or box that needs to be checked ?

J

 

[bcastner]

The other client must be already running winchat.exe

 

[FoxEgg]

I did that... However to be honest... I accessed one computer from home with radmin.... ran winchat... no answer

so I used VNC to control the OTHER computer and run WINCHAT... still no go.. from either

I wonder if all the remote access was confusing the poor computers..

I will try at work without remote access.

Cheers

 

[bcastner]

This sounds a better chore to give to Windows Messenger, the IM client.

There are many firewall issues, as well as Netbios issues, involved in trying to do this remotely.

 

[Tightpants]

We used CheezePopper which was fantastic but when we upgraded to Windows XP we lost the userlist.

As an alternative we tried RealPopup which was okay but not nearly as good as CheezePopper.

Both were freeware programs.

 

[bcastner]

I really know nothing about CheezePopper or its replacement, but if either depending on raw sockets I can possible help you if under SP1 or SP1a:

http://support.microsoft.com/Default.aspx?kbid=897656

 

[Tightpants]

I have installed QuickMessenger. Thanks bcastner.

 

[dstrong]

Does anyone know what Windows policy (in server 2000) to turn on to get this to hit all our pc's. Or possibly a registry entry. Also, how about the issue that net send will not cross subnets

Thanks
Doug

Doug Strong
All around techie
dstrong@stpetes.org

 

[bcastner]

dstrong:


Q1: In the logon script:

net start messenger

Q2: A registry edit is less elegant. Use the native NET command with the start parameter, or SC.EXE.

Q3: "Also, how about the issue that net send will not cross subnets."

Netbios naming is broadcast based and therefore will not traverse routers. You can implement WINS on the servers, or use the full syntax for NET SEND to access other domains in which you have a Trust relationship:

net send {name | * | /domain[:name] | /users} message

Parameters
name : Specifies the user name, computer name, or messaging name to which you want to send the message. If the information that you supply contains spaces, use quotation marks around the text (for example, "Computer Name"). Long user names might cause problems when you use them as NetBIOS names. NetBIOS names are limited to 16 characters, and the sixteenth character is reserved.

* : Sends the message to all the names in your domain or workgroup.

/domain:name : Sends the message to all the names in the computer's domain. You can specify name to send the message to all the names in the specified domain or workgroup.

/users : Sends the message to all users connected to the server.

message : Required. Specifies the text of the message.

 

[linney]

Prior to XP SP2 the Messenger Service was enabled by default.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Messenger, with the Start value of 2 (I think).

Net Send across Subnet.

http://groups-beta.google.com/group...ill+not+cross+subnets&rnum=1#e0cdf5f287de7592

http://groups-beta.google.com/group...D:2004-50,GGLD:en&q="net+send"+across+subnets

 

[linney]

If any machines are running Microsoft AntiSpyware Beta 1, it will pop-up a clickable message offering to disable the Messenger Service.

 

[FoxEgg]

I was obviously a bit slow on the pick up ... a Slow Ozzie...

Try: Quick Messenger, freeware

http://pages.videotron.com/mmoose/

Thanks BC, this QuickMessenger works well... and the price was unbeatable.

John Fox

 

[bcastner]

FoxEgg,
I like Quick Messenger as well.
I warn you that for the first week or two your office will see a decline in productivity as your users play with this new feature.

Best regards,
Bill Castner

 

[FoxEgg]

Already seen....

JF