similar to: XP SP2 offline files sync delay (again)

I'm scratching my head at the following issue that surfaced with Windows XP Prof. + SP2. First, a summary of my configuration: . Running Samba 3.0.7 in a LDAP-based PDC configuration, and with separate machine as member server for home directories. . The OS for PDC is Mandrake 9.2, the file server (FILES) is Mandrake 10.0. . 1000BaseT Ethernet. With XP SP1 and Samba 3.0.7 or prior,

I posted a while back (twice, actually), about some long delays with offline files sync and, to a lesser extent, domain logins with Windows XP SP2. This is Samba 3.0.7 (ldapsam backend) on Mandrakelinux 9.2 and 10.0, with XP SP1 clients. I make use of WINS and everything works fine for SP1 clients. Here's what I found since then: after the client is joined to the Samba (NT) domain,

My clients are Windows XP SP1 and SP2, members of a Samba-PDC NT domain (tested 3.0.7 and 3.0.10, same result). Attached is ethereal output of a two packet client-server exchange that takes place when an offline files sync is done. SP1 quickly does this exchange twice - first broadcast, then unicast (as attached) and goes on its way. SP2 tries, pauses many seconds, tries again, finally

Gentlemen, I have noticed (!) an unbelievable drop in performance with Windows xp pro sp2 systems, compared to sp1. The performance I have noticed is 122 seconds to write 65,000 indexed records to a dBase type file under sp2 and the same job in sp1 is 7 seconds!! I can't believe that this is a 'normal' feature of Windows sp2 software when working with Samba. Is it possible that

I have a file testing program that creates, writes and indexes a file on the server from the Windows client. On xpp sp1 the program takes 7 sec to write file and 8 sec to read the indexed file. After telling the Firewall to go away I can get the following numbers from xpp sp2; 29..30..45 (tested multiple times) sec to write the file and 7..8 sec to read the file. Any ideas on why the

> I have few Windows2000 Pro samba domain members which logon to the domain > without any obstacles. Recently I decided to upgrade all client workstations > to WindowsXP SP2. Fresh copy of WindowsXP joined domain properly but when I > tried to logon as usual it accepted password and shut down after a while > (logs of samba confirm that workstation logged on). Windows claims that

I've having trouble getting XP SP2's to join a domain. Whenever I try to join, at the point I'm asked for a user name and password with permission to join the domain, I enter root and root's password, then get the dreaded "Unknown user or bad password" error message. The clients are a mixed bunch with some 98's, 1 Win2K, a few XP SP1 (I know, I know!, but

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear developers, I tried to use tinc on my Windows XP Box wich has Service Pack 2 RC1 installed. I'm using the Tap-Win32 driver from openvpn 2.0 beta2 since they were the only working drivers. Now here is the errormessage i recieve when I try to start tinc: C:\Programme\tinc>tincd -D -n hive tincd 1.0.2 (Nov 8 2003 14:19:06) starting, debug

Hi all! I'm a system administrator for a company that uses Samba (the latest, 3.0.14a) as a PDC for a subnet with various windows clients. The following diagram illustrates the situation of the various host in my network: +----------+ | Win 2003 | +--+-------+ - Clients - | 10.100.0.0/16 | +--------+ |

I have samba 3.0.4 acting as a local master browser and couple of win xp sp1, sp2, win 9x client machines. Everything works fine excepts win xp sp2. It just disappears from network neighborehood in about 15-20 minutes after start. stop/starting "Server" system service on this machine solves problem for next 15-20 mins. %) What can be done about it? Is there any sence to upgrade samba to

How can I effectively and completely hide private interfaces on my Linux Samba servers? (PDC and file server) Even when I use the "interfaces" option and even "bind interfaces only", "net lookup dc" still returns IP addresses from the private interfaces, and for that matter another machine that is not even running Samba (once was, no longer). Seems like the

Hello, I was wondering if anyone else has experienced this. >From an XP machine printing to a SAMBA printer, printing is painfully slow. Selecting the printer, and even sending the job through windows makes the app appear non-responsive. The print job is completed fine, but just takes a long time to print. XP boxes with SP1 print like a dream. I've managed to replicate this on 4 boxes

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but only clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K errro message. But if the same user loggs on on a client machine with W2K SP1 all things are ok.

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K error message. But if the same user loggs on on a client machine with W2K SP1 all things are ok. In

Hallo, > We have problems with printing after installing XP SP2. > In nearly every software it takes about 10 seconds to 30 seconds, if you > click on "Print-Button" and wait for the print dialogue window. > Extremly slow are programs like MS Word (30 seconds, when you open a > document the first time). same problem here. This a known but _unresolved_ problem for Samba

we are using samba 2.2.3a-6 for debian (woody) and found that our w2k machines do not apply the ntconfig.pol when sp2 is installed. (the sp1 machines do) Is there a way around this? -- Torsten

Hi all, I'm using Samba 3.0.6 (on IRIX 6.5). This is just a 'let you know what I've discovered' message really. I've just installed upgrade a laptop here to SP2 of Windows XP. It then started failing to make network connections. After much fiddling about, I tracked it down to DFS shares. This PC can now connect to the DFS root OKay, but doesn't recognise the entries

I use Samba 2.2.12 like print server and all were fine until some XP clients start upgrade to SP2. The "feature box" (see attached feature2.jpg) is absent on SP2 clients (see attached feature1.jpg) but still present for 2K, XP, XP-SP1 clients. Other things look well with SP2 but I guess that absence of this "feature box" probably hide some other problems. How can I fix it?

Hi, i have a lot of win XP clients with SP2 preinstalled and when i try to join to samba PDC i get an error: [...] user unknown or incorrect password. [...] The other clients (win 2000-SP4, NT-SP6, XP-SP1) work correctly, the problem is with XP-SP2. My version of samba is samba-2.2.8a. Exists any solution without having to update to last samba? thanks Joan Ramos Ramos

On Wednesday 26 June 2002 08:55, you wrote: > Hi, > > I'm using win2k + sp2 and the policies are still being applied. The > Ntconfig.POL file is in the netlogon directory with root.root -rwxr-xr-x > (755). > > I hope this helps What exact version of samba are you running? Did you join the domain *before* or *after* you installed sp2? Could you send me the netlogon