I'm still having problems printing from Win95 or NT 4.0 to my SAMBA server (RedHat 4.2). I just upgraded SAMBA to 1.9.17p1 and tried the default smb.conf, only changing the workgroup name. It still gets the print file and holds it in the spool directory until I manually lpr it. I have gotten mail from other users getting the same problem. Any suggestions?? Quinn
> Date: Wed, 10 Sep 1997 17:43:49 -0400 (EDT) > From: "spatel@webfirst.com" <spatel@webfirst.com> > To: samba@samba.anu.edu.au > Subject: PLEASE HELP with SMBTAR > Message-ID: <Pine.SOL.3.91.970910174049.2617R-100000@seuss> > > Hello > > I have read the docs for smbtar a million times, and I am sorry if > this is dumb but can someone please tell me the syntax > to restore from tape to an NT box. I have been trying this command > with no luck: > > smbtar -s PHOENIX -x cdrive -u administrator -p password -r -l 1 sanjayYou need to specify the filename/tape device (unless it is the default - tar.out) -t archiveName i.e. smbtar -s PHOENIX -p password -x cdrive -u administrator -t /dev/rmt/0m -r -l 1 sanjay (assuming sanjay is the directory you want to restore) - if you just want everything, you can (probably) omit this. Pat Sullivan psullivan@inri.com (401)849-3524
On 12 Sep 97 at 3:42, Tim Winders <twinders@spc.cc.tx.us> wrote:> Date: Wed, 10 Sep 1997 14:08:20 -0500 (CDT) > From: Tim Winders <twinders@spc.cc.tx.us> > To: Luke Kenneth Casson Leighton <lkcl@switchboard.net> > Cc: Multiple recipients of list <samba@samba.anu.edu.au> > Subject: Re: logging out hangs win95 consistently > Message-ID: <Pine.OSF.3.96.970910140407.19673A-100000@barney.spc.cc.tx.us> > > On Wed, 10 Sep 1997, Luke Kenneth Casson Leighton wrote: > > > On Thu, 11 Sep 1997, Tim Winders wrote: > > > > > I am seeing the SAME problem... but there is no Samba in the picture. I > > > have this problem with NT4.0sp3, Netware 4.11, Netware 4.10, Netware 3.12. > > > > like i mentioned earlier, if you log out the same user from two machines > > simultaneously, you can get a reproducible case where one of the machines > > will hang. > > Yes, but, if I am logged in at two computers and try to logout from only 1 > of them, the machine will lockup almost 100% of the time. > > > at this point, given that you are seeing this with NO samba servers > > involved, i think it might be time for someone to give microsoft a call, > > or to see if this issue has been covered on any of the KB or other > > documentation. > > Microsoft has a KB on Troublshooting Shutdown Problems, but none of the > issues are related to networking. The fixes presented in the document do > not fix the problem. > > > i can't believe that it hasn't been experienced before, and reported to > > microsoft as a bug. > > Neither can I, but... I have posted a message to the Win95-L but received > NO responses. It seems to me to be a Win95 BUG, but, with OSR2.1 you HAVE > to go to the vendor for support. I have tried to call Microsoft and I was > told that is an OEM product and to call the vendor...IMHO the discussion is going in the wrong direction: OSR2, samba updates, domain logons, logging out at the same time, etc. Here is my $0.02: It's definitely not OSR2.1 related: I've been having this problem since the first release of WIN95. Out of a dozen systems in our network, one machine consistently has this failure. (Samba, no domain logons !) Last month I replaced the hardware, made a fresh WIN95a install, and enabled user profiles, domain logon, roving profiles, the whole stuff (still no NT in the network !): Guess what, the new system has the same problems as the old one. Some more strangeness: You may have noticed that the keyboard is still working, but somehow WIN95 won't accept anything alphanumerical. But one can cut and paste letters of the user name to the password field ! At some point I pressed escape to enter windows without domain logon, clicked around to the keyboard configuration screen. Then I played with the settings a little, made no real changes and logged off again. At that point I was able to enter a password ! Hope this helps, Bas.> > --------------------------------------------------------------------- > | Tim Winders, CNE | Email: twinders@spc.cc.tx.us | > | Network Administrator | Phone: 806-894-9611 x 2369 | > | South Plains College | Fax: 806-897-4711 | > --------------------------------------------------------------------- >-- Bas Laarhoven Vimec Applied Vision Technology BV phone: +31 40 255 06 07 Meerenakkerweg 1, 5652 AR bas@vimec.nl fax: +31 40 252 67 25 Eindhoven, the Netherlands
Yeah! Samba is DEFINATELY the problem. Running Samba 1.9.17 acting as WINS server for multiple subnets. When shutting down Win95, it locks up MOST of the time. Samba is acting as a login server, but no one is logging into it. We have NT4sp3, NW411, NW410, NW312. Most users logging into a server are locking down. Many of those NOT logging in anywhere are locking down when they try to shutdown. Win95 is getting the WINS assignment through DHCP. I am using the ISC DHCP beta5.16 server. To test the problem, I removed the WINS assignment on the server and rebooted the problem Win95 machines. When they had NO WINS assignment they shutdown WITHOUTH A PROBLEM. I changed the nmbd debug level to 10 and added the WINS assignment back to the machines, rebooted and they ALL LOCKED DOWN when trying to shutdown. I did NOT try a different WINS server. The log.nmb file is ~6.7MB. I have made it available at ftp://ftp.spc.cc.tx.us/pub/log.nmb.10 so you can d/l it and try to figure it out... I tested this with 3 machines. Their names are TA123-03, TA123-04 and TA123-05. I HOPE this helps. If there is anything else I can help with, please let me know. It would be WONDERFUL to get this fixed! --------------------------------------------------------------------- | Tim Winders, CNE | Email: twinders@spc.cc.tx.us | | Network Administrator | Phone: 806-894-9611 x 2369 | | South Plains College | Fax: 806-897-4711 | ---------------------------------------------------------------------
i'm using nisgina-1.0.2.0 with a sunos 5.5 nis server running samba-1.9.17. this is working very nicely. i'm now trying to use sambapasswdd from nisgina-1.0.2.0. it built fine but i don't think nisgina is communicating with it properly. i ran the server and tested it using the sambapasswdd-client program and that seems to work fine. as expected, it updates the smbpasswd entry if the user's new password matches their nis password. i'm running nisgina on an nt 4.0 workstation with service pack 2. i've enabled 'use sambapasswdd' in nisginaconfig. for debugging, i edited sambapasswdd SAMBAPASSWDD_s.cc to print the password that was received by sambapasswdd rather than the ?? string. i then watch the sambapasswdd and nisgina log files as i log in using nisgina and i see the interaction as UpdateEncryptedSambaServers is called after a successful nisgina login. i see that sambapasswdd is receiving garbage rather than the password i typed and so the password change fails because this garbage doesn't crypt to my actual nis password. does anyone have any idea what's wrong? -- Todd Pfaff \ Email: pfaff@mcmaster.ca Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \