similar to: Running Samba 2.2.3a under RedHat 7.2

I'm trying to network-boot a GCT Allwell set-top box without success. My frustration level is high. The problem seems to be that the Allwell is sending a RRQ with an option. tftp-hpa responds with an OACK, and waits for the corresponding ACK from the Allwell. The Allwell never sends that ACK, but instead continues with the same RRQ until timeout. Having read RFC1782, this makes me think

Hi, Kjohn Sasitorn <kjohn at cs.utexas.edu> schrieb am 06.02.02: > i am attempting to perform remote installs for various computers in my lab. i > would like to know what are the features / limitations between syslinux 1.63 and > rh pxe 0.1. do you have any light to shed on this matter? thanks in advance, I can't say much about the RH pxe thing, AFAIK this is really old. In

I used linux.0 from the pxe package of redhat linux 7.2. It's successfully boot vmlinuz-2.2.19, but when I try to boot vmlinuz-2.4.14, it reboots after Setup() call in linux.c The phrase "Uncompressing linux" does not appear. What I ought to do to successfully boot linux-2.4.14 kernel image? Best regards, Dmitry. -------------- next part -------------- An HTML attachment was

Hi, "Mircea Popescu" <nufarul.alb at go.ro> schrieb am 29.01.02: > I have this problem: > I've partitioned my hard drive with PQMagic 7 in the following way: > hda1 - fat32 > hda2 - ext2 > hda3 - fat16 > hda4 - extended > hda5 - Linux Swap > hda6 - fat32 > hda7 - ext2 > hda8 - fat32 > > I've put syslinux on

I have successfully implemented Samba in the past but I am now perplexed by a new installation which fails smbstatus with the message: "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR:

Hi, we have installed the newest release of samba from HP for HPUX. It's based on samba 2.2.3a (B8725-1.0.8 HP number) We used the same config file and started the samba stuff and run into the following problems. 1) The machine was only reachable under one netbios alias. 2) Only some pc could connect (~15 out of 150), but those could also only see the toplevel of a share 3) The following

i've been integrating a Samba server into a mixed windows 2000/2003 authentication environment for use as a NAS device. i finally have things working for the most part, but in the process of debugging authentication i noticed an error when performing the following command: hmason@mpinas1:~$ smbclient -L localhost the error shows up when loglevel = 5 in smb.conf: Netbios name list:-

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)): tdb_open_ex: could not

I am trying to enable unix password sync. PDC is solaris 3.026a on Solaris 9. my smb.conf file includes: [global] workgroup = MYDOMAIN server string = myserver passdb backend = tdbsam passwd program = /usr/bin/passwd %u passwd chat=*New\sPassword:\s%n\nRe-enter\snew\sPassword:\s%n\npasswd:\s password\ssuccessfully\schanged*\n unix password sync

When I start winbindd (Samba v2.2.3a on Linux), I get the entries in log.winbindd shown below. What's the story on all those complaints about file "unexpected.tdb"? There is no general problem with Samba writing to that subdirectory: # ll /var/lock/samba/ total 288 -rw-r--r-- 1 root root 696 Feb 12 22:01 brlock.tdb -rw-r--r-- 1 root root 231 Feb 13

Hi all, I am running RedHat 7.3 and Samba 2.2.3a. I am using DHCP for my Linux box (hostname: NGPLinux, IP 132.189.26.62). I can see the list of shares I defined by using "smbclient -L NGPLinux -N". I can resolve the name using "nmblookup -U 127.0.0.1 NGPLinux". However, when I tried to use "nmblookup -B 132.189.26.255 NGPLinux" on the local machine, I got the

Gurus, I have downloaded and compiled 3.0.2a. I can map from 2000 to my share fine. If I try a smbstatus I get errors, see below. Can someone please point me in the right direction? smbstatus -s /usr/local/etc/meltwk-tst02.conf -d 10 edited to keep it short but this error about not having this charset repeats about 10 times. Locale charset 'ISO8859-15' unsupported, using ASCII

[2799/3801] Compiling source3/locking/locking.c [2800/3801] Compiling source3/locking/brlock.c ../source3/locking/brlock.c: In function 'brl_get_locks_readonly_parser': ../source3/locking/brlock.c:2071: error: expected expression before 'struct' ../source3/locking/brlock.c:2071: warning: assignment makes pointer from integer without a cast ../source3/locking/brlock.c: In function

Experts, We've just migrated from samba 2.2.8a to samba 3.0.20b in a very large corporate environment. Everything was really fine in our lab, but we began experiment serious load problems on the productive servers the morning after the procedure took place. I'll try (briefly) to describe the characteristics of the scenario: Resources: Old Environment: Hardware:

Everytime I install Samba on Debian 2.4.27, And I check smbstatus I get this: tdb((null)): tdb_open_ex: could not open file /var/run/samba/brlock.tdb: No such file or directory Failed to open byte range locking database tdb((null)): tdb_open_ex: could not open file /var/run/samba/locking.tdb: No such file or directory ERROR: Failed to initialise locking database Can't initialise locking

Hi! I've been fighting with Samba for over a week now and I can't seem to work it out. It all started when I installed the standard samba (2.2.1a-4) which came with RH7.2. I ran "smbstatus" and got the following error: Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting. I've tried the

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write

Hi all I try to get Samba running on the recent Debian stable release. All upgrades have been done and Samba was included in the OS Installation. I use the Samba version 2.2.3a-12.3 for Debian. smbd and nmbd are starting automaticly when the System is running. The smb.conf is still the one from the installation, nothing edited yet. Here are the errormessages that i get if i try testparm and

Well I seem to have everything working now, I started up the daemons and the ran smbclient -L localhost and then smbstatus and everything looks good!Strange.. Thanks, -Dusty > -----Original Message----- > From: Dusty Hall [mailto:draper7@ziplip.com] > Sent: Friday, February 15, 2002, 8:01 AM > To: samba@lists.samba.org > Subject: [Samba] Locking Module? > > Hello everyone,

Please, What's this? Please, please, how to resolve ? [root@neosaldina-lj003 samba]# more nmbd.log tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04 00:12:51, 2] tdb/tdbutil.c:tdb_log(725) tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04