similar to: local machine cannot find smb shares

Hello, I''d like to ask why is Rails fixing it''s version, like gem ''rails'', ''3.2.12'' ? Given the recent attacks on Rails - wouldn''t it be more secure to not fix the version? Maybe have something like ''~>3.2.12'' ? -- You received this message because you are subscribed to the Google Groups "Ruby on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Asterisk Gurus! I have a very simple question. I've just started playing around with Asterisk and BSD box. I also have grandstream ip phone and installed asterisk from ports. Now I'm on my very first steps to configure Asterisk. The question is: " How do I make Asterisk communicate with my Grandstream hard phone?" Thank you in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I run |#rsync --daemon and get this in /var/log/messages| #skywalker rsyncd[5522]: unable to bind any inbound sockets on port 873 #Nov 20 17:30:20 myserver rsyncd[5522]: rsync error: error in socket IO (code 10) at socket.c(482) [receiver=2.6.8] I run it on FreeBSD 6.1. Does anyone know what does the problem relate to? -----BEGIN PGP SIGNATURE-----

-----Original Message----- From: M. D. Parker [mailto:mike.parker@ga.com] Sent: Thursday, August 10, 2006 9:02 AM To: 'samba@lists.samba.org' Subject: HELP -- Problem with access list on samba 3.0.23b but not on 3.0.20c PDC I am using samba with NO windbind and a configuration file that has worked for years stopped working at 3.0.23b. The affect was that my [netlogon] area was not being

dear Samba team, Today we have used samba ver. 3 as primary domain controller at my company. To improve the Samba technology and feature to support our business , we want to upgrade to Samba 4. Is there any tools or support to provide upgrade solution from Samba 3 to samba 4 ? For the information current Samba version we are used and running on Mandriva : samba-common-3.0.23b-7mdv2007.0

I portupgraded my working 3.0.23b PDC on FreeBSD 5.5 to 3.0.23c and found that all workstations could not login. The log file reads: get_md4pw: Workstation PC01$: no account in domain I ran pdbedit -L, and it returned nothing. I use tdbsam backend; all user accounts show up fine with 3.0.23b. Now they are missing. I deinstalled 3.0.23c and switched back to 3.0.23b. Everything is then back

Hello all, I'm running samba3 as domain controller. I have upgraded samba from 3.0.22 to 3.0.23b and faced an issue with groups display: samba does not see any groups. "net rpc group -U Administrator" returns empty set. usrmgr.exe does not show any groups also. Groups are present in ldap, nss_ldap works fine: # id asv uid=2005(asv) gid=513(Domain Users) groups=513(Domain Users),

Yesterday evening I upgraded my FreeBSD 5.5-RELEASE Server from Samba 3.0.22 to 3.0.23. This gave me a LOT of work today... :-( This is what I found so far: My Samba-Server is member of a large ADS-Domain. After the upgrade, file based Usermapping didn't work anymore... better: it worked TWICE. (I once opened a PR for that a few years ago :-). So, with LogLevel 3:

Hi, Cannot spot the debian binaries for 3.0.23b - please please please as 3.0.23a has some issues regarding domain users and I'm too lazy to compile my own packages Thanks, -- DanB

hello when I try to install samba 3.0.23b I get this error error: Failed dependencies: perl(Unicode::MapUTF8) is needed by samba-3.0.23b-1 is this perl module required since 3.0.23b? and why? can you use 3.0.23b without it? werner Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

I'm compiling samba-3.0.23b as I write this. However, after studying the documentation, I have some serious concerns about installing it. The WHATSNEW file says that the method of mapping unix-native uids and gids to SIDs has changed since 3.0.22. As I read this, this would imply that upgrading Samba will cause much breakage because domain users will no longer be able to access files they

I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)

Hi All, Just upgraded a test box to 3.0.23b and discovered some changes that cause a panic. I had an smb.conf with passdb backend = tbdsam guest The guest bit now causes panic action. log.smbd complains ... "No builtin nor plugin backend for tdbsam guest found" Either the build options have changed or the guest operative has issues. Works OK without guest, but it's been

I installed a PDC some days ago for some 15 users/PCs (w98,2000,xp), with samba 3.0.23b-1 and valid users wasn't working. I'm going to update to 3.0.23c which solves that problem. I'm using smbpasswd passdb backend. In /etc/group I have only two groups. I don't understand very well the changes related to primaryGroupSID and RID commented in previous posts. Please, is it

Mates, Since nobody is building binaries for mandriva, I thought I would share a quick cheat sheet for those who want to compile from source to update 10.2 from 3.20 to 3.23. Here goes: 1. Download samba-3.0.23b.tar.gz to your local machine (a given...) 2. Unzip it: tar xzvf samba-3.0.23b.tar.gz 3. Change to the source directory: cd samba-3.0.23b/source/ 4. Make sure you are

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Where does he get those wonders toys?" -- The Joker (Batman 1989) ============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've uploaded the *final* 3.0.23c roll up patch to http://samba.org/~jerry/patches/patch-3.0.23b-3.0.23c-gwc-2.diffs.gz. I've already cut the 3.0.23c tarballs so unless there is a major problem, this will be the final change set. Please report *any* bugs that you find. I'd like to wrap this one up and do the public 3.0.23c

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've upload the preliminary patch against 3.0.23b that will become 3.0.23c so people can do full testing against what we hope to be the release code. Note that the reported version in the patch is 3.0.23c-gwc-1 to prevent confusion from the final 3.0.23c release. You can download the gzipped patch file from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Where does he get those wonders toys?" -- The Joker (Batman 1989) ============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is

So, I'm building 3.0.23b for Slackware (since they don't have it out yet[1]), and I've noticed these two lines in the script that Slackware uses to build Samba 3.0.23 from source (which I'm modifying to build 3.0.23b): # -j options don't seem to work... make Anyone know why that comment might be there? Is it true that Samba can't be built with "-j2" or