similar to: Using NT to browse Samba shares

When the world was young, Anand Rao carved some runes like this: > SECURITY = SERVER > > PASSWORD SERVER = < MY PDC SERVER > < OTHER SERVER > < ANOTHER > SERVER > > > WINS SERVER = 10.10.10.10 > > NAME RESOLVE ORDER = HOSTS WINS > > SHARE MODES = YES > But with these paramter set.. as mentioned above... I can see the share >

I am trying to use Samba 2.0.3 with encrypted passwords. I have everything set up according to the instructions in encryption.txt, and can authenticate into NT 4 Server shares with smbclient. I can also attach to my smb server using either smbclient or Win95. But NT4sp3 won't browse or connect. That I can connect to external NT shares would seem to indicate that samba is correctly sending

Here's an interesting thing I notice between NTSP3 and Linux 2.0.33+ w/samba 1.9.18p8 [TCP_NODELAY, read prediction on, SND and RCV buffers to 64k, though I've tried 16k, 32K, 64k, max size 2k, 4k, 8k, 16k, no difference] When I copy a file from any share to my NT's HD, I get perhaps 280KB/sec. When I copy from NT HD to Samba share, I get almost 1MB/sec. Doesn't matter where

Hi, I had trouble getting the pwdump program to work correctly on a german version of NT4SP3. I believe the problem is based on the fact that the german group 'Administrators' is called 'Administratoren', and Administrators is hard-coded into the utility. Would it be possible to make that an optional parameter? Unfortunately, I have no access to a C-Compiler on an NT-station, so

JdL> I've always been afraid to ask, but here goes... JdL> What's the advantage of GUEST_SESSSETUP being a compile time parameter, JdL> instead of having it as an smb.conf parameter? I'd like to second this question! Also, just in case that it will not become an smb.conf parameter: can't it be added as a comment to the Makefile (probably near the comments to

Hi James, we use some NFS mounted shares on our Linux-SCO-network. Samba runs on the linux box. The linux server mounts some NFS shares from the SCO server. The access error should not be a samba failure. Make sure that the directory above the mountpoint is accessable for user nobody (chmod o+x , if you upgrade to samba > 1.9.18p7 make sure that there is read permission on the directories too:

Stupid me, I forgot to add the Info about the Samba Versions in use: 1.8.18P3 (CDC Epix), 2.0.3 (IBM AIX) and 2.0.5a (on my Printserver, running on SuSE 6.2 This machine sadly caused the trouble in one case today) Hope this helps better. Juergen Hello, our sysop's asked me to forward this: Hi everybody, maybe someone can give me a solution to the following problem (get rid of NT

Hi quite strange assumtion, but I have the feeling, that samba makes my NT-CLient crash (blue screen). I haven't found anything in the archives about such troubles. It dosn't matter whether sp3 is installed on the NT machine, nor does a specific samba version makes this behavior vanish, it's just that my samba server wasn't available for a 3 months period in which the NT

Iztok Polanic <iztok@hakl-hakl.si> carved some runes like this: > > 1. I have just installed samba on my computer. It works great and > > I can mount all Windows computers, except NT. When I try > > "smbmount //192.168.1.4/C /mnt/test" I get this error: > > > > Password: > > smb_get_length: Invalid NBT packet > >

On 3 Apr 99, "Laura S. Tinnel" <ltinnel@cs.utk.edu> had questions about NT access problems: [snip] > NT is the only remaining problem. It cannot access anything on Linux > through Network Neighborhood. First off, as soon as I double click on the > Linux machine's icon, it immediately prompts me for a userid/password even > though it is sync'd up with the Linux

Hello, our sysop's asked me to forward this: Hi everybody, maybe someone can give me a solution to the following problem (get rid of NT unfortunately is no solution). Our net environment contains NT4SP5 and SAMBA servers. Workstations run NT4SP3 and SP5. Part of our password policy is to change passwords every thirty days, and lock the user account after ten unvalid logon attempts. Lately,

Here is a re-post of PR#19365 which was originally post back in Aug.. If anyone can help I am still looking for a solution ! Forwarded message: > > Hi Jeremy ! > > Don't know if you remember this one but it is definetely turning > my hair grey :) I have left your original reply at the end. > > I finally have a configuration which works with Bentley's >

I am trying to get Samba 2.0.3 up on MacOSXServer (which is BSD 4.4). I can't get NT to recognize samba shares. Samba is running as security=server, pointed to an NT PDC for security (using the netbios name; should this be by ip address?); passwords are encrypted. I can use smbclient to attach to my own samba shares. I can also attach to other NT shares as a client and view network lists. I

Howdy all: I thought I had this problem beaten into submission, but I guess not. We just got our first NT box, which is another new wrinkle... Anyway, the LAN just went belly-up again yesterday, and when the LAN guy disconnected my linux/samba box from the network, Network Neighborhood came right back. I still don't think it's a linux/samba problem, but I'm certainly no

-----Original Message----- From: SI-Gaetan Boudreau <boudreg@IRCM.UMontreal.CA> To: Andrej Borsenkow <borsenkow.msk@sni.de>; samba@samba.anu.edu.au <samba@samba.anu.edu.au> >> It has nothing to do with initial null passwords > >Thank you for taking time in trying to help me. > >The reason I suspect it does it's that it works for the other users, the >ones

I'm getting the following in my logs when people try to connect to our Samba server. Any idea why this happens? The smb passwd file is there, and the user *does* exist. When I try to connect to the server, Win95 gets a message saying "You must supply a passowrd to make this conection. \\salamanda\IPC$". Security = server, the WinNT boxes have SP3 loaded, and this is Samba

Hi, all! In the end I want to make Squid authorize users via NT4 domain. I have Samba 3.0.10 (further named PROXY) and NT4SP3 PDC (named CONTROL). # net rpc join -U admin Password: (I enter) Joined domain: REGENT.CENTER. It seems to be OK, but the following record appears in PDC's system log: Event ID: 5723 Source: NETLOGON Type: Error Description: The session setup from the computer

Hi, I'm trying to setup a Linux box with Samba (1.9.18p10) and it isn't having any luck making a home for itself on the network. If I go to a Windows95 machine, I see all (well most) machines on the net there, but not the Linux box. I can also not see any other machines from the Linux box. Here is log.nmbd output that repeats every 5 seconds or so: find_workgroup_on_subnet: workgroup

> This problem was occurring on 19p8 so I moved to samba 2.0.0 yesterday in > hopes it was a bug > that had been solved... All the information I am supplying relates to > version 2.0.0. The only change > I made to my global.conf file between the two versions was to remove the > socket option IPTOS_THROUGHPUT. > > We have a large number of zip files named

We're using Samba 1.9.18p10 on a Linux 2.0.35 box as a fileserver chiefly for software development under VC++. Builds are done from the command line, not the IDE. I'm seeing rather slow build performance under NT4SP3. Build performance is fine under Win95. Build performance is also good when building from Samba 1.9.18p8 running on a Sun UltraSparc. To give some concrete figures, building