Conference turris::digital_unix

    
    I think you mean SAMBA, the software which lets your Unix box act
    as an NT file server.
    
    Yes, samba runs on Digital Unix. Our group's DEC 7000 server is running
    it. Get the sources and build it.
    
    -Jeff D.
    
    

    The customer can get it from
    
    	ftp://samba.anu.edu.au/pub/samba/

    From the experience of those who have taken this code and recompiled
    it on Digital Unix, is it a simple recompile or do code changes need to
    be made?
    
    Thanks,
    
    Forough

It's an easy recompile.  I don't remember having to fiddle anything.

There also are binaries for dec unix at some ftp sites.

check 
	http://samba.canberra.edu.au/pub/samba

The only issue I've had with Samba is running C2. You have to compile
it with C2 support and if you do, your C2 password is restricted
to 8 characters or less... Not sure why this is (might be an SMB
restriction or just a samba buglet) but after I changed my password
it worked fine. 

			Pete

    I have a customer with samba as a very critical part of its production
    systems. We suport over 550 print queues, thousands of pages of
    printing a day, dozens of PCs doing file sharing.
    
    We simply pulled samba over the net, ran make and it has been fine.
    
    This may be one of the best examples ever of 'freeware' or whatever you
    want to call it. 

ANU is right across the road from here.

I remember years ago when some guy wandered in to speak to the "PC" guys (Dave 
Simpson and myself). He'd reverse engineered the SMB protocol with a packet 
sniffer and written a UNIX server, and wanted to know if we could do anything 
with it. What could we say?

We encouraged him and sent him on his way.

PJDM

    I guess we need to get few more enterprising individuals who could do
    the same with the Exchange so that we could run the Exchange client on
    Digital UNIX :-)
    
    - Vikas

You don't need an Exchange client on UNIX. See 
http://www.exchangeserver.com/testdrive/
(currently down to upgrade server capacities, despite the AphaGeneration logo on 
the page).

PJDM

    Can I use that capability _today_ to read the Exchange mail which is
    piling up in my Exchange mailbox?  I suspect unless the CCS which
    provides the Exchange services upgrade their servers to support the new
    capability, I am out of luck.
    
    - Vikas

    Another question on SAMBA:
    
    I can never access pathwork share from different LAN segment.  I don't
    know if that's the pathwork limitation or the way it has been
    configured by the system manager.
    
    Does SAMBA work across WAN ?
    
    - Vikas

    Samba seems to have no trouble across a WAN- my customer supports 530
    printers spread over the entire US on NT servers local to every plant
    and sales ofice. Smaler numbers of users of file sharing, but also
    acrosss the US.
    
    Having installed Pathworks a long time ago I resisted doing any kind of
    PC files service from unix because it seemed to be such a mess. I didnt
    believe how easy SAMBA was to setup, and in 2 1/2 years we have not
    spent 2 hours doing maintenance to samba or anything related to it.
    
    How a college guy could sniff out and hack together such a fine
    solution when we have had small armies of people on Pathworks to
    create an almost unseable package is an amazing story. 

    Amazing, simply amazing;  I spent total of 15 minutes or less on my own
    workstation and the things just worked!  I am absolutely impressed.
    It managed to export the cross-mounted disks with no problems at all.
    
    And all it needed was 8 pre-built images and 1 conf file which I
    edited.
    
    - Vikas

>    How a college guy could sniff out and hack together such a fine

University, not college.

PJDM

    I am still unclear as to how to set it up so that the shares will be
    available from
    
    	Win NT 3.51
    	Win NT 4.00
    	Win 95
    	Over WAN (without RAS, direct connect)
    	Over RAS (telephone)
    
    Lot of stuff do work but some of it works from one box but not from the
    other.  The insidious password caching in windows make debugging it
    next to impossible!
    
    - Vikas

I spent half a day reading through documetation before I figured out how to
export unix disks. And it works, I can mount them on my PC at home over the
phone line. And it was easy. 

