similar to: Can't connect Windows 7 client to Samba 3.3.12 on AIX

This samba is scheduled for upgrade. We've been testing samba 4.3.8 packages (from BULLFreeware) on other AIX. It was not easy the install, even with RPM packages. I hope to do the upgrade soon, but I need to have this particular user working now. What puzzles me is that I have other windows 7 PCs happily working on the same resource. 2017-01-04 16:21 GMT-03:00 Rowland Penny via samba

On Wed, 4 Jan 2017 15:58:39 -0300 Andres Tarallo via samba <samba at lists.samba.org> wrote: > Hi !!! > > I've Samba 3.3.12 running on AIX, I have a few windows 7 using a > shared resource on that server. > > This is the shared resource definition: > > [shared_disk] > comment = shared_disk > path = /home2/nfs-chiappe/shared_disk >

Every so often I will see this in my log file: smbd[1034]: [2009/02/02 08:47:21, 0] lib/util_sock.c:get_peer_addr_internal(1607) smbd[1034]: getpeername failed. Error was Transport endpoint is not connected smbd[1034]: read_socket_with_timeout: client 0.0.0.0 read error = Connection reset by peer. smbd[1036]: [2009/02/02 08:47:22, 0] lib/util_sock.c:read_socket_with_timeout(939) smbd[1036]:

Hi All, I installed OpenSUSE 11.0, updated samba server to 3.2.4 version. Added two users in linux and samba with user names "test1" and "Test2". (Please note the capital letter in Test2). Created two shares in /srv/samba/shares "test1" and "Test2". The permissions of the shares are as below. drwx------ 2 test1 users 4096 2009-12-11 12:42 test1 drwx------

Samba 3.2.5 I'm running into an issue when using Vista to access Samba shares. I'm able to connect intermitently and it stays connected for a brief period of time (under 60 seconds) before I get the following error on the Vista box: "Network path was not found" In syslog it shows: [begin] [2008/12/09 11:09:03, 2] auth/auth.c:check_ntlm_password(308) check_ntlm_password:

Hi, I have a problem of Access denied to samba server from win7 64bit behind a VPN. the samba server is 3.2.5-4 release on a debian lenny (I will upgrade it soon), member of a win2K AD domain. the win7 PCs are on the same AD domain, they can access to an other samba server witch is very similar (same release, same smb.conf, same VPN config). If I do on a win7 PC: net view \\srvlinux I see:

Hi, I'm hoping someone can help with this. We have a 3.3.8 Samba server, on Centos 5.5 64, security DOMAIN, works beautifully with XP. When windows 7 systems attempt to log in via \\NAME, the login window just continually repeats, but they can login successfully when using \\IP_ADDRESS Samba log shows the below in response to windows 7 login attempts. [2011/01/25 10:08:26, 0]

Help, ???? I have set up?RHEL5 to authenticate against Windows Server 2003 R2 Active Directory using ldap/kerberos.?? Everything works fine except that I cannot map a drive from Windows machines to the shares I have set up in Samba on the linux machine.??? I can log into Linux using accounts in AD, and running smbclient \\\\linuxserver\\sambashare works fine on the linux box using account

Hello, I'm running samba-3.0.33 (samba-3.0.33-3.15.el5_4) On Centos 5.4 and some files have issues being copied from the Samba server to the Vista (Service Pack 1) clients local disk via Windows Explorer, copying too the Samba server also has no issues and copying via the CMD prompt has no problem, I'm getting the following errors 1. Invalid MS-DOS Function

Hi all, Earlier I emailed the list on some issues I was having with Windows 7, and one of those issues was the trust relationship breaking down after one month. I think I have some more light to shed on this topic. First, some environmental facts I am running Ubuntu Karmic 9.10 with Samba 3.4.0-3ubuntu5.1 I have installed the latest LDAP schema into OpenLDAP 2.4.18-0ubuntu1 I have a working

Hi, I am trying to upgrade Samba from 3.3.2 to 3.3.9 for Win7 compatibility issue. It is running on Redhat 9.0 (I've planned to upgrade to Centos 5.5 in a second setp) and without any ldap backend (tdbsam actually). As I have already done in the past for upgrading, I have done the following procedure : 1) Compile 3.3.9 . My configure option are : ./configure --with-acl-support

I am trying to access a samba share from windows 7. The samba version is 3.3.3 on FreeBSD 7.2, The samba daemons are running and I can see the server in my Network Places on the Windows client. When I try to login using the username "spacebizall" and password (the same as the account on the server) I receive an "unknown username or password" error. I installed the registry

Hello all, I've set the log level of my DC to 3. I'm using it as a file server too although it is not recommended. I now have the following errors in log.samba: [2015/03/03 08:58:54.244106, 2] ../source4/dns_server/dns_query.c:629(dns_server_process_query_send) Not authoritative for 'versioncheck.addons.mozilla.org', forwarding [2015/03/03 08:58:54.266123, 1]

Hi, I just updated my samba servers (debian wheezy, sernet samba4) from version 4.1.12-9 to 4.1.14-9 and suddenly all my hp printers produce errors instead of printing. Kyocera printers are still working. HP printers all use HP Universal drivers Version 5.9.0.18326 with snmp disabled. Errors occure from Windows Server 2003 32Bit and Windows 7 clients. Here's an level 1 log of what

I have a problem with samba (3.2.3) not working properly with windows clients. I run a FC11 samba storage server, that has windows and mac client machines connecting to it. So far mac clients work. However windows client, whenever I try to install some application that is stored on the samba server, or even copy a very large file (few gbs) I get this in /var/log/messages and the file

Greetings list, I am about setting up a domain controller in a little company, so I choose samba (debian lenny) and I did it against openldap. Everything seems to be ok in the server but when I try to log in (windows client) I have a bizarre output: it said that my profile will not be saved. And after that when I try to connect to virtual machine running in the same computer, it doesn't work:

Hello, All! I found that Samba checks description fields encoding at various tdb files to late. Case 1. FreeBSD with UTF-8 support. At some cases FreeBSD's adduser script can save incorrect UTF-8 sequence to GECOS /etc/passwd field. (Here is example http://www.acc.tula.ru/~acc107_3/samba/miscoding/gecos.txt) When user is added to Samba, Samba reads GECOS field "as is" without

Hi, I just upgraded from 3.0.32 to 3.3.4 on Aix 6.1, and noticed that a 'net view' command from a windows xp workstation fails with a system error 1745. The share works perfectly fine, just the net view command doesn't. This occurs when there is an umlaut in the comment line of the share. Is this WAD? here are the debug lines...from Samba 3.3.3, but it's the same error. Thanks,

Hello, as I continued exploring Samba 3.0.4 as a PDC, I managed to get roaming profiles up ... Saving changes worked out fine. I logged in as TheUserWithUID=0 ... and tried to add a user. Access denied. The logs for the XP-client contain: > [2004/06/03 23:10:46, 2] passdb/pdb_ldap.c:init_group_from_ldap(1792) > init_group_from_ldap: Entry found for group: 513 > [2004/06/03

Every so often I will see this in my log file: Feb 2 08:47:21 int-torino smbd[1034]: [2009/02/02 08:47:21, 0] lib/util_sock.c:get_peer_addr_internal(1607) Feb 2 08:47:21 int-torino smbd[1034]: getpeername failed. Error was Transport endpoint is not connected Feb 2 08:47:21 int-torino smbd[1034]: read_socket_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Feb 2