similar to: Cannot join domain from WinXP

===INFO=== Server: Fedora Core 2, Samba 2 Client: Windows XP, all TCP incoming ports firewalled, outgoing TCP permited Problem: Cannot join to domain ===SHORT-LOG=== write_socket: Error writing 5 bytes to socket 23: ERRNO = Connection reset by peer ===FULL-LOG=== [2005/09/21 17:56:44, 0] lib/util_sock.c:write_socket(455) [2005/09/21 17:56:44, 2] lib/access.c:check_access(324) Allowed connection

Hi all, here's hoping you can help with a problem I have got. I am currently running samba 3.0.7-1 on a Suse 9.0 system and I am having the following problem. I am trying to get my samba server to join a windows NT4 domain called BVFL-DOM and then use winbind to get user names from that domain to be use samba. The samba box joins the NT domain without a problem and I can use NT server

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Don't change nothing in the smb.conf and appers in the log.smbd this: [2005/02/27 15:48:57, 2] auth/auth.c:check_ntlm_password(305) ~ check_ntlm_password: authentication for user [mdonada] -> [mdonada] - -> [mdonada] succeeded [2005/02/27 15:48:57, 2] lib/access.c:check_access(324) ~ Allowed connection from (192.168.2.252) [2005/02/27

After building the latest CVS sources obtained this morning 6/12/03 I can not log in to my Samba PDC using a LDAP backend. Can someone tell me what I am dooing wrong please. --- windows event log Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 3210 Date: 6/12/2003 Time: 12:29:33 PM User: N/A Computer: JEFF-WS Description: This

Hi Neo I installed the samba 3.0.23.d, because I thought that it is a """""stable version""""", but the problem continued. Same error, same problem: "smbd/sesssetup.c:setup_new_vc_session() setup_new_vc_session: New VC == 0, if NT4.x compatible we would ". I tried to use your command: "/usr/local/samba/sbin/smbd -V Version 2.2.08a

I'm trying to make windows xp a member of a samba domain, after pressing ok, I type in Administrator (has uid=0) and type the password, but windows tells me that "The user name could not be found." although the log file looks ok, help? [2004/11/23 02:28:06, 2] smbd/sesssetup.c:setup_new_vc_session(608) setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old

I've recently set up an Openfiler 2.2 system, with a few disks under md (RAID6), LVM on top of that, and formatted ext3. When snapshots are in use, large file transfers (transfers of large files, or transfers of many smaller ones) are disconnected - Leaving a Windows 2000 client with an error like 'The network resource is no longer available'. Re-trying works, but cuts out again

It seems that my smbd process got fuxed somehow. It appears to have take up all the file handles, and there were over 130 smbd processes running on the system. I'm not entirely sure what happened. My first thought is that something bad happened between the server and the Windows client that's running Kaza (with a couple hundred mid-download files) and it just spiraled out of control,

Hello list! Are there any known issues regarding samba3 - linux 2.6 kernels? I'm getting disconnects every 20 seconds or so, both via cifs and smbfs mounts. This occurs regardless of whether the connection is in use and sometimes leads to I/O errors (even doing 'ls' on a mounted dir). It is not consistent though, and seems to be triggered by high network traffic. When it is

Specifics samba-3.0.0beta1-1.i386.rpm on RedHat 9 and smbpasswd authentication, the machine is the PDC and security is set for user. The machine account was setup on the fly and it appears in passwd, shadow, and smbpasswd files as it should. However it seemed to take a very long time to join the domain, about 1-1/2 minutes. I can browse the Samba PDC machine and access the shares, etc. After

Hi there, Since upgrading our debian sarge boxes to 3.0.23c, we have found that we are unable to connect to shares using the official hostname of the servers (short or fully qualified) but can still use its netbios aliases (again, short or fully qualified). As nothing else has changed in our configuration, I think that the change of behaviour is down to the newer release and can find nothing in

Windows 98 client cannot print via samba to PrintPro printer "exported" via Cups/PrintPro on PrintPro/Samba server. "Exporting" with Cups on server node allows print drivers to be downloaded to Windows clients from the server. Any help or suggestions are greatly appreciated. Win98 node gim98.rsmas.miami.edu [129.171.97.21] connects to Samba 3.0.0-15 server "prima"

Hi all, I'm usigin Samba version 3.0 with OpenLDAP 2.2.23 server:~# smbd -V Version 3.0.14a-Debian server:~# slapd -V @(#) $OpenLDAP: slapd 2.2.23 I was using the Windows XP client login on Samba PDC but after some days, unexpectedly it didn't login anymore The client: client$ id added on LDAP and the configurations above are sets on Windows XP: Domain member: Digitally encrypt or

Hi all, I'm usigin Samba version 3.0 with OpenLDAP 2.2.23 server:~# smbd -V Version 3.0.14a-Debian serverl:~# slapd -V @(#) $OpenLDAP: slapd 2.2.23 I was using the Windows XP client loggin on Samba PDC but after some days it didn't log in anymore The client: client$ id added on LDAP and the configurations above are on Windows XP: Domain member: Digitally encrypt or sign secure

Hi, I see some wird messages in samba's logfile on Solaris 2.6. Could anyone explain me what's that? I think some hostanmes and usernames are just missing. [2002/09/25 19:17:33, 3] smbd/oplock.c:init_oplocks(1211) open_oplock_ipc: opening loopback UDP socket. [2002/09/25 19:17:33, 3] lib/util_sock.c:open_socket_in(813) bind succeeded on port 0 [2002/09/25 19:17:33, 3]

Hi all hope you can help, I have a mixed XP / 2K client deployment, and the samba server is running as a PDC. On most machines I have no problems, but on 2 2K machines and 1 XP machine I'm getting the same behaviour every time I either try to write the file or execute a file, no matter whether I log on to the domain or which userid I log on as. I'm also running debian woody 2.4.19, and

Hello, I'm still testing Samba with security=ads. Everything runs fine atm., but when I logon I'm getting this in pc's log: [2009/05/07 13:17:58, 2] lib/access.c:check_access(406) Allowed connection from (10.255.255.7) [2009/05/07 13:17:58, 2] lib/access.c:check_access(406) Allowed connection from (10.255.255.7) [2009/05/07 13:17:58, 1]

Hello all, I am trying to add W2K8 server to our domain "ns.local". This domain is working O.K. for all XP machines we have (~10), but when adding a W2K8 server, I get user/pass prompt and then after typing my* username and password I get: --------------------------- Computer Name/Domain Changes --------------------------- The following error occurred attempting to join the domain

I have a working copy of Samba 3.0.20 (installed under /usr/samba) configured as a PDC. Recently I install Samba 3.0.28 under /usr/newsamba, and copy the files lib/smb.conf (with path modifications), private/*, var/locks/* to the new locations. Following the HOWTO, the groups "Domain Admins", "Domain Users", and "Domain Guests" (with RID's 512, 513, 514 resp.) are