The only problem I found on my 3.2c WS: when i kill smbd deamon, it kills my CDE
environment. I have not tried to run smbd on demand. Other than that it works
amasingly well.

>> Serge

    Hi,
    
       Vikias,  I think your WAN problem is a problem with your PC setup.
       You need to either update your lmhost file or run dns from your
       PC.
    
       I print and read files all the time from NT and Win95 to my
       PATHWORKS for Digital UNIX Server and to an NT Server.
    
    Paula

    Hi,
    
    SAMBA is a nice tool for users who need basic file and print from
    Microsoft clients to UNIX Servers.  This assumes the user doesn't need
    'offical' support.  If they do they are out of luck, thou there are
    a few contract shops around who might support them. Also since you
    have the sources and the stuff appears to be pretty simple you
    might be able to fix it yourself.  SAMBA is available for most UNIX 
    platforms.  If you just need to queue print jobs from NT to UNIX,
    you may want to look at the NT-Server Resource kit.  It has lpd for
    NT. Also there's an app called clispool kicking around that might do
    the job. 
    
    If you need full NT and WIN95 File Attributes, Account Creation
    flexibility, NT Peer Services, Highend Scalability (100's of users), 
    and management of UNIX 'PC NOS' environment from an NT Box, Advanced
    Server for UNIX might a better match you.  Also if your interested
    in things like integrating with NT V5.0 security, directory services
    and new browsing technology in the future it might be tough to track the 
    MS technology via a freeware code stream.  Since MS will likely support
    downlevel servers for years to come it's a safe bet that what works with 
    SAMBA today will continue to work long into the future.
    
    The Advanced Server for UNIX code is derived from the NT Server code.
    Many UNIX vendors OEM the code from AT&T.  HP, SCO, IBM (thru BULL) and 
    SUN (thru UniSource), Sieman, and Digital UNIX (thru PATHWORKS V6.x for 
    Digital UNIX).
    
    The AS/U product for Digital UNIX is new as of last June, so it sounds
    like you haven't given it a spin.  If your use to the NT Management Tools
    for managing remote 'computers' you'll like managing AS/U much better.
    AS/U on the Digital UNIX server can be managed from the NT system for
    many operations.  There's a UNIX based managment tool also.  It's
    pretty weak however.  It's being replaced overtime.
    
    So the right solution really depends on what your trying to accomplish. 
    Free is cool if it does what you need, and you have a support strategy
    in mind.  The AS/U product was designed to make UNIX a full Peer to 
    NT.  It was also designed to be manageable from NT.  Since AS/U is based
    on NT sources from Microsoft it will track the NT technology closely.
    
    Paula
    
    BTW: There's less the a platone working on Advanced Server for
         Digital UNIX :-)

    Hi Paula,
    
    I guess the Digital UNIX group is still paranoid and is staying with
    Advanced Server 3.51 for UNIX on their own production systems?
    
    Head to head comparison, SAMBA is _LOT_ slower than corresponding
    Pathworks or Windows NT Advanced Server but the nice thing about the
    SAMBA is that it is very lean.  
    
    I am running it on my lowly Pelican with 32MB memory / single RZ26
    disk.  All the paths which are  accessible to the Pelican can be made
    available to the PCs connecting to the Pelican.  The ability to
    pc-share nfs-exported volume from my own workstaion beats having to
    beg/bug the sys-admin folks who manage the production systems in ZK3.
    
    (It is also possible that the slowness of Samba might be due to the
     volume being remote-nfs mounted and also the lack of memory on the
     Pelican acting as the Samba server)
    
    Besides, I was never able to connect to my Pathwork share from home. 
    The access is allowed only through known PCs. 
    
    My current problem with the Samba is its interaction with NT 4.0 and the
    Exchange username (LastnameF type user names) conflicts.  The %U macro
    in the samba.conf works great from Win95 and WinNT3.51 but from NT4.0 
    either it says "wrong password" or says "network name not found".
    
    - Vikas