similar to: samba 2.2.7a, security=server, password server = win2k, winxp client

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'm building an new server with CUPS 1.1.18 and Samba 2.2.7a (Both compiled from source) Installed the printer with CUPS and printed a test page with CUPS. Next step make Samba use CUPS. I've used cupsaddsmb command to do this, which completed successful. Running command: smbclient //localhost/print$ -N -U'root%XXXXXXXXX' -c 'mkdir W32X86;put /var/spool/cups/tmp/3e1bf35d1d1f9

What kind of error is "NT_STATUS_OK"? Logs below: [2003/01/29 15:30:46, 3] libsmb/namequery.c:resolve_lmhosts(768) resolve_lmhosts: Attempting lmhosts lookup for name TESTE011<0x20> [2003/01/29 15:30:46, 3] lib/util_sock.c:open_socket_out(845) Connecting to 192.168.100.1 at port 445 [2003/01/29 15:30:47, 0] rpc_client/cli_netlogon.c:cli_net_auth2(157) cli_net_auth2: Error

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

Hi All- Please tell me if I'm posting to the wrong list. I looked for the list called samba-ntdom (listed at http://us1.samba.org/samba/archives.html) because it seemed a more appropriate forum, but it looks like that list has been dissolved. Has the discussion for that list moved to some other list? Anyway, here's the problem that I'm hoping someone can help me with: I have

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

I hope this is just one of those issues where just after hitting the send button I figure out what is wrong. Client is 3.0.4 (also tried with 3.0.3) and server is windows 2003 with all patches as of today applied via windows update. Short summary: wbinfo -u doesn't work and wbinfo -g lists just a BUILTIN domain. I have done this lots of times, but now winbind seems to be not working anymore.

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

G'day all... Has anyone had any success in achieving the above, without requiring the user to run smbpasswd on the samba server? On the client machine (2000 or XP) when I press ctrl-alt-del and attempt to change the password I get the error "The User name or old password is incorrect..." I need to keep things as simple as possible for my users, they're not highly computer

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

I have a script that is attempting to notify a user that a job has finished. However, when called from within the script nothing is received by the user. When the equivalent message is sent from the command line, the user receives the message. The portion of the script that is relevant is below: ----- cut from script ----- #!/usr/bin/sh : : MESSAGE="$WINNAME, your job $_3GJOB\nhas

Hello, I have big problem with WinXP clients on my network. I tried to find some solution via google, but without success. I have Win2K Server as a PDC and Linux machine as a fileserver. Linux box is joined in domain and all users are authorised against W2K server. When I start WXP client everything works OK. But after about 30 minutes client workstation lost connection to Samba server and

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

Samba 4.0.4 installed, provisioned by classicupgrade, running on Debian Squeeze: -------------------------------------------------------------------------------- The issue is, that changes to the roaming profile is not transferred after log ins/outs between Win2K and XP machine. In example: I log into the W2k machine with my testuser and create a "testdir1" and "testdir2" on

Really odd problem that I'm having, and I'm totally clueless as to whats causing it. Scenario: 2 mounts from a W2K machine to a Linux box. The Win2k box gets powered down overnight. Obviously during this, if i do a df it freezes because it cant reach the drives. I used to be able to boot the machine back up in the morning and it would see the drives again. Not anymore. The same

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, 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.

Emperors1000@aol.com wrote: > > Dear reader, > The emperorsclothes list does not seem to be working. Please forgive us if > you receive this post twice. - Jared Israel, www.tenc.net > ************************** > URL for this article: http://emperors-clothes.com/articles/rozoff/abyss.htm > > To join the Emperor's Clothes email list, go to >

Johan says: > After upgrading from 2.2.5 to 2.2.8, our WinXP clients don't recognize our > DFS-root shares as DFS anymore. > When viewing the properties of a DFS root share on a WinXP client, we don't > get the "DFS" -tab page. Luc says: > I'm having the same problems with DFS and WinXP clients since I upgraded > to 2.2.8. > > >Can anyone else

Has anyone else seen this but I just came across this on google trying to research my problem. Hi, I've always found adding w2k workstations to a samba server a bit 'hit and miss'. A couple of things I did which helped around this problem when I had it: 1. Define root as a samba administrator 2. Created a user root (with same password) on the w2k machine - set as an