samba - Jul 1997 - SAMBA digest 1363

>Date: Mon, 21 Jul 1997 18:17:48 +0200 (MET DST)
>From: Hiran Chaudhuri <hiran@chaudhuri.indernet>
>To: samba@arvidsjaur.anu.edu.au
>Subject: Re: SAMBA digest 1355
>Message-ID:
<Pine.LNX.3.91.970721181423.28113A-100000@chaudhuri.indernet>
>
>
>
>> Subject: roaming profiles
>> Message-ID:
<Pine.BSF.3.91.970713134508.2508B-100000@cb1-gw.cb1.com>
>> 
>> 1) roaming profiles only work if your primary login is 'Client for 
>> Microsoft Networks'.  if, in the Network Control Panel, you select 
>> 
>> 2) it _might_ be the case that you have to use a WINS server to get 
>> roaming profiles to work.  if anyone successfully does this, without 
>
>Luke,
>
>how do I find out whether roaming profiles are active?
thinks.  log in a user on one w95 machine.  add some shortcuts to the
desktop or the start menu.  log out.  go to a second machine.  log in
again.  if those shortcuts appear on the desktop / start menu of the
second machine, roaming profiles are working.  ah, sorry, this explains
how to find out if they're working, not active.  oops!

if you want to _activate_ them on w95, read the.... DOMAIN.txt (or is it
LOGON.txt?) file with the docs distribution - i give full instructions
to w95 users as to how to switch them on.

i don't know about nt: i've not investigated this.  if someone sends me
some instructions, or i get round to physically setting up an nt
workstation (which i don't have - only NT server :-), i will incorporate
them into the documentation.
>If I understand roaming profile correctly, there should be a file on the 
>user's home directory where all the desktop settings a user customized 
>are stored. Is that correct?
correct, for w95.  it's called user.dat.  read the NT server "user
manager" help file, if you have access to it.  it's all explained in
gory detail, there.

regards,

luke
>

Further to my printing problem,

:>I've an odd problem with samba, running on SCO3.2.4.1. (sys.V)
:>Most PC's (runing win95 or NT) seem to print fine.
:>A few however will print the first print job OK, but will not print
:>again until either the samba deamon is restarted or the PC is 
:>reset, ....

:The usual problems are incorrect print commands in your smb.conf 
:file. One that we ran into with SCO Release 5 (3.2v5.??) was that 
<snip>
:we use for our printer->fax gateway on our system:
:   print command = /usr/local/bin/lp -dfaxprn < %s 2>> /tmp/plog%u; 
: rm   %s

After a bit of experimentation , it seems that samba is taking the 
first job, and sending it to the lp service correctly. For subsequent 
jobs, it takes the job, spools it in the place specified in the 
printer service section, and doesn't run the print command - I set 
the print command to just place a time stamp on the end of a log file 
and after the first go it just stops executing the print command for 
that client. Other clients carry on fine.
Here's my print command :
print command = date >>/tmp/smb.test;lp -c -R -d%p -o nocr %s >>
/tmp
/smb.test 2>&1
It used to be:
print command = lp -c -R -d%p -o nocr %s
And I briefly tried :
print command = date >>/tmp/smb.test
All behave in the same way, ie. they execute once and then stop 
thereafter for that client. 
-- 
===================== Ext : 247 ================== _o      Network Support for
TIS Software
O>O 
===================================================