similar to: Chronic Intermittent Problems with "File system does not support long filenames."

When trying to create a file or folder on a samba share (3.0.28-0.el4.9) from a Windows 2003 R2 server, I occasionally receive an error message stating that the target filesystem does not support long filenames. This happens even if object name follows 8.3 naming conventions. It does not *always* happen. Also, I have another samba 3.0.28-0.el4.9 server where this does not happen at all. What

When trying to create a file or folder on a samba 3.0.28-0.el4.9 share from a Windows 2003 R2 server, I continually receive an error message stating that the target filesystem does not support long filenames. I have another samba 3.0.28-0.el4.9 server where this does not happen. What causes this? Here's the smb.conf from the "bad" server. It's pretty much the same as the

Attempting to install a fully virtualized instance of Windows 2003 fails on CentOS 5.2 x86_64 with xen-3.0.3-64.el5. After issuing the command... # virt-install --hvm -s 70 -f /vm/ts05/ts05.dsk -n ts05 --cdrom /download/Win2003x64/disk1.iso --vnc -r 1024 The script just hangs at... Creating domain... In another terminal window, I can see that vnc-viewer has been started and is

Hi all, Using the Chronic.parse method, I see some weird behavior. Perhaps someone can set me straight or confirm that it is indeed weird. Note that the date changes to one day earlier in the last example below. Since the date and time are uniquely specified using the hh:mm:ss notation -- though in the future -- I would expect the same result as when I specify the time as in

Hey all, Chronic will parse a date range in console: Chronic.parse(1/1/2011 - 1/1/2012, :guess => false) => 2012-01-01 12:00:00 -0500..2012-01-01 12:00:01 -0500 However, when I use logger to check if it''s parsing in application, it is not: logger.info "The value of history date is #{history_date}" => The value of history date is 1/1/2011 - 1/1/2012

Hey all, I am getting this error: NoMethodError (undefined method `gsub!'' for 2012-01-22 17:00:00 -0500..2012-01-23 00:00:00 -0500:Chronic::Span): in this code: date_range = Chronic.parse(the_date, :guess => false) reports.sum_distance_by_date(date_range).each do |d| u[:m] << d end def

Hello! I found your address on a site about wine and spirits, cigar and good living and I thought that you would be interested by the services that our site offers. Wine Alley is a virtual Club for all those interested in wine in both a professional and personal capacity. You too can be among our 7085 members to receive our free weekly bulletin which commits you to nothing but presents an

Our samba boxes are integrated with our Windows 2003 AD domain, with Windows servers acting as AD domain controllers. Everything is working fine, but in my krb.conf and krb5.conf files on my Linux boxes, I currently only have one Windows server specified as the AD logon server. If that server is down, I suspect that Linux users could not login. How to I specify more than one AD domain controller

Any ideas why this is not working? [root at host67 ~]# pdbedit -u testuser -h \\\\five-68\\testuser -p \\\\five-68\\testuser\\profile Unix username: testuser NT username: Account Flags: [U ] User SID: S-1-5-21-369316088-3201261441-1704813131-2216 Primary Group SID: S-1-5-21-369316088-3201261441-1704813131-513 Full Name: Home Directory: \\host67\testuser

Problem: When I try to open a samba share from a Windows 2003 R2 computer, I get a login challenge. When winbind and smb start up, the logs look clean except for the following: smbd.log -------- [2008/11/11 04:42:16, 3] lib/privileges.c:get_privileges(261) get_privileges: No privileges assigned to SID [S-1-22-1-0] [2008/11/11 04:42:16, 3] lib/privileges.c:get_privileges(261)

I have two CentOS servers running samba3-3.0.34-37. When I connect to a samba share from my Windows 2003 R2 servers, and then try to copy a file to it, I often get the message "target filesystem does not support long filenames." Sometimes it works and sometimes it doesn't. I've been fighting this problem for 2 years. I've replaced my Windows servers, changed my Windows

I've been struggling for almost 2 weeks to get Samba working on two new servers. When I try to open a Samba share from a Windows 2003 computer, I always get a logon challenge. I always get the following lot message [2008/11/13 16:05:06, 3] lib/util_sid.c:string_to_sid(228) string_to_sid: Sid MYDOMAIN\mygroup does not start with 'S-'. [2008/11/13 16:05:06, 2]

Mac OS details: Our client was able to access her network resources without any problem until yesterday. She is using a high end Macbook Pro. She has the latest full version of Dave 7.1 installed. Her Mac OS X is 10.4.11 When she attempts to connect to these resources she receives the following error: "The Finder cannot complete the operation because some of the data in

Good morning. I'm having some problems with one thread of samba, taking excessive CPU usage. This is one single thread, that i can kill with 'kill -9 pid', and the server will keep other connections. This thread will severely slow down the server, and clients notify me within minutes of this happening. In essense the server becomes unuseable, because it's too slow. This is

Hi, I have successfully compiled and installed Samba 4.0.0rc2 on Debian Squeeze as described in the Wiki. In order to support Win XP and Win 7 clients, I have created GPOs for folders redirection. The problem I am facing is with random PANIC messages in the logs and logon/logoff/file access process gets hung on the client. Here are the logs: Oct 18 13:42:32 pdc smbd[27384]: [2012/10/18

> I have multiple CentOS servers running a couple versions of Samba > serving various Windows versions and I've never once ever seen > this message. Glad to hear it. That's the kind of behavior I would normally expect. One thing that might be different between our environments is that my users are all in Remote Desktop sessions connected to a pair of Windows terminal servers.

I have two CentOS servers running samba3-3.0.34-37. When I connect to a samba share from my Windows 2003 R2 servers, and then try to copy a file to it, I often get the message "target filesystem does not support long filenames." Sometimes it works and sometimes it doesn't. I've been fighting this problem for 2 years. I've replaced my Windows servers, changed my Windows

Is there any way to have doveadm NOT log using mail_log, but have the daemons do it? (or have doveadm's log go to syslogd)? Thanks! ex: doveadm(ler): Info: copy from SA/FN: box=#ARCHIVE/2015/11/SA/FN, uid=1, msgid=<cm.021005.htukhul.cdhuutux.j at cmail2.com>, size=107835, vsize=110376, from="Alley Boost" <alleyboost1 at gmail.com> , subject=Alley Boost: VIP Mixer

Does anyone know how can I monitor files that was being open and access in the samba directory? If this was not possible, is there third party apps that can help me do what I want? -- Nelson Serafica http://nelsontux.blogspot.com

SILICON ALLEY TALENT FAIR - TOMORROW !!! http://www.myworkster.com/myworkster/page/eventdetail/1587252515 Sign up as a job seeker use code Rfrio - 100% Discount ! Over 140 startups coming ! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to