search for: psmnv

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, I have a samba PDC (with ldap), all ok for several months since today users experience very slow login, in my log I have : [2008/12/03 11:00:18, 0] auth/auth_util.c:create_builtin_administrators(792) create_builtin_administrators: Failed to create Administrators [2008/12/03 11:00:18, 0] auth/auth_util.c:create_builtin_users(758) create_builtin_users: Failed to create Users net sam

I am trying to setup a way to watch each file that is created, updated, and deleted through samba. I have currently looked at inotify but I am not sure if that is the best way. What suggestions would you have to setup a way to get some type of event when one of these actions occur? I would like to watch a directory recursively and be able to run a shell script or perl script and that script know

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

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

I have samba 3.0.28 installed on several servers and winbind dies every couple of days on all of them. The deaths appear to correlate with the following log messages: [2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655) PANIC (pid 13395): internal error [2009/01/25 04:02:09, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 14 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x800ccc10] #1

Formerly, I could connect to my CentOS 7.5 servers using \\server<file://server> but after upgrading to 4.8.3, now I must used \\server.my.domain<file://server.my.domain>. What happened and how can I fix it? --Eric Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should

I have samba 3.0.28 installed on several servers and winbind dies every couple of days on all of them. The deaths appear to correlate with the following log messages: [2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655) PANIC (pid 13395): internal error [2009/01/25 04:02:09, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 14 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x800ccc10] #1

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

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, or sometimes even rename a file, 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. 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 causes this? Here's the

Does anyone know how I can tell which Kerberos libraries (MIT or Heimdal) my Samba was built with? -- Eric Robinson Disclaimer - November 13, 2008 This email and any files transmitted with it are confidential and intended solely for samba@lists.samba.org. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in

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 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 just read the Samba list rules and did not see anything against offering payment for expertise, so I'm letting the list know that I need Samba help and am willing to pay normal consulting rates. If you are interested, please respond by direct email. We have a number of CentOS 5.2 and 5.3 servers that work quite well and are AD-integrated using relative IDs to maintain UID/GID consistency

We have a lot of users on our AD domain, and the more we add the longer it takes to get a directory listing on my Linux servers. When I do 'ls -l' it might take 20 seconds before the listing starts. However, if I immediately do 'ls -l' again, it comes up quickly. I assume this is because samba/winbind is polling the AD domain controller on the first attempt. Is there any way to

We have three Windows domain controllers in our AD domain. They are DC01, DC02, and DC03. We have Linux (RHEL5 and 6) servers in the domain as well. The Linux servers are working fine with AD. However, they are currently configured in krb.conf and krb5.conf to use only DC01 for AD domain controller. if DC01 is down, Linux servers cannot authenticate. How do we configure the Linux servers to use

There are three DCs in my Windows 2003 AD domain, but I have noticed that only one of them is referenced in my krb.conf and krb5.conf. Should there be a reference to one or two of the other domain controllers? If the DC goes down, how will my Samba/Winbind servers authenticate? -- Eric Robinson Disclaimer - February 27, 2011 This email and any files

I have samba 3.0.28 installed on several servers and winbind dies every couple of days on all of them. The deaths appear to correlate with the following log messages: [2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655) PANIC (pid 13395): internal error [2009/01/25 04:02:09, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 14 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x800ccc10] #1

I've been Googling, but have not come up with anything. It worked before the update, bit now samba won't start. I see the following in the logs. -- Unit smb.service has begun starting up. Apr 22 18:51:47 001cognos01.ccnva.local systemd[1]: smb.service start operation timed out. Terminating. Apr 22 18:53:18 001cognos01.ccnva.local systemd[1]: smb.service stop-final-sigterm timed out.