search for: beasys

.... Any pointers will he appreciated much. Thanks rakesh -------------------------------------------------------------------- Rakesh Jain Systems Administrator, MIS Dept BEA Systems, Inc. voice: +1-972-943-5135 4965, Preston Park Blvd fax: +1-972-943-5111 Suite 500 email: rakesh.jain@beasys.com Plano, TX 75093-5150 WWW: http://www.beasys.com/

.... Any pointers will he appreciated much. Thanks rakesh -------------------------------------------------------------------- Rakesh Jain Systems Administrator, MIS Dept BEA Systems, Inc. voice: +1-972-943-5135 4965, Preston Park Blvd fax: +1-972-943-5111 Suite 500 email: rakesh.jain@beasys.com Plano, TX 75093-5150 WWW: http://www.beasys.com/

james.strauch@beasys.com wrote : > The problem is with the share "beasw". (see config below) This share > contains executable installs for various standard PC desktop software. The > share works fine and is viewable and writable by both Windows95 clients and > Windows-NT 4.0 clients. But when try...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Trying to run ./configure and after a while of chugging along, I get this: checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs.fsize member (4.4BSD and NetBSD)... no checking for two-argument statfs with struct fs_data (Ultrix)... no checking if large file support can be enabled no checking

Hello Samba Guru's Your last solution was so successfull I though I would try one more question to throw at you. I am currently running samba-1.9.18p7 on a Solaris 2.6 Ultra Enterprise 450. I have the default service to be homes which loads auto_home map from a Solaris server. Logon works great from Windows95 and WindowsNT Workstation clients. But when I attempt to login to the samba share

> > Samba Fans: I currently have a number of samba servers running Samba-1.9.18 on Solaris 2.6. But each and every share requires the user to log in with not just the password but the correct username as well. Here is the interesting part. I left the security parameter as default, security=share. # Global parameters security = share workgroup = BEACORP [backup1]

Hello Samba Gurus: I have a unusual printing problem on a Samba server (version samba-1.9.18p7) on a Solaris 2.6 server. Basically I had 2 Solaris 2.5.1 machines that were retired when this new machine was deployed. Each individual machine had Samba shares and printers on it individually. Those file systems and printers were then duplicated on the new server. The version of Samba was the same