I am having a heck of a time getting smbclient to work on my sgi irix box. I am trying to connect to a share that has been established on a windows 2003 box. I use ./smbclient -L 192.168.0.251 -U Test%letmein to connect with the test account that was created for me.

it spits the following out:
Domain=[DDSPA] OS=[Windows Server 2003 3790 Service Pack 1] Server=[Windows Server 2003 5.2]
tree connect failed: NT _STATUS_ACCESS_DENIED

I am not sure what else needs to be done.

Any help would be great. Thanks

My guess would be you need to specify a domain/workgroup in the smbclient command.

I tried doing that as well but I get the same result

Any other ideas as to what could be going on?

i'm getting something like that:
added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
session request to 192.168.0.244 failed (Called name not present)
session request to 192 failed (Called name not present)
Anonymous login successful
Domain=[XXX_XXX_XXX] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
Error returning browse list: NT_STATUS_ACCESS_DENIED

As I noticed, it is trying to do an anonymous connection... try without the '%' in your command -U Test%, of course, maybe you'll be asked for the 'Test' user password if any on your Windows box

Hi

I found out that modifiying all sorts of parameters means very little.
The only thing that works is to use pdbedit
pdbedit --user=<username> --create
it will prompt for the users password.
which manipulates the backend database. (whetever that is defined to be) and confirm with
pdbedit -L
which should list all users in the backend database

When you introduce users you create them and then
preferably at the same time assign a password.

NOTE: smbpasswd -a <username> may also be
used to create the user. To reset the passwd you
smbpasswd <username>

You would do this on a LINUX machine running SAMBA.
Of course if your server is not LINUX or UNIX ??

Active directory is a real hassle. Once you run DNS
and tell the Windows machine to use Active Directory
as well - then you can no longer run a successful
'export (DNS zones) to file', because it gets exported all right
but to a container within AD. SIGH!!!

Now if your AD hickups then so does your DNS server
and that can be really scary.

Kind Regards
Helpful.