Samba 2.2.4 Error

[John E. Malmberg]

> Today's Topics:
> 
> 1. Samba 2.2.4 Error (Diane M Gonzales)
> 
> 
> --0__=87256C980071ADF38f9e8a93df938690918c87256C980071ADF3 
> Content-type: text/plain; charset=us-ascii
> 
> 
> 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.

The version of TCP/IP and OpenVMS, plus any ECOs for concerning TCP/IP 
or the C run time library may be needed to give you any advice.

If you have a C compliler installed, it's version could be helpful, as 
it could have installed a newer CRTL.

> 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.

Have you tried the tests in Diagnosis.txt?  If one was not provided in 
the distribution that you downloaded, a version can be found on a Mirror 
from http://www.samba.org.

> 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]

This is an indication of a general networking problem.  If you search on 
http://www.google.com for "SAMBA-VMS FAQ" one of the links should end up 
with a general list of potential causes to check.

I do not know if the producer of the 2.2.4 port has included or updated 
this listing.

> 
> (See attached file: smbx.conf)
> ________________________
 > Diane Gonzales Informatics Support,

> 
> --0__=87256C980071ADF38f9e8a93df938690918c87256C980071ADF3 
> Content-type: application/octet-stream; name="smbx.conf" 
> Content-Disposition: attachment; filename="smbx.conf" 
> Content-transfer-encoding: base64
> 
> OyBDb25maWd1cmF0aW9uIGZpbGUgZm9yIHNtYmQuDQo7IFRlbXBsYXRlIGZvciBWTVMNCjsgPT09
[Several pages of unreadble hash snipped]

Please do not post your smb.conf file, or large log files to this 
mailing list.  If someone needs more information from these to assist, 
they will ask for it.

As you can see, attachments do not make it through many e-mail systems, 
and ones that are tagged application/octet stream can cause the entire 
message to be blackholed by virus filters.

Unless you specifically know that the reciver can handle MIME, E-mail 
should always be plain-text only, no attachemnts.

-John
wb8tyw at qsl.network
Personal Opinion Only