similar to: Problems with smbpasswd on a solaris 2.5.1 server

Would anyone have experience or a prediction about the feasibility of using the pre-compiled solaris 2.5.1 executable on a solaris 2.5.0 system? Thanks for any advice on how well this might work. Frank R.Brown Frank.R.Brown@MailAndNews

Does anyone have Samba working on Solaris 2.5.1? I posted more or less the same question a few months ago, and didn't hear anything back, but the issue has reared its head again on my end. I have Samba 2.0.0 running successfully on Solaris 2.6, but have failed in repeated attempts to get Samba running on Solaris 2.5.1. Basic symptom: I can get the daemon running, but can't connect to

I have a samba server at ip address aaa.bbb.ccc.ddd I can connect to it from clients on subnets aaa.bbb.eee. and aaa.bbb.fff. I can't connect to it from clients on ggg.hhh. smb.conf has hosts deny = all hosts allow = localhost, aaa.bbb., ggg.hhh. The client can successfully 'ping mysambaserver' (resolves to aaa.bbb.ccc.ddd). Doing 'net view \\mysambaserver' fails with

I see that mksmbpasswd.sh (plus a little editing) would be a good way to set up users with "NO PASSWORD" in bulk. But suppose I don't want the risk of the "NO PASSWORD" approach. Now somebody with root access must run smbpasswd for each user they want to activate. But can't I just do this anyway (with the -a 'add user' option), without ever having run

I have been using (actually inheareted the system) a file for the Samba password database using since something during the 2.0 erra. New accounts have been successfully added and users are apparently logging in ok. After installing 3.0.6 I am seeing these things in my log (log level=3). mod_smbfilepwd_entry: Using old smbpasswd format. This is no longer supported.! 1. What is the

Hello again, I would like to thank Giant Wang and Miquel Bonastre for their responses to my query in "Samba Digest 1734" regarding simultaneous passwd changing for users via Samba. Their comments were helpful, but have not solved the problem. For those who do not have a back log of the Digests, the problem is that with unix password sync=yes, users are not able to change their own

I have (more than) three subnets: A: all unix (I think) B: mixed unix and PC's C: all PC's (I think) I have a samba server on both A and B. They have essentially identical configurations. Both are running the nmbd daemon, and are configured as workgroup = XXSAMBA. I have a PC on C. Both net view /domain:XXSAMBA and network neighborhood show only the server on B. I assumed that

I'm hoping this turns into another case of 'knowing it works makes it happen.' I am involved with a unix clearcase installation which now needs to work with nt. We have clearcase 3.2.1 running on both the unix and nt side. Because we have checkin/checkout triggers hooked to some unix-side stuff, we need the unix views to be accessible from nt. Does anyone have direct experience

I am very confused by how our browsing works. I have three samba servers on two different subnets all set up to be in the same workgroup. (No other machines are in that workgroup.) None of them have a guest account set up. When nt clients browse the network (in explorer's map network drive), they do see the samba workgroup. If you click on the samba workgroup, some clients are given the

Hi, I just got a comment from one of my IBM support engineeres that there is a problem with auth-passwd.c only calling authenticate() once. He claims it should potentially be called several times, in case several authetication methods are defined in /etc/security/user. F.ex.: SYSTEM = "NIS and DCE" Suggested (untested) patch should look like: ----------------- cut

We have come across a problem with OpenSSH 2.3.0p1 (and still in 2.5.1p1) which affect authentication on an AIX 4.3 system. The code in auth-passwd.c at line 168 reads: #ifdef WITH_AIXAUTHENTICATE return (authenticate(pw->pw_name,password,&reenter,&authmsg) == 0); #endif however, the AIX manual page for "authenticate" states: "The authenticate subroutine maintains

When the world was young, "Frank R. Brown" <list.Frank@MailAndNews.com> carved some runes like this: [snip] > I have two concerns: > > The first is that I don't understand what is going on, so I'm worried that > this setup will turn out to be flaky. The only thing flaky in this setup are the various incarnations of windoze... See below. > Secondly, I

Hi, This is a very scary problem I have here. I use a precompiled 2.0.6 samba on my SGI IRIX 6.3 system. I also have smbpasswd file setup. When I tried to change the samba password using smbpasswd program ( from a non root account whic I use) I got an error messgae saying that it cannot change the password. My goodness, I found that the instead of changing password for my account smbpasswd

I am at a loss. I have two SUNs and 10 PCs (W95) on our network. One SUN box runs Solaris 1.1.1, it has four serial printers (old printers never die they just...) running from a serial extension card. Users validate when the come to their PC so they can access the printers and the disks on the SUNs. The second SUN runs 2.5.1 and I wanted to move the printer activity there with time. I created two

http://bugzilla.mindrot.org/show_bug.cgi?id=17 Darren.Moffat at Sun.COM changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From Darren.Moffat at Sun.COM

I've discovered a problem with OpenSSH 2.9.9p2 under Solaris 2.5.1 . In auth.c, secure_filename() walks upwards toward the user's home directory or the filesystem root, verifying that no directories along the way are group or world writable. Solaris 2.5.1's dirname() function has a bug where dirname("/.ssh") returns an empty string instead of "/". This causes

Aside from the u_int_8 thing, Solaris 2.5.1 has some other problems. For some reason even the newest gcc's preprocessor can't grok #define blah (x,y) (stuff using x and y) as opposed to #define blah(x,y) (stuff using x and y). also, getsockname() expects its "tolen" parameter to be initialized for some reason. This patch seems to fix any problems with 2.5.1. It includes my

http://bugzilla.mindrot.org/show_bug.cgi?id=558 Summary: configure broken_dirname checks not run on Solaris 2.5.1 Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

Hello all, I am still expecting someone to help with this problem Thanks > -----Original Message----- > From: Olusanya, Olukunle O > Sent: Thursday, April 01, 1999 8:13 AM > To: 'samba@samba.org' > Subject: Printing Problem with Samba running on Solaris 2.5.1 > > Hello, > > Until 2 weeks ago, Samba 1.9.18 running on my Solaris 2.5.1 system was > working

Try adding these to your smb.conf after the 'set printing = bsd' and restart your daemons load printers = No disable spoolss = Yes show add printer wizard = No btw, be sure to remove the quotes from the lines (i.e. set "printing=bsd" should read: set printing = bsd not set "printing=bsd" (you probably knew that already) Are your Windows clients trying to print