similar to: Errors when NT4sp3 is the client; 95 works

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

I am running Samba 3.4.8 as a PDC on Solaris 10. I recently made this the WINS master- previously the BDC (Samba 3.0.37 on another Solaris 10 server.) I also use Sonicwall ipsec VPN for remote access (Windows XP clients.) The sonicwall client creates a virtual NIC on the client so that the client can have an IP address directly on the company LAN (ie. the same LAN as the samba

Hello all, we use Samba to serve about 20 DOS/WfW/Win95 machines in 'security=share' mode. We use unix accounts as password validation, so I _know_ our Samba does not accept encrypted passwords. On Thursday, we added a NT4/SP3 box. I expected it not to logon before we made the plain-text password registry patch, but it did! It's a new NT installation (on a new AMD K6 box), so I

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

I have a prerelease version of Samba 2.0.4 running successfully on MacOSX Server with encrypted passwords and domain security. (Thanks to help from Bill Chin and others on the list, and Jeremy Allison and rest of the samba team) I have just started work on testing Samba as a NT domain member, and want to know if I have the right ideas from my reading of the docs: With security = domain, the Samba

Adam Nielsen schrieb: >> It is configured as an NT domain controller and has been working >> well. I needed to add a routed (over VPN) connection to the system >> but cannot get the routed clients to access the browse list. The >> clients are all Windows XP professional. The remote client is not a >> domain member. All clients work when directly connected to the Samba

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 using Samba version 3.0.10-1.fc2. It is configured as an NT domain controller and has been working well. I needed to add a routed (over VPN) connection to the system but cannot get the routed clients to access the browse list. The clients are all Windows XP professional. The remote client is not a domain member. All clients work when directly connected to the Samba server (broadcast),

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

Hi all, I've had cross-subnet browsing working in Samba in the past, though I tend to struggle with it each time I set it up. For whatever reason, I can't seem to get things working this time. Summary: Only my desktop, not the file server, shows up in the desktop's Network Neighborhood. (I have left the machines running for several hours, in case there's a time-to-sync issue

I had some discussion about this problem at the end of January and have investigated further. The problem: Clients directly connected to the subnets of the Samba server get a browse list (network neigborhood), while clients that access the serveer over a router do not. there are no broadcasts, Samba is functioning as a WINS server and is working for all clients (nblookup proves this). I

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 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:

OK...Back ground... Wins server is nt4 client is redhat 7.3 latest and greatest samba 2.2 ok I work in a large network.1000 plus pcs in multiple subnets... I got rid of windows on my desktop and I am trying to get samba working with all those win9X,2000,NT boxes.... I see myself on the browse list but can not do a net view on any winx box to my linux box. I can nblookup windows pcs from my

>> The problem is performance. While Samba is not terribly slow it's still >> too slow. Copying large files takes about half a minute/meg on an > >i find that samba running on FreeBSD is also pathetically slow: 10 to 20 >k per second. adding "socket options = TCP_NODELAY" speeds this up by a >factor of ten to twenty, on a 10mb/s LAN with NE2000 cards. it

Okay, I've run through all of the tests in the DIAGNOSE, which my 1.9.18p1 SAMBA server (and NT4SP3/W95 clients) pass with flying colours. server box: Linux 2.0.33, gcc 2.7.2.2, libc 5.4.33, shadow, quota on (usr+grp), and my smb.conf is summarised (by testparm output) below: Problem is this: with respect to programs not long filename-aware/compliant, users cannot "double-click" on

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

I compiled samba 2.0.2 on a intel RedHat 5.2 machine successfully. I then set up the machine according to the DOMAIN_MEMBER.html instructions to join my domain. Everything seemed ok so far, i got the message: change_trust_account_password: Changed password for domain INFO. smbpasswd: Joined domain INFO So far OK, right. I set up the smb.conf like this. The options in Global that are commented

Hi, sorry to borrow everybody, but i ve got a big pb! I developp scripts with perl, i use samba and netatalk in order to access my script and try to make "portable" scripts... i ve got a nt4sp3 and before installing sp3 i could connect to my unix via samba. Since the sp3, he says error 67! i ve try the solution in the nt registry (found in the samba digest) but no success.... as we