As some of you are no doubt aware, one of the later versions of Mac OS X (Tiger) has issues in connecting to Windows Server 2003. The only solution I have found that semi-works is to disable the Digitally Sign Communications option in Windows 2003. This option seems to be too much of a security risk.

Surprisingly, even though we can't connect to the server using the Mac GUI, I have been able to get access to the server using a shell and smbclient. My users, however are not that technically minded ot be able to transfer files this way.

One possible solution I have thought of is to write a script that will copy all the files in a specified folder to a specified share on the server. This works fine, until the script opens the smbclient, at which point the script stops. When I exit the smbclient, the script resumes.

My question then is, how can I get the script to execute certain commands INSIDE the smbclient???

Any help would be greatly appreciated. Thanks.

well I don't know much about the smbclient, but if it can take input from a file, construct the file in the script, upload it first & execute the smbclient in batch using that file as config.

You can also rsh multiple commands no?

My 2 cents...

Check the man page of smbclient, there is a switch option to execute commands in smbclient.