That's a pretty old version of Samba. There may be some bugs giving you
fits, but some of the veterans here may know more.
Other than the errors you are seeing in your Samba logs, what behavior
are you seeing on your Windows box? Are you pushing from the Windows box
or pulling from the Samba server?
Will Holmes wrote:
Aaron,
I put in a server string with the same name as the hostname.
I commented out the port 139 line in the smb.conf file.
I restarted smb and winbind and rejoined the Domain.
I verified that the server was joined successfully.
I tried the copy again and the same issue.
I am running Suse Linux Ent Server 9 for IBM Power.
Samba version is 3.0.4-SUSE
Here is my Krb5.conf file
I have replaced some server and domain names for security purposes.
[libdefaults]
# default_realm = MY.REALM
clockskew = 300
default_realm = myrealm
[realms]
XXXX.XXX.COM = {
kdc = myserver
default_domain = XXX.XXX.COM
kpasswd_server = myservername
}
XXX.COM = {
kdc = myservername
default_domain = mydomainname
kpasswd_server = myservername
}
# MY.REALM = {
# kdc = MY.COMPUTER
# admin_server = MY.COMPUTER
# kpasswd_server = MY.COMPUTER
# }
# OTHER.REALM = {
# kdc = OTHER.COMPUTER
# }
[domain_realm]
.XXX.COM = XXX.COM
.XXX.XXX.COM = XXX.XXX.COM
# .my.domain = MY.REALM
[logging]
default = SYSLOG:NOTICE:DAEMON
kdc = FILE:/var/log/kdc.log
kadmind = FILE:/var/log/kadmind.log
[appdefaults]
pam = {
ticket_lifetime = 1d
renew_lifetime = 1d
forwardable = true
proxiable = false
retain_after_close = false
minimum_uid = 0
debug = false
}
Thanks!
Will
-----Original Message-----
From: Aaron Kincer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 30, 2007 8:47 AM
To: Will Holmes
Cc: samba@lists.samba.org
Subject: Re: FW: [Samba] Help Please! - Copying files from Windows to Samba
share loses connection
I'm not sure that it's a problem, I just know that when you do a net ads
join, that value is what tells Active Directory your computer name. At
least that is how I've seen Samba behave. I don't know what happens if
you don't have that set. I'm sure someone here knows.
I am a bit confuse by your specification of port 139. Comment out that
line and see if you have better luck. For giggles, set your server
string to the same as your hostname and rejoin the domain. Also, have
you taken other steps to configure AD such as editing your krb5.conf
file? What OS and Samba version are you running?
Will Holmes wrote:
Aaron,
Yes, I left the server string out intentionally because of how the
mapped
drive description showed in Windows. Could this be causing my problem? I
was able to join this server to the domain and I could retrieive a list of
users using the winfo command.
Thanks!
Will
-----Original Message-----
From: Aaron Kincer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 12:21 PM
To: Will Holmes
Cc: samba@lists.samba.org
Subject: Re: [Samba] Help Please! - Copying files from Windows to Samba
share loses connection
I see you don't have the server string set.
Have you tried to join this server to the domain with a net ads join
command?
Will Holmes wrote:
Hello all,
I haven't been able to solve an issue I am having when copying over
data
from a Windows box to a Samba share. I have found others with the same
issue and I have made some configuration changes to try and solve the
issue
but the issue is still lingering. I want to migrate off my old Windows
box
but until I solve this issue I am I cannot move forward. Please let me
know
if you need any further info. Thanks!!!
Here is the two lines I have added to my smb.conf file. Niether change
did
the trick.
client schannel = no
smb ports = 139
************************************************************
Here is my smb.config file:
************************************************************
# smb.conf is the main Samba configuration file. You find a full
commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE
# Date: 2004-07-01
[global]
workgroup = FMIC
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
printer admin = @ntadmin, root, administrator
username map = /etc/samba/smbusers
map to guest = Bad User
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
security = ADS
encrypt passwords = yes
domain logons = no
ldap idmap suffix = ou=Idmap
ldap machine suffix = ou=Computers
local master = yes
wins server =
wins support = no
netbios name = FMICLINUX
add machine script =
preferred master = auto
ldap suffix = dc=example,dc=com
realm = FMIC.FMIC.COM
idmap uid = 15000-20000
idmap gid = 15000-20000
server string =
allow trusted domains = yes
password server = *
nt acl support = yes
map acl inherit = yes
winbind use default domain = yes
client schannel = no
smb ports = 139
************************************************************
System Log errors:
************************************************************
May 23 12:59:00 fmiclinux /USR/SBIN/CRON[2745]: (root) CMD ( rm -f
/var/spool/cron/lastrun/cron.hourly) │
│May 23 13:59:00 fmiclinux /USR/SBIN/CRON[2755]: (root) CMD ( rm -f
/var/spool/cron/lastrun/cron.hourly) │
│May 25 09:00:03 fmiclinux smbd[3241]: [2007/05/25 09:00:03, 0]
lib/util_sock.c:get_peer_addr(978) │
│May 25 09:00:03 fmiclinux smbd[3242]: [2007/05/25 09:00:03, 0]
lib/util_sock.c:get_peer_addr(978) │
│May 25 09:00:03 fmiclinux sshd[2983]: fatal: Timeout before
authentication for ::ffff:10.0.0.158 │
│May 25 09:00:03 fmiclinux smbd[2263]: Error writing 51 bytes to
client.
-1. (Broken pipe) │
│May 25 09:00:03 fmiclinux smbd[3241]: getpeername failed. Error was
Transport endpoint is not connected │
│May 25 09:00:03 fmiclinux smbd[3240]: [2007/05/25 09:00:03, 0]
lib/util_sock.c:write_socket_data(413) │
│May 25 09:00:03 fmiclinux smbd[3242]: getpeername failed. Error was
Transport endpoint is not connected │
│May 25 09:00:03 fmiclinux smbd[3241]: [2007/05/25 09:00:03, 0]
lib/util_sock.c:get_peer_addr(978) │
│May 25 09:00:03 fmiclinux smbd[3241]: getpeername failed. Error was
Transport endpoint is not connected │
│May 25 09:00:03 fmiclinux smbd[3241]: [2007/05/25 09:00:03, 0]
lib/util_sock.c:write_socket_data(413) │
│May 25 09:00:03 fmiclinux smbd[3240]: write_socket_data: write
failure.
Error = Connection reset by peer │
│May 25 09:00:04 fmiclinux smbd[3240]: [2007/05/25 09:00:04, 0]
lib/util_sock.c:write_socket(438) │
│May 25 09:00:04 fmiclinux smbd[3240]: write_socket: Error writing 4
bytes to socket 5: ERRNO = Connection res│
│~et by peer
│
│May 25 09:00:04 fmiclinux smbd[3240]: [2007/05/25 09:00:04, 0]
lib/util_sock.c:send_smb(630) │
│May 25 09:00:03 fmiclinux smbd[3242]: [2007/05/25 09:00:03, 0]
lib/util_sock.c:get_peer_addr(978) │
│May 25 09:00:04 fmiclinux smbd[3242]: getpeername failed. Error was
Transport endpoint is not connected │
│May 25 09:00:04 fmiclinux smbd[3242]: [2007/05/25 09:00:04, 0]
lib/util_sock.c:write_socket_data(413) │
│May 25 09:00:04 fmiclinux smbd[3242]: write_socket_data: write
failure.
Error = Connection reset by peer │
│May 25 09:00:04 fmiclinux smbd[3242]: [2007/05/25 09:00:04, 0]
lib/util_sock.c:write_socket(438) │
│May 25 09:00:04 fmiclinux smbd[3242]: write_socket: Error writing 4
bytes to socket 21: ERRNO = Connection re│
Thanks in advance!!
Will Holmes
Programmer Analyst
Fremont Insurance Company
Ph: 231-924-0302 Ext. 145
E-Mail: [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
