I was able to download the new 2.2.4,version of Samba and have followed the steps to install from Objects. I am new to VMS and have no one on site who knows VMS that well.
Now that I run samba_startup I show sys and do not see the NMBD process as I did in the earlier version, however I do get a process number after running script. $ @samba_startup %RUN-S-PROC_ID, identification of created process is 00000AC2 I have a very simple smb.conf that uses my Win 2000 machine name in the workgroup. All I need to do is a copy from my PC to the share drive on VMS. However with the new version I am getting this error C:\>copy uiprint.txt \\servername\slbfile The semaphore timeout period has expired. 0 file(s) copied. And I get these error the the log.starbucks 2002/12/23 13:48:15, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_4-SRC.SOURCE.LIB]UK.C;8:(1018) getpeername failed. Error was socket is not connected 2002/12/23 13:48:16, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_4-SRC.SOURCE.LIB]UK.C;8:(505) write_socket_data: write failure. Error = broken pipe 2002/12/23 13:48:16, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_4-SRC.SOURCE.LIB]UK.C;8:(1018) 2002/12/23 13:48:16, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_4-SRC.SOURCE.LIB]UK.C;8:(529) getpeername failed. Error was socket is not connected write_socket: Error writing 4 bytes to socket 3: ERRNO = broken pipe 2002/12/23 13:48:16, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_4-SRC.SOURCE.LIB]UK.C;8:(505) 2002/12/23 13:48:16, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_4-SRC.SOURCE.LIB]UK.C;8:(709) write_socket_data: write failure. Error = broken pipe (See attached file: smbx.conf) ________________________ Diane Gonzales Informatics Support, ABI 800-762-5467 Option 1 [EMAIL PROTECTED]
smbx.conf
Description: Binary data