samba 2.0.7 smbclient -M failure

Gert-Jan Vons vons at
Thu Apr 27 09:19:48 GMT 2000


after installing samba 2.0.7, I discovered that "smbclient -M <host>" no 
longer works.

Everything works fine when I use the smbclient from samba 2.0.6 (even 
with smbd/nmbd 2.0.7), but fails when I use the smbclient from 2.0.7.

With the 2.0.6 smbclient:

>$ smbclient -M alcina
>Connected. Type your message, ending it with a Control-D
>sent 6 bytes

With the 2.0.7 smbclient:

>$ smbclient -M alcina
>Unable to resolve name alcina

I have this problem in two different configurations:

  - samba 2.0.7 under freebsd 3.4 and a w2k client
  - samba 2.0.7 under solaris 2.5.1 and a nt4sp5 client

On both samba servers, I have "name resolve order = hosts" in smb.conf, 
and no wins server configured.

In both cases, the older smbclient binary from samba 2.0.6 works fine 
with the 2.0.7 smbd/nmbd.

Any ideas?

If it was easy, the hardware people would take care of it.

More information about the samba mailing list