[EMAIL PROTECTED] wrote: > > Hello, > > I have successfully installed SAMBA-2.0.3 on a VAX running VMS-6.2 > and TCPWARE-5.4-3 (this VAX's name is CLFTS2). > > I installed the same SAMBA-2.0.3 on another VAX (name = CLF10U) ... > but now I'm not able to get the smbd working correctly on this new > VAX. > <snip> > > [2002/06/26 13:38:55, 0] DSA1:[KITS.SAMBA-2_0_3.SOURCE.SMBD]OPLOCK.C;1:(79) > open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was > can't assign requested address > [2002/06/26 13:38:57, 0] DSA1:[KITS.SAMBA-2_0_3.SOURCE.SMBD]OPLOCK.C;1:(79) > open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was > can't assign requested address
I am afraid that I can not be of much help, but here are some comments: I think you may need to ask someone familiar with TCPware to assist you with some of the debugging. Also I have never used Samba 2.0.3., but I think that oplock support may not be working in it. There may be an option in smb.conf to turn it off, so that SMBD does not try to create the oplock break socket. You would need to look at the source to determine what port it is trying to bind the oplock port to, and then use the TCPware utilities to see if something else already has the port. Be aware that Pathworks 6.x is available for OpenVMS VAX, and interoperates much better with Windows NT domains than any known version of Samba for OpenVMS does. There is an FAQ for Samba VMS that can be looked up at http://encompasserve.org or http://www.google.com [wrapped URL] http://eisner.encompasserve.org/htbin/ dnqindexform?TEXT=R30328472-30368736-dra4%3A%5Bdecuserve_extracts%5Dvms.full%3B415 -John [EMAIL PROTECTED] Personal Opinion Only
