similar to: additional authentication box in Windows 2000 RC2

Dear sir: There was one problem which bothered me for a long time. I used the Red Hat 5.2 with kernel 2.0.36 (gcc 2.7.2.3) and samba-2.0.3, samba-2.0.5a for a period of time. The Linux was treated as the Samba server. All of the file/printer sharing from the Linux samba server to the MS-Windows 95/98/NT clients are OK. It only got problems in the Windows 2000 (since Beta3, now RC2) as the

Dear all: ---------- The original message: ---------- > --> But, I found one problem in this version. All of the file sharing > actions are OK. But if the windows 2000 client start to use the samba shared > printer, it will appear one popup box "You must enter the password to use this > printer "http://172.16.3.12" username:____, password:____". But the

Dear all: I used the samba-2.0.6 under Red Hat 5.2 for a period of time. (I used samba server, not client.) It works fine. Recently, I found one strange problem when I use "Find Computer" from MS-Windows 98. I hope someone could help me to solve this problem. ----> Samba Server got a user (user1) with a password (pass1) (Both /etc/passwd and /etc/smbpasswd used this username and

Just curious, has anyone gotten Samba to work with Windows 2000? I've mucked with it a bit. But can't seem to make it go. I haven't tried applying the NT 4.0 Registry patches yet I will probably take a look at them and see if I can get them working with Win2000. Thanks! -- Steve "We confuse you, or your money back!"

Here is a cleanroom specification of RTMPE which has been documented from rtmpdump v1.6 source code. updates will be at: http://lkcl.net/rtmp/RTMPE.txt it is from the perspective of a client however implementing from the perspective of a server is a trivial matter. please distribute freely and widely. please implement and distribute even wider, in both client and server. note: absolutely no

Howdy, I'm trying to see my Samba shares from my Linux box on my WinNT machine. I can see the Linux box in the Network Neighborhod, but clicking on it just gets the old "remote computer not available". I've got RedHat 6.0 on the Linux box. I can ping the Linux box, I can FTP/Telnet to it, and it's my email server and I have no probl Content-Type: multipart/alternative;

Hi David, Thank you for your reply. In fact, my question originally came from the google native client. I thought that the bitcode can be shared among the different targets as it inherently is. Therefore, I used the clang to generate the bitcode to prove that my thought is right, and I supposed that the different bitcode caused from the different versions of libraries before. Thanks for the

Dear all: I've found one strange things. I am using Red Hat Linux 5.2 and Samba 2.0.6. (I rebuild the RPM in RH 5.2) The samba is treated as a Server. Every windows 95/98/NT could access the samba server without problem. In windows 2000 RC2 (treated as client), it could access the samba server. But if I enable the "IP Security Policies on Local Machine". (You can enable

Hi Óscar, Thank you for your reply. It looks like the limitations are the platform's API and ABI (included the size of variable). So, if there are two platforms that have the same API, ABI but different ISAs, the bitcode can be shared. Can I say that? Thanks, Kenia Kuo 2012/9/25 Óscar Fuentes <ofv at wanadoo.es> > Kenia Kuo <kenkillerkuo at gmail.com> writes: > >

All, With the belief that, "given enough eyes all bugs are shallow", I submit the following to the list. I had sent a shorter version to samba-bugs last week, but, given the nature of this problem, I think everyone needs to check this on their own systems. Overview: Pulling files from an NT 4.0 machine to a RedHat 5.0 linux box using 2.0.3 or 2.0.4b smbclient *consistently* results in

Hello, I'm new to this list. The NT folk here, are concerned about some timeout errors and stuff that appear in their event viewer. They are building a case to convince management that unless these "samba" errors are fixed, we should move to NT file shares. I think this is a bad idea. Can anyone help me out here. We are running samba 2.0.6 (1st msg) and 2.0.5a (2nd err msg)

I have not used astcc with pin codes so far, since I set-up the phone number as card number. Some of my users want now to dial in to the system and than use their card, which is their phone number. For that I would need a way of authentication, like a pin. I want to use something like: What is your card number: <user keys in the number> Enter your pin: <user enter a long pin>

jimd@gie.com wrote: > > Overview: > Pulling files from an NT 4.0 machine to a RedHat 5.0 linux box using > 2.0.3 or 2.0.4b smbclient *consistently* results in randomly corrupt > files, with no error message to indicate internal file corruption. We > are able to recreate this problem on all manners of servers and > workstations running NT 4.0, and all manner of linux boxen

Replying my own post: > Date sent: Tue, 26 Oct 1999 15:03:21 +0200 > Samba 2.0.5b on Linux 2.0.36. Sorry, it was 2.0.5a, now 2.0.6. > Inoculan virus scanner up-to-date on WinNT4SP3HU and WinNT4SP5HU. > There are zillions of problems (eg. oplock breaks (oplock is now disabled); the client and server > having different ideas of what files are open; multiple connections

Kenia Kuo <kenkillerkuo at gmail.com> writes: [snip] > Currently, I tried the toolchains of ARM and PowerPC that have the > different versions of libraries, obviously the generated bitcode are > different. > So I wonder whether the version of library is the only reason why the > generated bitcode are different.

Hi, I'm using clang to build my project as follows: $ clang++ -ccc-host-triple arm-none-linux-gnueabi --sysroot=/usr/local/arm-none-linux-gnueabi/arm-none-linux-gnueabi/libc/ -o foo.o -emit-llvm -c foo.cpp $ clang++ -ccc-host-triple arm-none-linux-gnueabi --sysroot=/usr/local/arm-none-linux-gnueabi/arm-none-linux-gnueabi/libc/ -o main.o -emit-llvm -c main.cpp $ llvm-link foo.o main.o -o

Has anyone else noticed this? With Samba 2.0.6, Samba seems to ignore my logon path= statement, and always put profiles in the home directory. I can toggle this symptom by switching back and forth between 2.0.5a and 2.0.6. With login path=\\%N\profile\%U, 2.0.5a puts them below the directory I define in [profile]. 2.0.6 puts them below my home directory. In my case I have 2.0.5a and 2.0.6 in

Hi Everyone, Just wondering if anyone has seen anything similar to this: Jul 28 21:57:30 GATEWAY smbd[6681]: open_directory: unable to stat name = proc /self/cwd/proc/self/cwd/proc/self/cwd/proc/self/cwd/proc/self/cwd/proc/self/ cwd/ proc/self/cwd/proc/self/cwd/proc/self/cwd/proc/self/cwd/proc/self/cwd/proc/s elf/ cwd/proc/self/cwd/proc/self/cwd/proc/self/cwd/proc/ Jul 28 21:57:30 GATEWAY

I am looking for the answer for the same subject. Currently I have Linux 2.0.36 running on my linux box. I would like to install Samba server on the box. I am expecting the Windows XP client will access to the box for file transfer. If someone have the answer for the question whether the Samba 2.0.5a support window XP client? It would be greatly appreciated for any idea or clue to help with

Dear Samba Experts, after browsing the mailing list archives for some time I still do not have a solution for the following problem: I recently set up the Samba Server Version 2.0.5a on a SuSE-Linux 6.0 PC (Kernel 2.0.36). Whenever I try to reach the shares on this machine from Windows 95 or Windows NT machines (with different user-names) in our Network, by double-clicking on the servername in