similar to: Samba 3.0 PDC installing Exchange 5.5 SP4

I created a brand new nt 4.0 server with exchange 5.5 server in my samba 3.0 pdc domain with no problems. The exchange server runs fine under the samba 3.0 pdc, but when I try to install exchange 5.5 sp4 on the exchange server the service pack gives me an Dr. Watson error. The exchange service pack makes it through the copying of the service pack files and then modifies the registry settings for

Hi Jerry - I'm just e-mailing you regarding the Exchange SP4 upgrade error when using a Samba 3.0 PDC. We presently have a Samba 3.0 PDC and using Exchange 5.5 SP4 without a problem, however we are in the process of migrating to Win2K3 and Exchange 2K3 and are setting up a test network to simulate the migration. While installing SP4 on exchange I keep getting a Dr. Watson error exactly the

Hi all. Scenario: Fedora Core 2 Samba 3.0.6 PDC with ldap Exchange 5.5 on Win2K SP4 Whenever a try to install Exchange SP4 I run in to a situation similar to the one reported in bugzilla's bug 1076 (https://bugzilla.samba.org/show_bug.cgi?id=1076 ) and to this http://lists.samba.org/archive/samba/2003-November/001828.html Also found this on another list: ----- Begin quote ------------

Hi again. After installing ethereal on the samba server itself, I've found this: WIN2K -> SAMBA LsarLookupSids2 request SAMBA -> WIN2K Fault: call_id: 4 ctx_id: 0 status: nca_op_rng_error WIN2K -> SAMBA LsarLookupSids request SAMBA -> WIN2K LsarLookupSids response, STATUS_NONE_MAPPED Once again i'm completely lost. Anyone? Best regards. Bruno Guerreiro -----Original

Hi. Applied it to 3.0.8, which still has the issue... Worked like a charm... Thanks a lot. Will it be merged with future samba releases? Best regards. Bruno Guerreiro -----Original Message----- From: Guenther Deschner [mailto:gd@sernet.de] Sent: Tuesday, November 16, 2004 1:08 AM To: Bruno Guerreiro Cc: 'Gerald (Jerry) Carter'; 'samba@lists.samba.org' Subject: Re: [Samba] Samba +

We want to migrate our Novell 4.11 server to a Redhat Enterprise Server 3.0 with Samba 3 and Openldap. Our configuration is the following : - 1 Windows NT 4.0 server with Exchange 5.5 SP4 as PDC - 1 Windows NT 4.0 server as BDC - 1 Novell 4.11 server as file/print server We want to change the Novell server by a linux server (RH EL 3) and put it as the PDC with Openldap. The 2 Windows NT 4.0

I'm afraid I am stumped, and need some help or pointers. Ever since I've "upgraded" my Win2k boxes to SP4, I've been unable to print to Samba-shared printers (on Solaris and Freebsd). Originally I was running the current 2.2.x, and figured trying to diagnose the problem would provide an impetus for trying 3.0, which I have from beta3 through RC1. That bit of history is

