similar to: bind failed on port 445 socket_addr = 0.0.0.0.

Hey, I've got a probleme. My AD is a windows 2008 R2 (sh?ma 2003) I have tow windows 2008 R2 rodc in my architecture. I've a squid under suse 11.1 x64 and daemon samba and winbind; The version of samba is : Version 3.4.5-3.1-2289-SUSE-CODE11 I have tow domain windows 2008 r2 in my architecture Domain : medical Domain administrative. Squid/samba/suse is join to the domain Medical.

Hi Folks, I am looking to try and find a solution to the following problem and hope someone can help. I have just installed Samba on an HP Proliant Microserver at home to share disk with my Windows 7 PC and Vista laptop. I have managed to get everything set up but I have an issue where on a reboot the Windows 7 PC looses the share. If I restart samba (using /etc/ini.d/samba restart) then

Hi. Today I upgraded samba from 3.0.34 to 3.4.4 without changing anything in smb.conf but with changing local and domain sid: old samba 1) net getdomainsid and getlocalsid new samba 2) net setdomainsid and setlocalsid to ones (both the same) from 1) after restarting samba I can't log into domain: XP says : domain controller unavailable ... I tried to rejoin domain - and I can ;) however

I have a data frame in wide format. There are six variables that represent two factors in long format 3x2, Valence and Temperature: > head(dpts) File Subj Time Group PainNeg.hot PainNeg.warm SociNeg.hot SociNeg.warm Positiv.hot Positiv.warm Errors 1 WB101_1_1_dp.txt 101 1 MNP 30.700000 13.75000 16.319048 35.166667 30.18333 14.383333 1 2

I can't figure out what is causing the error message of [1999/10/13 11:39:42, 0] lib/util_sock.c:open_socket_in(671) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) in my logs and thus preventing smbd from serving up connections. How can I track down what is causing this? Samba has been working great and now I must have done something but I don't know what. The

My wife and I each have our own workstation dual-booting WinXP and Gentoo Linux. We also have a third which runs Gentoo all the time. I wanted to set up samba on the third box and provide some extra storage space for both our Windows installs. It worked for a few days, then all of a sudden it stopped letting my account (michael) in while still letting my wife's account (amy) use the share.

Not sure what port is using, Need help on the same urgently. Thanks, Manish Jain ______________________________

Need help in resolving above mentione error message, unable to start smbd on Solaris. Thanks,

I can run nmbd successfully, but smbd dies almost immediately when I run it, the smbd.log file has the message "bind failed on port 139 socket_addr = 0.0.0.0.". When I do a netstat -an | grep 139, it shows that tcp is listening on port 139. How do I resolve this conflict between tcp and smbd?

Hi, I just installed a new Centos 6.1 machine with Samba 3.5.6-86.el6_1.4 . I use Webmin to administer the server and configuring Samba (SWAT is also available in Webmin). I have chosen the option to convert the Linux users to Samba users and the command completes and says the users have been converted. However, when I then look at the Samba users the list is empty. Restarted the Samba

# smbd -Fi -d 2 smbd version 3.5.4-62.fc13 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 uid=0 gid=0 euid=0 egid=0 rlimit_max: rlimit_max (1024) below minimum Windows limit (16384) Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED rlimit_max: rlimit_max (1024) below minimum Windows limit (16384) Processing section "[homes]" Processing section

No-one has had this problem before? ----- Forwarded by Raymond Hoogerdijk/home on 20-12-2011 20:36 ----- From: Samba <samba at hoogerdijk.org> To: Samba Maillist <samba at lists.samba.org> Date: 14-12-2011 21:37 Subject: [Samba] Convert Unix users to Samba users Sent by: samba-bounces at lists.samba.org Hi, I just installed a new Centos 6.1 machine with

CentOS 6.2 [mlapier at mushroom ~]$ uname -a Linux mushroom.patch 2.6.32-220.4.1.el6.i686 #1 SMP Mon Jan 23 22:37:12 GMT 2012 i686 i686 i386 GNU/Linux [mlapier at mushroom ~]$ Applicable sections of smb.conf: [global] workgroup = MYGROUP server string = Samba Server Version %v log file = /var/log/samba/log.%m max log size = 50 security = user

In samba 4 log I get the following message: [2013/04/29 00:44:30,? 0] ../source4/smbd/server.c:369(binary_smbd_main) ? samba version 4.1.0pre1-GIT-5727bfa started. ? Copyright Andrew Tridgell and the Samba Team 1992-2013 [2013/04/29 00:44:31,? 0] ../source4/smbd/server.c:475(binary_smbd_main) ? samba: using 'standard' process model [2013/04/29 00:44:32,? 1]

I've compile a Samba 4.0.9 for x86_64 with the following options: CPPFLAGS="-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -march=atom -O2 -pipe -fomit-frame-pointer" \ samba_cv_HAVE_GETTIMEOFDAY_TZ=yes \ samba_cv_HAVE_IFACE_IFCONF=yes \ samba_cv_HAVE_IFACE_IFREQ=yes \ ac_cv_have_setresuid=yes \ ac_cv_have_setresgid=yes \ ac_cv_file__proc_sys_kernel_core_pattern=yes \

Greetings- I'm venturing into a new (for me) area of using R: some presentation graphics based on R data. I'd like to compare two distributions of ordinal variables in relatively small (N=203 and 207) subsets of an R dataset. I can get a reasonably good picture of the distributions' differences with: x11() plot(table(hcd.df$auth.sum[hcd.df$datecat==1]),

?Hi,? On 10 March 2014 18:13, Eric PEYREMORTE <eric.peyremorte at iut-valence.fr>wrote: > Ok i give up. I will stick with the old version version (4.07) which works > well with dell 380 and 790. > > I tried to understand what happened between 4.07 and 5 but i don't have > the skill to understand low level c. > > Seems that the memory management changed a lot, maybe

G'day Guys, I've hit a snag. After using S4 from Alpha, beta, rc, 4.0.1..16 with success, I wanted to upgrade to the 4.1 series. However, after compiling, installing, and provisioning, with no errors, samba4 won't start correctly. I did a few tests by installing from scratch, on the same server each of the following versions (4.0.17, 4.0.18, 4.0.19, and 4.1.9), and got the same

Hi there, We had to setup a pxelinux on a new server (windows 2012) and used the latest release of pxelinux 6.0.2. Everything went ok on my first client test machine : dell optiplex 740. Pxe was really fast (vesamenu with large background image was appearing in less than 3 secondes) But on different client machine i got different results : On optiplex 790 (core i5 with intel 82579 nic) and

Yes on optiplex 790 i upgraded from A07 to A18 (there was a nic upgrade) but it didn't change anything.. On optiplex 380 i upgraded from bios A01 to A07(don't know if upgrade contained pxe or not)... I tried, lpxelinux.0 and it wasn't faster. Only v4.07 helped on these machines. Tomorrow, i will give a try with 6.03pre2. In wireshark, i saw no errors, the packet length was the