On my Samba server I created a directory called 'netlogon' and I put a batch file in there called 'login.bat'. Also did I create a share called 'netlogon' which points to the 'netlogon' directory. I set up samba to use a login script (login script=netlogon/login.bat). Strange enough it does not seem to be executed when Win95 clients logon. If I double-click the batchfile straight from the server after logon it works just fine. Can somebody help me out? Thanks in advance, Mark -------------- next part -------------- HTML attachment scrubbed and removed
> Mark Leupen wrote: > > On my Samba server I created a directory called 'netlogon' and I put a > batch file in there called 'login.bat'. Also did I create a share > called 'netlogon' which points to the 'netlogon' directory. > > I set up samba to use a login script (login > script=netlogon/login.bat). Strange enough it does not seem to beShould be logon script = login.bat The netlogon path is assumed Cheers, jerry ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
Hi Mark, Just put "logon script = login.bat". [netlogon] is assumed. JOhan>On my Samba server I created a directory called 'netlogon' and I put a >batch >file in there called 'login.bat'. Also did I create a share called >'netlogon' which points to the 'netlogon' directory. > >I set up samba to use a login script (login script=netlogon/login.bat). >Strange enough it does not seem to be executed when Win95 clients logon. If >I double-click the batchfile straight from the server after logon it works >just fine. Can somebody help me out? > >Thanks in advance, > >Mark
> Subject: RE: Printing problems > Message-ID: <00dd01bee387$c1a10d00$1c0100c0@allsportssupply.com> > MIME-Version: 1.0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: 7bit > > I can think of 2 problems. > > 1. JD's only take one session. so when your Win boxes try to get a queue > list (by asking Samba and samba doing an 'lpd') the win machine will hang > since the lpd request will not be answered by the JD until it is done with > it's current printjob. > > Solution: in smb.conf change the lpq command to 'echo "No Entries > Available"' this unfortunately is a limitation of JD's > > 2. If you JD's respond after being reset (i.e. pulling the plug on EX's) > then look over your Unix printing system. Something is amiss and it is not > handling time-outs from the JD correctly (i.e. back to the above problem. > lpd sends a printjob the JD is busy with that and then lpd gets another > print job from another queue to that JD and tries to print and gets no > response from the JD due to it being involved in the other printjob)I used to have this problem when printing to HP printers with jetdirect cards. What solved it was switching to printing to port 9100 on them rather than the normal unix remote printing setup. There is a good package called cti-ifhp which is a pinter filter for HP Laserjets which is quite handy too. Andrew -- Andrew Howell Managing Director Informed Technology E-mail: andrew@it.net.au Ph: 08 9380 4244 Fax: 08 9380 4354
Mark Leupen wrote:> I set up samba to use a login script (login > script=netlogon/login.bat). Strange enough it does not seem to be > executed when Win95 clients logon. If I double-click the batchfile > straight from the server after logon it works just fine. Can > somebody help me out?You have to configure your Client for MS Networks on your Win95 box. Check the box that says "Log on to Windows NT Domain". Next time you logon, your batch will be executed. Randy Wilkinson