I tried to add my backup samba4 as DC or DC to a Windows 2000 SP4 to synchronize the "user database" and "kill" the Windows to let the SAMBA Instead it without touching the profiles of network clients. First of all to mention what I said Andrew Bartlett: We are working to enable support for Windows 2000 DCs as a target for a 'samba-tool join' (which will then do what

I've been experiencing an incredibly slow samba access from a Win2k SP4 client to a Linux samba server (Mandrake 9.0, samba 2.2.8a). It seems like the file transfer rate is not so slow, but the initial opening of files on the Linux samba server takes very long (10 ~ 20 seconds). The directory listing is also very slow. In the past, it took me about 2.5 hours to compile Mozilla-Windows

Hello, I am unable to do a graceful shutdown or reboot of SLES 10 SP4 virtual machines (Kernel version: 2.6.16.60-0.85.1-default) with virsh shutdown or virsh reboot commands. (e.g virsh shutdown "vmname" ). On issuing these commands there is no impact on the VM. Also unable to perform the shutdown or reboot operations from the menu options available on the console when accessing the

We are trying to install a 32-bit SLES9-SP4 paravirtual machine on a 64-bit SLES10-SP1 Dom0 host from scratch. We have two problems: 1. The YaST2 VM creation tool fails to create a vm if a network card is selected. 2. The initial vm boots from the SLES9-SP4 iso file, but then complains it can''t find the installation source. Here is the /etc/xen/vm/file (after manually editing for a

Hi! I've one big problem. In my work we have a mixed network: one Debian Sarge with samba 3.0.14 acting as PDC and some w2k sp4 and windows xp sp2 pro/home with all updates (including w2k sp4 update rollup) . Samba uses OpenLDAP as backend using smbldap-tools 0.9.1 to manage users and computers. This setup has worked perfectly since december (the LDAP is used by other services as Apache,

Hello folks - back on April 2nd I asked why my NT 4.0 with SP4 computer wouldn't connect to my old copy of Samba (1.9.16p9), while my neighbour's NT 4.0 with SP3 computer did just fine. This was in the case of a read-write share that only myself and my neighbour had access to under our user names. A read-only share worked just fine on both our computers. Thanks to Herb Lewis & Jan

Hi, I've upgraded an NT 4.0 Client from SP4 to SP5. Now I'm unable to mount a shared medium from the samba server, because the user authentication failed. After downgrading all things are well. Is this a problem of NT password encryption? I read NT 4.0 SP4 uses encrypted passwords already?! The samba server is running SuSE 6.1 with Samba 2.0.3. Thanks, Lars --

Hello all, Yesterday I've setup samba 3.0.2pre1 as PDC on linux Debian Wooody with 2.4.24 kernel on my home network. I have also 2 additional machnies running win2k with sp4 included. Samba conf file is as attached below: [global] ???netbios?name?=?zasoby ???workgroup?=?mojezasoby ???server?string?=?Serwer?Zasobow ???passdb?backend?=?smbpasswd ???os?level?=?65 ???preferred?master?=?yes

Hello list. I've been running an old version of Samba (1.9.16p9) to give read-only access to my Digital UNIX 4.0B workstation hard drives (the share is called "rootdir"). It's worked great for over 2 years for that purpose. I finally want to give read-write access to 2 users (myself and my assistant). Her computer has NT 4.0 with Service Pack 3. Mine has NT 4.0 with Service

Hello, now I still have a problem with my Samba installation. Userprofiles don't work under W2K SP4. They work fine with Windows NT 4. When loggin on for the first time the user profile directory is created. After loggin off however no data is written to the profile directory on the Samba PDC. My smb.conf looks like this: =====> # Samba config file created using SWAT # from 192.168.0.1

Hello, at this time we're using s. 2.2.8a (running on SuSE-Linux StandardServer 8 - Kernel 2.4.21) as fileserver for our terminal server environment. We ran into the 128 connections per client limitation and had to modify the MAX_CONNECTIONS-parameter in smbd/conn.c. Now we're planning the migration from s. 2.2.8a to s. 3.0.1. Is the modification in smbd/conn.c still necessary, when using

Samba Masters: I installed SP4 on a NT 4.0 workstation and now it cannot connect to any samba shares. I reran the NT4_PlainPassword.reg script but that did not fix the problem. Your suggestions / flames would be appreciated. Thank You **************************************************************** Leo Crombach System / Network Administrator Tropel Corporation Phone: (716) 388-3566 60

Is anybody running SAMBA with NT4 SP4 clients ? -- +-------------------------------------------------+ | Milan Bednar mxb@inel.gov 208-526-8640 | | MAILSTOP EROB M/S 3640 | | | | "FACT times IMPORTANCE equals NEWS!" | +-------------------------------------------------+