smbclient -M "Cannot resolve name"

[TobyR]

I'd like to send a pop-up to my WinXP PC from Linux machine (why? - just for the fun of it).
Having looked into it, I tried the following command from the Linux box:

smbclient -M HOME-PC "Hello"
.. and got ...
added interface ip=10.0.0.254 bcast=192.168.0.255 nmask=255.255.255.0
Cannot resolve name HOME-PC#0x3


But,

# smbclient -N -L HOME-PC

gave

added interface ip=192.168.0.254 bcast=192.168.0.255 nmask=255.255.255.0
Got a positive name query response from 192.168.0.11 ( 192.168.0.11 )
Domain=[HOME] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
IPC$ IPC Remote IPC
SharedDocs Disk
print$ Disk Printer Drivers
hpdeskje Printer hp deskjet 5550 series

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

Workgroup Master
--------- -------



... which makes me think there isn't anything wrong with name at all.

Any ideas? Thanks in advance.

[ph34r]

What happens when you use the IP of the windows machine instead of the name?

[TobyR]

Good point.

added interface ip=10.0.0.254 bcast=192.168.0.255 nmask=255.255.255.0
session request failed


Thanks.

[ph34r]

Is it possible that messaging is blocked or disabled on the windows machine?

[scinerd]

I was able to reproduce both errors with a windows 2k box. The errors happen when you stop the "messenger" service. I'm guessing xp has one to. See if it's stopped and if it is then starting it might fix the problem.

[TobyR]

As far as I can tell the service that allows win pop ups is 'Messenger' and that's running. Although the symptom suggests that the WinXP box is refusing access ('session request failed') in fact I can tell from Snort that no the command doesn't get outside of the Linus box.