similar to: netlogon error?

Greetings all, I'm trying to connect to the default shares Windows NT workstation enables for "administration" purposes but I'm not having any luck. smbclient can see the shares: [esisler@shaun esisler]$ smbclient -L ghost added interface ip=198.243.2.206 bcast=198.243.2.255 nmask=255.255.255.0 Got a positive name query response from 198.243.2.200 ( 198.243.2.150 ) Password:

Greetings all, I'm still struggling with Samba 2.0.7-4 on a RedHat Linux 6.2 box and I'm wondering if there are any known issues when using samba on a box with multiple processors. I *seem* to recall reading something about this quite awhile ago, but I can't find it and don't remember enough about it to be useful. :-( Currently I'm using 1.9.18p10-52.4 on the box

Greetings all, I hope this is appropriate for this list, if not I'll take it somewhere else. ;-) Printer lock-ups: I have some printer shares available on my Samba server (RedHat Linux kernel 2.0.32, Samba 1.9.18p3) and they are working just fine in most cases, but from time to time the Win '95 client will either lock up while printing or send a print job samba & lpd don't like

Hi, WOW, this was posted over a year ago! A response now. The problem still exists. As reconfirmed in a post i read not to long ago (within the last 2 weeks?). HP jetdirect cards can only do one thing at a time. (HP has been writing Jetdirect firmware for 5 years, PLEASE HP you _MUST_ have the ability to fix it?! Or don't you??) This can be confirmed if you have an NT only shop. In the

Greetings all, I'm attempting to move a Samba-2 PDC to a new server and upgrade it to Samba-3. I'm seeing the error message "get_md4pw: Workstation WS1$: no account in domain". I have read the instructions at: http://www.samba.org/samba/docs/man/Samba-Guide/upgrades.html The new server and a test workstation (WS1) are on a separate network to avoid interference with the live

Greetings all, I apologize for the lateness of this reply. I've been having (and still am) problems with my local telco. I'm lucky to connect at 9600 at this point and even then it's not exactly an error-free transmission. <sigh> I wanted to thank those who offered advice & suggestions concerning my file locking problem. I have tried every combination of oplocks, strict

Hi all, we've just recently switched to a new file server upgrading to samba 2.0.3. Unfortunately I've noticed that a couple of times a day a smbd process dies with 'oplock break failed' so I actually had to turn off oplocks thus degrading performance drastically. Does anybody have any idea why oplock breaks are failing so often now? Cheers, --- Martin Hoffesommer Soft

My boss asked me to investigate a free (as in no cost) solution that would allow us to archive our AIX server onto the 12 gig tape drive sitting on our Linux server. I tried doing an SMB share with valid user set to root, but this apparently loses the permissions that the AIX box uses (everything is owned root/root), making it rather useless for backup and restore. Can SMB do what I need, or

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello: I've configured a Linux box with Samba to act as a secondary domain controller for an existing NT server. I've gotten everything working very nicely, all my file shares set up, etc. I've got 6 printers that I need to set up as print shares. The ones that speak Postscript or PCL were very easy to set up, and work admirably.

The "valid users" parameter already existed in version 3 of the SAMBA and indicated which users were allowed to access the share. The "username" parameter indicated which user should be used when it was not defined at the time of mapping. SMB.CONF [folder] ... username = userX valid users = userX, userY, ... To map the "folder" share, only the following line was

Hi! I'm having the following problem with samba 1.9.18 running on Linux 2.0.32: I can't map drives using MS Client 3.0 for Dos. I get "Invalid password for share (Error 86) from client when trying to map drives. --- smb.conf --------------------------------------------------- [global] domain logons = no dns proxy = no getwd cache = yes guest account = guest hosts allow =

I have a Samba 1.9.18p8 server running fine on a particular network: >From smb.conf: interfaces = 138.120.247.0/24 ..and all works well with PC's on that network accessing the Samba server. Now for the tricky part. I want to move all of my computers to a new Class C network: 192.168.164.0 I have the router setup with DNS working, etc. I migrated one machine over to that network.

Hello all, Got SAMBA running on a linux 2.0.32 box, and all is well. Looked over the docs and set up my printer with the (what I think) are correct entries. Basically, what the default smb.conf has. Testparms says it o.k.! And I can print (lpr) locally. Windows sees both printcap entries (inkjet and psjet), but any attempt to pring to them errors out. I then added the print command =

Hi, I have referred to the archive and some of you were having the oplock_break problem. Does anyone have any solution for this? Will reboot fix the problem? Please advise. regards, Bridget

this isn't strictly a samba question, but it is related in that i'm trying to a samba server as my domain master browser and multiple samba servers as local master browsers for a workgroup across multiple subnets. everything seems to be working wonderfully except for one WfWG host which does not show up in the browse list as expected. i notice that this host is announcing itself as a

Hi all! Here is my problem: I have installed RedHat Linux version 6.0 on a computer and I want to share its resources via samba. Unfortunately, my computer - which is running WfWg 3.11 for Eastern Europe and the trumpet winsock TCP/IP stack is not able to see the samba server. Other computers, running Win95, Linux and WfWg with M$ TCP/IP stack perform OK. I have tried the following combinations:

Has anybody got some experience with connecting machines running Windows3.1 or WfWG (3.11) to Samba? We would like to run a small lab network with user accounts and a shared printer off the samba box. Samba is running fine and there's no problem to connect to it from the Win95/WinNT machines... Any help appreciated. Frank Wornle, Glasgow Caledonian University Dept. of Engineering

HI all, ok. I read all the entries of this mailinglist with the subject nethwork path. I try everything but nothing happens. I have no more ideas what i can do. Pleaaaaaaasssseeee heeeeellllllppppp. (I also tried to walk throught document.txt) The problem: -Client Win2k -Server Suse Linux 8.0 with Samba -I completely installed and configured Samba. I walk throught the document of Samba. I tried

On Mon, Apr 30, 2018 at 05:04:29PM +0100, Rowland Penny via samba wrote: Hello Rowland. > I had to read this several times to understand it, then a few more > because I didn't believe it. Well. In the industrial environment you may find everything ranging from CPM-86 onwards... old things talk via RS-232 or 422, the LAN equipped are regarded as "modern". In general all are

Rudolf Kollien email: Rudolf.Kollien@medas.de Rudolf.Kollien@kollien.de *************************************************************************** Never trust a operating system you have no sources for *************************************************************************** Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions.