I've got a device on my network that is
supplied by a vendor. It is Caldera Linux,
running Samba.

I've setup a regular Linux user, as well as a smbpasswd
added user.

\n[broom@mash prisma_bin]$ smbclient -L XXX.25.223.131 -N\nAnonymous login successful\nDomain=[PRISMA-EAST] OS=[Unix] Server=[Samba 2.2.8]\n\n        Sharename       Type      Comment\n        ---------       ----      -------\n        u               Disk      U-Filesystem\n        hotdirs         Disk      Hotdir top level\n        simplex         Disk      Simplex Hot Folder\n        duplex          Disk      Duplex Hot Folder\n        simplex-pn3-f   Disk      Simplex Hot Folder for Printnet 3 with f-def=f100ld\n        duplex-pn3-f1   Disk      Duplex Hot Folder for Printnet 3 with F-def=f100ls\n        IPC$            IPC       IPC Service (Oce Prisma East Samba Server)\n        ADMIN$          Disk      IPC Service (Oce Prisma East Samba Server)\nAnonymous login successful\nDomain=[PRISMA-EAST] OS=[Unix] Server=[Samba 2.2.8]\n\n        Server               Comment\n        ---------            -------\n        OCE98450EAST         Oce Prisma East Samba Server\n\n        Workgroup            Master\n        ---------            -------\n        OCE                  WEB4\n        PRISMA-EAST          OCE98450EAST\n        WORKGROUP            OPS\n\n

As you can see, I can talk to it from my Linux
server. But I want to be able to smbclient to
a particular share.

Every attempts tells me my password is wrong.

\n[broom@mash prisma_bin]$  smbclient  //XXX.25.223.131/u -U mashspl\nPassword:\nsession setup failed: NT_STATUS_LOGON_FAILURE\n

The log entry is:

\n[2005/03/26 17:44:08, 0] passdb/pampass.c:smb_pam_passcheck(827)\n  smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User mashspl !\n

I've also tried adding the workgroup, ie:

\n smbclient  //XXX.25.223.131/u -U mashspl -W PRISMA-EAST\n

When I use the same smbclient command on the local box, it
lets me in without a problem.

\n[root@oce98684 samba.d]# smbclient  //XXX.25.223.131/u -U mashspl -W PRISMA-EAST\nadded interface ip=XXX.25.223.131 bcast=XXX.25.223.255 nmask=255.255.255.0\nadded interface ip=XXX.25.223.150 bcast=XXX.25.223.255 nmask=255.255.255.0\nPassword:\nDomain=[PRISMA-EAST] OS=[Unix] Server=[Samba 2.2.8]\nsmb: \\>\n

I can also connect to it from my WinXP laptop using the same
name and password without a problem, so it has to be specific
to mash.

Any ideas?

Note: I cannot update the Samba software on the box, out
of my control area.

Security implication?
Stability?
How is mash able to be a server and not a client.

Make the change, bounced smb.

One thing I noticed.

When I use smbclient (when it works) I notice the "added interface" lines, ie:
added interface ip=XXX.25.223.131 bcast=XXX.25.223.255 nmask=255.255.255.0
added interface ip=XXX.25.223.150 bcast=XXX.25.223.255 nmask=255.255.255.0

But I never see that when I do it from mash.