search for: webcob

The error message is the usual panic error - 3.0.11 and FreeBSD 4.8. Samba 3.0.8 ran fine with the same config (admittedly there were a few roaming profile sync related crashes, which is why I was upgrading). Now however I can't even connect - it crashes immediately, respawns and crashes again. My Samba server is a domain member of a Win2003 domain controller used for roaming profile

The second instance of Quickbooks shows a "file may be corrupt" message. 56310 DENY_NONE 0x2019f RDWR EXCLUSIVE+BATCH /MY_REALLY_LONG_PATH/My File.QBW Thu Mar 3 19:42:20 2005 56310 DENY_NONE 0x2019f RDWR EXCLUSIVE+BATCH / MY_REALLY_LONG_PATH/My File.QBI Thu Mar 3 19:42:20 2005 It works on Windows - just copied the same file to a network mapped windows

My Windows 2003 machines can get to shares on my older Samba servers (2.2.8a), however on newer versions of Samba (3.0.2), I get the following error message: \\servername is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The request is not supported. These same shares are

At our organization, we're currently gradually migrating the workstations from Windows 98 to Windows XP, while retaining the use of our samba server as a PDC. For those who may remember my previous post, our upgrade to Samba 3.0.11 from an ancient version (2.2.3) I inherited went extremely well, and I was thoroughly impressed how little I had to change to get everything running. Anyways,

Here's the problem we're encountering: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Having intermittent problems regarding users opening/accessing/saving/writing MS Excel files into samba shares. When a user accesses a file on a shared volume via samba, they can open an Excel file and end up with one of two conditions; either their system hangs after opening the file for a short pause

Hello, I have a samba server running at a customer site and they have the follwing problem: Employees of that company have for extended periods sometimes word documents opened for editing, but it happens regularly that for an half hour or more no activity takes place because they are working on something else (it's a flower seed growing company , with pc's in the glasshouses and they have

Ok this works: /usr/local/samba/bin/smbclient -U Administrator \\\\DC1\\C$ <file:///\\\DC1\C$> I can sign in and do normal smbclient stuff. I can't so far figure out how to send a message though. /usr/local/samba/bin/smbclient -M DC1 /usr/local/samba/bin/smbclient -M DC1 -I 10.1.0.6 /usr/local/samba/bin/nmblookup DC1 querying DC1 on 10.255.255.255 10.1.0.6 DC1<00>