similar to: huge number of port 139 messages in nmbd.log

I think this is probably an XP SP2 issue but perhaps you've seen it before? We use smbclient 3.0.13 to download files from a machine "Testmachine" that used to run Windows 2000 and use the zonealarm firewall. A couple of days ago it was upgraded to XP SP2 (fully patched) using the built in Microsoft firewall. One folder "Example" was "shared" and the firewall

Help please, a file server was upgraded from: Mandriva 2007.1, Samba 3.0.24-2.7mdv2007.1 to Mandriva 2008.1, Samba 3.0.28a-2.1mdv2008.1 and it broke something badly. After the upgrade logins from all XP workstations broke - some of the time. For an existing account (one with a profile already in the home directory) sometimes it will login normally. Well, almost normally, it never seems

Upgraded a Samba server from 3.0.28a-2 to 3.4.7-0.2. Initially the XP workstations could not log on (not finding machine account) then discovered a new "passdb" variable, so added to smb.conf: passdb backend = smbpasswd and also changed all browseable -> browsable. Restarted the server. Domain logins worked. Test files saved to desktop are retained between logins (are stored in

Our XP SP1 (patched with everything but SP2) workstations are logging events like: "Windows has detected that offline caching is enabled on the roaming profile share - to avoid profile corruption (etc.)" Following some goodle threads this was added to smb.conf (attached) csc policy = disable but the event still occurs, although only when something has been saved to the profile before

Hi, I am discovering several error messages from one of our samba servers. Logcheck says: Security Events =-=-=-=-=-=-=-= getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected

After doing some system work, including upgrading the Samba server to 3.0.28a from 3.0.24, upgrading the kernel to 2.6.24, and changing the firewall rulesk, the XP workstations which belong to that domain, the right click "run as ..." option is slow to bring up a dialog. The phenotype is this: right click some program (for instance, a shortcut to the "command prompt")

Setting up nut on a system where an LVM volume holds the root filesystem.. What is the appropriate device form to use with "mdadm --readonly" in halt? This is on a CentOS 5 system. So far I have found three possibilities, but I do not know which one (if any) will still be valid that late in the halt procedure: 1. /dev/md0 (from posts on the net) 2.

I recently ran into a situation where a Samba upgrade apparently broke the machine records in the smbpasswd file, with the resulting symptom that domain logons on those computers would fail about 95% of the time. (A very strange symptom, how it worked sometimes is still a mystery to me.) Similarly, this would fail: % smbclient -L saf01 -U 'saf/mathog%(password)' session setup failed:

Well this is even more interesting. Parts of the profile are not being saved back to the server, at least for existing users. For instance, 1. login 2. change the start menu to "classic view" 3. rearrange the desktop 4. logout 5. login again start menu is back as it was and it isn't classic view any more. Very strange. Wipe the test profile on the server and the copy on the

Yesterday I migrated a Samba server from one machine running Samba 3.0.13 (on Mandrake 10.0) to another running 3.0.20-3 (on Mandriva 2006). The contents of: /etc/samba/* (all the .conf files) /usr/local/samba/private/* (secrets.pdb, smbpasswd) were moved intact from one machine to the other, as was all of the user data. I even checked md5sums - no changes to any of the samba files. Then

Hi all, On my Suse 9.3 prof. server I had two NIC’s: Eth0 IP 192.168.1.1 Eth1 IP 192.168.2.1 Now I added new NIC (eth2) Eth0 IP 192.168.1.1 Eth1 IP 192.168.2.1 Eth2 IP 192.168.1.2 Now I erased eth0 config and turned off this NIC in motherboard bios Eth1 IP 192.168.2.1 Eth2 IP 192.168.1.2 I renamed eth2 to eth0 Eth1 IP 192.168.2.1 Eth0 IP 192.168.1.2 And, finally I

> The domain user does login eventually. Mostly. Roaming Profiles are > very broken on W7: the top level "Vista.V2" directory is created, but > nothing is stored back into it on the server, and the logged in domain > user ends up with a C:\Users\Temp profile. Thanks to Drew Vonada-Smith the roaming profiles are working again. The problem was that information stored in

After update from 3.0 to 3.4.7 roaming profiles were not being saved on XP. Disabled ipv6 on our Samba server (some update must have re-enabled it) and rebooted. Now profiles on XP seem to be working OK again. Not so for Windows 7. This is a newly set up Windows 7 machine, registry fixes were applied as indicated here: http://wiki.samba.org/index.php/Windows7 was able to join domain, and

Short description: when upsmon starts it logs this to /var/log/messages: Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found Near as I can tell upsd is running properly. Long description: Centos 5 system (x86_64), built nut 2.2.2 from stable source with ./configure --with-usb --with-user=nut --with-group-nut make

Just in case anybody else ever needs these, here are my semi-automated powershell cloning scripts for Windows domain clients for Samba domain servers. ftp://saf.bio.caltech.edu/pub/software/windows/Cloning.zip They are not very polished, but do what I need, and could serve as a starting point for other sites. These have been tested only on XP SP3. These scripts do not use sysprep, so the

> Date: 30 Nov 1998 20:22:27 GMT > From: mathog@seqaxp.bio.caltech.edu > To: mlist-samba@nntp-server.caltech.edu > Subject: W95/98 connect to any SMB share as another user? > Message-ID: <73uuq3$s7j@gap.cco.caltech.edu> > > map H: as \\machine1\share1 as username=John, password=JohnsPassword map > M: as \\machine2\share2 as username=Jane, password=JanesPassword >

Hi, I have setup samba server on my linux box (Fedora Core 4 with latest samba, just updated via RHN) and has configured file sharing via samba for this server and connecting to it from my windows xp box. So far, everything works fine and it is very fast. Then, I configured a printer, and shared it via samba. And, I can see+connect to it from Windows XP and can even print. But, everything

Dovecot 2.0.13 on a 64 bit linux. We have an archiver account on one machine. Most mailing lists that handles go directly to it and everything is fine. However, there is one campus list that will only send to real people. So for that one I subscribed. When one of these messages comes in, which is 1-2x per week, I copy it to an export folder and then manually run a script which does: cat

We're running an older version of Samba on an Irix machine, and just got 2.0.2 working (finally!) on our Intel/Linux box. The odd thing, is that findsmb gives different results on the two systms. On Irix it lists the NetBIOS names with OS descriptions, but on Linux it lists the IP name and no OS description. I went through it line by line and found the first difference at: ../nmblookup -r

I am trying to automate W7 joining to our Samba domain. It works fine through the Windows GUI from the W7 workstations. However, for a script one would have to store password used for domain access, and since that is the server's root password, I really don't want to hard code that into a file. Is there a way to set (temporarily) a Samba server so that it will accept (admin/anything) as