Just Installed Fedora Core 5, Samba Client Installed Newest Version Im Guesing.
Made Sure My Windows System Is Running The Messenger Service And Tested With Another Windows Machine With Net Send, It Worked. Read Many Forums & Google Searched But Cant Seem To Get It To Work. Ive Tried Linpopup But It Gives Me The Same Error Message, (session request failed/Connection to xxxxx failed)As The smbclient Command Does. I Can Ping The Windows System, Net Lookup Both The Machine Name And Ip Address Just Fine. Also I Can Connect To The Windows System Through The File Brower And Do Whatever I Want As If I Was On A Windows System. So Im Thinking Its Something To Do With Samba smbclient -M Switch. Ive Read Some Google Searches Where It Said Something About Editing The smb.conf but Im Not Sure What Command I Need Or Even If I Need To For This Purpose.

This Is What I Get In The Terminal.

[DiscreetControl@localhost ~]$ smbclient -M dim2350
Connection to dim2350 failed
[DiscreetControl@localhost ~]$ smbclient -M 192.168.1.101
session request failed
[DiscreetControl@localhost ~]$ smbclient -p 139 -M dim2350
Connection to dim2350 failed
[DiscreetControl@localhost ~]$ smbclient -p 139 -M 192.168.1.101
session request failed
[DiscreetControl@localhost ~]$

It Looks As If Samba Isnt Resolving Host Names. I Have A Router But I Dont Think I Have To Open This Port Due To Another Windows System Being Able To Net Send.

If You Need Any Other Information Just Let Me Know

Thanks In Advance

Try doing an 'smbclient -L HOST' to see if it can even get a list of resources. And remember you should be using NetBios names, not DNS names.

This Is What It Gave Me When I Tried smbclient -L

[DiscreetControl@localhost ~]$ smbclient -L 192.168.1.101
Password:
Domain=[DIM2350] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
Printer Printer hp deskjet 845c
session request to 192.168.1.101 failed (Called name not present)
session request to 192 failed (Called name not present)
Domain=[DIM2350] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Server Comment
--------- -------

Workgroup Master
--------- -------
[DiscreetControl@localhost ~]$ smbclient -L DIM2350
Password:
Domain=[DIM2350] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
Printer Printer hp deskjet 845c
Domain=[DIM2350] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Server Comment
--------- -------

Workgroup Master
--------- -------
[DiscreetControl@localhost ~]$

What Do You Mean Use NetBios Names And Not DNS Names?

Well, it's obviously able to connect to the server and authenticate successfully. It's possible that the remote system has the messenger service disabled, and so you are unable to send messages to them.

Thats The Problem I Know The Messenger Service Is Running As I Mentioned In The First Post.
I Setup The Messenger Service To Start And Start With Windows Personally On The Windows Box.

What Do You Mean Use NetBios Names And Not DNS Names?

Ok I Did Some More Research And I Added This To My smb.conf File. I Read By Adding This I Would Be Able To Recieve Messages...

message command = csh -c 'xedit %s;rm %s' &

Tried To Send A Net Send From Windows And Nothing...
But When I Tried To smbclient -M To The Windows System It Worked As Long As I Used DIM2350 Instead Of xxx.xxx.xxx.xxx.

[DiscreetControl@localhost ~]$ smbclient -M DIM2350
Connected. Type your message, ending it with a Control-D
Worked
sent 8 bytes
[DiscreetControl@localhost ~]$ smbclient -M 192.168.1.101
session request failed
[DiscreetControl@localhost ~]$ smbclient -M DIM2350 -I 192.168.1.101
Connected. Type your message, ending it with a Control-D
Worked
sent 8 bytes
[DiscreetControl@localhost ~]$ smbclient -p 139 -M DIM2350 -I 192.168.1.101
Connected. Type your message, ending it with a Control-D
Worked
sent 8 bytes
[DiscreetControl@localhost ~]$

Can Someone Tell Me Why smbclient -M Works Now. And Also Why IT Doesnt Work With The IP Address. And Also Why Im Not Able To Send Messages To The Linux System From Windows.

Or Am I Like The Only One With This Problem.

xedit cannot be run from the message command unless a DISPLAY is specified for it to connect to. Hence, the message is received, but it is unable to handle the message.

As far as putting in the IP address, you have to specify the destination by the Netbios name of the receiving machine.

linpopup works great for me - I can send messages in both ways. I don't know how does samba catch messages in command line, but Linpopup shows them. Hope this helps