similar to: Wierdness using Samba PDC with WinXP-Pro and Win2K-Pro clients

Hi All- Some time ago (24 September 2002), I wrote the list about this problem with using a WinXP Pro client with a Samba PDC (see below for details). In response, Kenneth Illingsworth (if I understood him correctly) suggested that the error message given by the Win XP client just might be accurate (ie. that when the client complains of "Insufficient Memory" and then crashes

Hi Mathias, I can't speak on Win2k Pro but have recently tested WinXP Pro. Now with XP you will need to use the reg file included with the samba archive (in a sub directory in the docs dir). Once that has been applied (presuming all accounts have already been created on server) you can join the domain and log in no problems. -- Regards, Deryk Robosson Robosson Business Services 22

Hello, I'm having some problems with the this setting. I'm trying to have a winxp client logon to a samba-2.2.7a machine which is using a win2k server as password server. It works if I use a linux client (smbclient): smbclient -L pandora -U bush%george Pandora is the samba machine, and it contacts the w2k server and validates bush's password. This is working, but only with

Hello, I have a network, where users want to login with their same username from Windows 2000 and from Windows XP on a samba PDC. When the machines logon, I can see the OS in the logfile of the machine on my server, but i cannot use different profiles for Win2k and WinXP, because the %a in smb.conf always gives back Win2k. The profiles of win2k and winXP aren't compatible, so i can't just

I have samba 2.2.7 running on a RedHat Linux 7.3 system that is being used as a PDC and a file server for a group of Windows 2k and Windows XP Pro computers. I am having a problem with the roaming profiles working on both the 2k and XP machines. The profiles seem to load fine when you log on, but when you log off it will only copy the ntuser.dat file and then a few more files (seems to go to

I am running Debian on a LAN. I am trying to send popup messages(Winpopup protocol) but just get the same error over and over. We have a WinXP machine named "Mindelessdemon"(He is actually a very nice guy, don't get foolled by the demon stuff), a Win2k machine called "Whitehead" and a win98 machine called "Wyrm". I cant connect to the WinXP or Win2k machine

Hi I have ported syslinux to win2k/winxp. It is attached. It has been tested with floppies and flashcards, but not on harddisks. On harddisks I'm not sure if I should use \\.\PHYSICALDRIVEX or \\.\X: as arguments to CreateFile (I'm no windows wiz) and I do not currently have a system to test this on. The program can be compiled using mingw or in cygwin using the option -mno-cygwin

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

Real quick I have 1 Windows 2000 Pro machine that can connect to my Samba server just fine.....no problems whatsoever.... I have 5 other machines, all running Windows XP Pro (all have been updated with Microsoft's latest patches, etc.) that cannot even access the Samba server. I have only a Workgroup created, and from each of my XP machines, they all see the Samba server just fine in the

I am using samba 2.2.7a an would like to use the %a variable to distinguish between WinXP und Win2k because I (and others) have problems when using the same roaming profiles for both OP-Systems --> During Logoff when writing back the profile I get an error message: "unable to write ... file prxxx.tmp" and after this the profile when written back by XP is not more usable

I have Samba running on my web server (it's not a major file server or anything) so that I can access files on it from my local network. Mainly things like I can view my webalizer pages thru a local machine, or to copy files over for installation. Anyway - every 2-3 hours, I 'lose' the connection and have to reboot the WinXP machine (yeh, I know - 'Rule #1 of Microsoft - When in

Hello fellow Samba users and devs. This is my first post. I've searched documentation far and wide for Windows, Linux, and Samba, and have not been able to shed any light on this issue. I can't get more than 8MB/s during a single file copy stream out of my Samba server over my 100FDX switched network either from Win2K or WinXP (I don't have a *nix client to test with). The network

My Win98(SE) Samba clients can query the Samba-exported printer status, but Win2K(SP3) clients cannot. Both clients can actually print documents. I am running Samba v2.2.3a on a Linux (Red Hat v7.3) system. This server makes 2 printers (via a LPR subsystem) and several shared directories available to our Linux, Win98 and Win2K (soon to be WinXP also) clients. From a Win98 client, print

Dear List: I have a network (about 30 PCs) that was working fine using USER=SHARE. Last weekend we switched over to take advantage of a Win2K server (recently added to the network) to be used as a PDC, Active Directory, etc. The network clients are a mix of WinXP, Win2K-SP3, and WinNT-SP5. After the switch, the WinXP clients started experiencing a severe slowdown after a short period of

We are seeing some strange inter-subnet browsing issues here, our setup is as follows: .129 subnet [ samba box ] | | [ router ] ^ _.1 subnet _/ \_ .9 subnet_ The .129 subnet contains only the samba server configured to the letter from the browsing.txt file. The .1 subnet conists of win98 and winME boxes all configured from DHCP to use the samba box for WINS lookups.

Dear List: I have a network (about 30 PCs) that was working fine using SECURITY=USER. Last weekend we switched over to take advantage of a Win2K server (recently added to the network) to be used as a PDC, Active Directory, etc. The network clients are a mix of WinXP, Win2K-SP3, and WinNT-SP5. After the switch, the WinXP clients started experiencing a severe slowdown after a short period of

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.

I can actually answer this one. Windows 2000 and higher NO LONGER USES WINS. While 2000 server does still include a WINS server component, 2000 clients no longer (mostly) use them. They now use the active directory DNS for all resolution instead of WINS. I'm a bit out of my element, but I've had my WINS get hosed before, and I never knew until somebody with win98 called and said they

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.

Hi, I have a linux box configured with samba-3.0.1pre1-1 joined to my Win2k ADS domain. I can succesfully use kinit and smbclient -k without entering a user/pass to connect to things on my network. Winbind, getent, wbinfo, ... everything works great however, from WinXP and Win2k client hosts I cannot connect to my linux shares. From Win95/98 clients works great. Always that I connect from