Re: [Samba] time sensitive error the specified network name is no longer available.
At 04:09 PM 10/29/2008 -0500, William Marshall wrote: I have a user w/ puzzling error. We have not been able to get a tcpdump or significant samba log, but I'm posting to see if anyone else has seen this. I did find some older posts that point to possible client issues. We're running samba 3.0.25b on RHEL4. The user reports: I am getting an error whenever I want to make a copy of a MS Excel file on my shared network drive: (From windows explorer) I was trying to create a copy, and when I do the paste I get the error. Cannot copy _filename_: The specified network name is no longer available. And then the file that is created is corrupt. The original file is about 240K. Now for the timing part. If she executes the copy command, and waits (count 1,2,3,4 seconds) then it seems like it works. Seems to be a common problem that no one has been able to address yet. When it does it to me, it creates a zero-length file. Repeating the operation at any time up to about 2-3 minutes delay causes winders to ask if I want to overwrite the file. If I say Yes, I get a good copy. I see it mostly when copying video files to a Samba share. One possible explanation is that WinXP tries both the low port (139 ?) and the high port (445 ?) at about the same time, and continues the transaction with which ever port answers first, leaving the other one to die. Some sort of collision results. I added a line to smb.conf: smb ports = 139 This is supposed to help if you see this in the logs: get peername failed; endpoint not connected Using port 445 or 443 (I forget which) is supposed to be better but Win95/98/ME clients don't support that, and I don't know if Win2k does, but I suspect it does. The bad news: I still get the Network name not available error from time to time. But it's better. I just make very sure not to do any file moves, I copy and delete. Sometimes I have to perform a copy or save a second time and overwrite the zero-length file. But that gets me where I'm going. - 535. [Love] What woman says to fond lover should be written on air or the swift water. --Catullus (B.C. 84?-54?) Carmina. LXX 3. --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting)WEB: http://www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Basic server role question
I have a samba 3.2.3-0.1-1882 server running on Suse SL11.0. It's out of the box, just the way YAST builds it. Pardon the extremely basic level questions here. The intent for this server is basically just file and print services. (It's defined as a BDC, I think, because I didn't do that on a previous install and I couldn't get name service (wins) to work right. Wins works great now, but I don't know if being a domain controller is the reason. ) I also want it to do DHCP and maybe DNS for a small network, but those two will come later. It works now for offering shares and printers, in my limited testing. I want to define what shares people can access based on who they log in as-- if they never get prompted for username/password until they attempt to access a resource on this Samba server, that's fine. First basic question: I get a complaint when I run testparm: Server's Role (logon server) NOT ADVISED with domain-level security So I'm wondering if my choice of security model is ill-advised, or if it's my choice of role I should be questioning. Actually, I don't remember specifying a server role. Please advise. -Tom My configuration is below. # Date: 2008-06-06 [global] workgroup = RIVENDELL printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = L: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = Yes domain master = Yes local master = Yes netbios name = ASIMOV os level = 65 passdb backend = smbpasswd:/etc/samba/smbpasswd preferred master = Yes security = domain [homes] comment = Home Directories valid users = %S, %D%w%S browseable = No read only = No inherit acls = Yes [profiles] comment = Network Profiles Service path = %H read only = No store dos attributes = Yes create mask = 0600 directory mask = 0700 [users] comment = All users path = /home read only = No inherit acls = Yes veto files = /aquota.user/groups/shares/ [groups] comment = All groups path = /home/groups read only = No inherit acls = Yes [printers] comment = All Printers path = /var/tmp printable = Yes create mask = 0600 browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 [netlogon] comment = Network Logon Service path = /var/lib/samba/netlogon write list = root - 268. [Philosophy] People can and will do things that no one could possibly believe anyone would do. For examples look at most of human history or the alt.sex.* hierarchy. --Ken Boucher on human stupidity in sci.nanotech --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting)WEB: http://www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] TCP/IP block size
At 08:11 PM 8/4/2008 -0400, Jeremy M wrote: I don't know if this is a Samba question or an OS question. I'm Or neither? How robust is your TCP/IP stack implementation? Is it possible it's reacting to response times by reducing block sizes? Is this sliding windows? Samba on Linux should do that since the TCP/IP stack on linux is pretty smart. working on an embedded project (microcontroller, limited RAM) that reads files from a FreeBSD/Samba (FreeNAS) box using TCP/IP transport on port 445. They're MP3 files so they're several MB at least. If I request 512 or 1024 bytes each time, I get 1024 bytes back from Samba every time. That's good. But, if I request more, say for example 1300 bytes, I get 1300 bytes returned for the 1st three requests, then the 4th 1300 bytes request is returned by Samba as two messages, one 196 bytes long and the other is 1104 bytes long. If it returns 1300 bytes for a few times, then reduces the block size, then I'm going to guess that the TCP/IP stack on your microcontroller is giving Samba some clue that it's having trouble keeping up. It appears that Samba is transmitting data in chunks of 4K, and if I How does it appear so? You have Wireshark on it? If Samba/Linux is sending 4k, then why did you say you're getting 512, 1024, or 1104? I'm not sure I understand your question. request an even fraction of that, such as 512 or 1024 bytes at a time, I always get that amount in the response. I wish I could request 2048 bytes, but this exceeds my ethernet controller buffer and TCP/IP specifications. Yup. 140-some bytes, maximum, without jumbo frames support on both ends. Even at that, specifications seem to vary. I have a switch that supports jumbo frames, but there's that pesky asterisk in the specs. At the bottom of the page it says 4096 bytes/frame, less overhead, maximum. Is there a way to change this? In summary, I would like Samba to always return the number of bytes I request and not split it up between two messages. I know I can combine the two response messages, but this causes performance problems for the microcontroller. I don't know if you can. You can set the no-fragment flag on transmit, but the other system (Samba) will still split up frames if it thinks it should. Perhaps there's different implementation of the driver for your NIC (in the Samba box) that behaves differently, or has more options for fine-grained control. Maybe a 10/100/1000 NIC would allow jumbo frames on 100mb. I know we had some HP NICs at one time that did, and as we were backing up servers on a separate backup VLAN, 2048 bytes packets seemed to be the way to go. Ulimately, the performance gain was pretty small. We did better by isolating the backup VLANs to their own switches. _ Get Windows Live and get whatever you need, wherever you are. Start here. http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home_082008-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba - 547. [Love] An absence, the decline of a dinner invitation, an unintentional coldness, can accomplish more than all the cosmetics and beautiful dresses in the world. --Marcel Proust (1871-1922) --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting)WEB: http://www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] TCP/IP block size
At 08:16 PM 8/4/2008 -0500, Tom Peters wrote: At 08:11 PM 8/4/2008 -0400, Jeremy M wrote: I don't know if this is a Samba question or an OS question. I'm request an even fraction of that, such as 512 or 1024 bytes at a time, I always get that amount in the response. I wish I could request 2048 bytes, but this exceeds my ethernet controller buffer and TCP/IP specifications. Yup. 140-some bytes, maximum, without jumbo frames support on both ends. Even at that, specifications seem to vary. I have a switch that Oops. Should be obvious that I meant 1415 bytes, not 140. It's 1500 minus the overhead, depending how you measure. - 442. [Humor] There's a fine line between fishing and just standing on the shore like an idiot. --Steven Wright --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting)WEB: http://www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] the specified network name no longer exists
At 12:05 PM 7/21/2008 +1000, you wrote: hi all i'm experiencing some really funny behavior on our samba server (CentOS5, Samba Version 3.0.25b-1.el5_1.4) from time to time, our xp/2000 users (our workstations are xp/2000 based) are reporting that while they try to copy a file from one location of the file server to another, they are presented with the the error the specified network name no longer exists if they retry the copy succeeds. I used to see this all the time-- still do sometimes. Was made slightly better for me by adding to smb.conf this line: smbports = 139 This makes it not try to use port 445. Without this, it tries both more or less simultaneously, then uses whichever one answers first. If you are having similar symptoms to mine, attempts to copy a large file will cause it to write a zero-length file then bark at you about the network connection no longer existing. Retry the same operation within a few minutes, and overwrite the zero-length file, and all is well, even if you are copying dozens or hundreds of files. I'm stuck with Samba 3.0.9-2.5 at the moment. -T - 798. [Conflict] If we cannot end our differences at least we can make the world safe for diversity. --John F. Kennedy --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting)WEB: http://www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba kills network.
At 10:14 AM 4/7/2007 +0200, C.Scheeder wrote: Tom Peters schrieb: By the way, I was hoping this would be significant: If I refresh my view of a Samba share on the XP box by pressing F5 or clicking View--Refresh, so that there is some recent activity on that share, and then begin the copy operation immediately, e.g. within 20 seconds, the copy operation always succeeds. This makes me beleave it's a problem of your XP-installation. Please give it a try to boot with a knoppix or another live-cd and then test if the problems are reproduceable or not. Roots [EMAIL PROTECTED] is that true for you as well? The files I am copying tend to be medium-large: 180 mb to 900 mb. But even with small files I've had it do the same thing. At 10:00 AM 4/6/2007 +0200, C.Scheeder wrote: Hi, First: you missed to tell us the version of samba you are using, and the Software/OS of the client you are trying to copy your files from. Yes, sorry, I realized after that we had not discussed versions or etc. Of course I don't know what versions Roots [EMAIL PROTECTED] but I have 3.0.9-2.3 of Samba here. I know it's pretty old. and your kernelversion is? 2.6.8-24.25 second: I never had any problems moving large files around using w98/W2k/XP boxes to and from the samba-servers i maintain (roundabout 12 machines), except when bad/dying hardware/software was involved. have you tried from another client? Yes. Similar issues result from another XP Pro box. have you updated ALL your clients drivers (not only the Nic's drivers) to the latest versions? No. Ok as you have tryend from two clients, that shouldn't be a problem, as i guess they have diffrentz Hardware. have you checked if there are corrupted packets on your network (ifconfig eth1 shows you statistics off packets on your server) It's eth0 for me. Out of 95 million packets received the errors counts are: 1 error, 7 overruns, 1 frame, 0 dropped. For 102.77 million packet sent, I have zero errors of any kind, zero collisions, txqueue length 1000. OK, that is bad. You should not get errors here with modern Hardware. I checked the servers i can lay my hands on from here, and they have no errors, nada. (one of them with over 300 million packets send and received, and 5 other with lower counts, probably caused by wrapping counters.) have you replaced any peace of hardware inbetween the server and the client? No. Well, yes, but it made no difference. I swapped my SMC 10/100/1000 switch out for a 3Com SmartStack 10/100. I did however try a crossover cable some time ago. The same results (errors) occur. Did you try and replace the NIC's in the clients and the server? I have seen strange things happen with partly damaged/dying NIC's. Even defekt onboard NIC's on brand new motherboards. (if you don't have a spare-switch, connect client and server via an crossover-cable...) has your switch updateable firmware? if yes, have you updated it to the latest version? I checked. There is no later version available for the SMC. try to boot knoppix on the client and smbmount the shares then test if then copying works. Make shure your server is the masterbrowser at any time. The os level is set to 33, which is supposed to make sure of that. SUPPOSED, i've seen XP-computers steal the Masterbrowser-role even from a samba server with os-level set to 255, took me half a Day to find the machine and punish the user for having installed tcp-ip, netbios and netware-protokoll on the machine. make shure ALL unused network connections in your clients are disabled. (like ieee1394-network, or dvb-network, unused WLAN-Connetions and what the hell modern windows versions think of devices being able to do networking) Hmmm The 1394 connection was bound to Client for Microsoft Windows, Service Advertising Protocol, File and Printer Sharing for MS Networks, and Internet protocol. I don't anticipate using the 1394 connection for anything soon, so I cleared the checkboxes for most of that. SAP is greyed-out, can't change that one. My first attempt to copy files to a samba drive failed immediately, just as before. Perhaps a therapeutic reboot is necessary. -Tom Christoph Christoph -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba - 933. [Haiku error messages] Wind catches lily / scattering petals to the wind: / segmentation fault --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting)WEB: http://www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba kills network.
By the way, I was hoping this would be significant: If I refresh my view of a Samba share on the XP box by pressing F5 or clicking View--Refresh, so that there is some recent activity on that share, and then begin the copy operation immediately, e.g. within 20 seconds, the copy operation always succeeds. Roots [EMAIL PROTECTED] is that true for you as well? The files I am copying tend to be medium-large: 180 mb to 900 mb. But even with small files I've had it do the same thing. At 10:00 AM 4/6/2007 +0200, C.Scheeder wrote: Hi, First: you missed to tell us the version of samba you are using, and the Software/OS of the client you are trying to copy your files from. Yes, sorry, I realized after that we had not discussed versions or etc. Of course I don't know what versions Roots [EMAIL PROTECTED] but I have 3.0.9-2.3 of Samba here. I know it's pretty old. second: I never had any problems moving large files around using w98/W2k/XP boxes to and from the samba-servers i maintain (roundabout 12 machines), except when bad/dying hardware/software was involved. have you tried from another client? Yes. Similar issues result from another XP Pro box. have you updated ALL your clients drivers (not only the Nic's drivers) to the latest versions? No. have you checked if there are corrupted packets on your network (ifconfig eth1 shows you statistics off packets on your server) It's eth0 for me. Out of 95 million packets received the errors counts are: 1 error, 7 overruns, 1 frame, 0 dropped. For 102.77 million packet sent, I have zero errors of any kind, zero collisions, txqueue length 1000. have you replaced any peace of hardware inbetween the server and the client? No. Well, yes, but it made no difference. I swapped my SMC 10/100/1000 switch out for a 3Com SmartStack 10/100. I did however try a crossover cable some time ago. The same results (errors) occur. (if you don't have a spare-switch, connect client and server via an crossover-cable...) has your switch updateable firmware? if yes, have you updated it to the latest version? I checked. There is no later version available for the SMC. try to boot knoppix on the client and smbmount the shares then test if then copying works. Make shure your server is the masterbrowser at any time. The os level is set to 33, which is supposed to make sure of that. make shure ALL unused network connections in your clients are disabled. (like ieee1394-network, or dvb-network, unused WLAN-Connetions and what the hell modern windows versions think of devices being able to do networking) Christoph Tom Peters schrieb: At 09:14 PM 4/5/2007 +0100, you wrote: When i try to swap files between disks on my server using samba i get errors: then windows reports The specified network name is no longer available. Sometimes the copies are fine other times files just wont copy. Hardware checks out fine. Ive even replaced the network cable between server and switch thinking that might be causing the problem. Ive included a ethereal cap of the network during one of these problems, and my samba config as attachments the errors are as follows: Apr 5 20:41:53 Ghost smbd[27010]: [2007/04/05 20:41:53, 0] lib/util_sock.c:get_peer_addr(1229) Apr 5 20:41:53 Ghost smbd[27010]: getpeername failed. Error was Transport endpoint is not connected Please Help im at a loss to what the problem is! [global] getwd cache = yes socket options = TCP_NODELAY SO_SNDBUF=65536 SO_RCVBUF=65536 IPTOS_LOWDELAY use sendfile = no lock spin time = 15 lock spin count = 30 map to guest = bad user log level = 1 security = user os level = 64 local master = Yes time server = Yes domain master = yes preferred master = yes wins support = yes domain logons = yes dos filetimes = Yes workgroup = Family netbios name = fileserver server string = Samba Server %v printcap name = cups load printers = yes printing = cups printer admin = root @adm @is log file = /var/log/samba/log.%m max log size = 50 ;hosts allow = 192.168.1.0/24 127.0.0.1 interfaces = eth1 lo bind interfaces only = yes encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd add user script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M %u wins proxy = yes dns proxy = no logon path = logon drive = U: logon script = %U.bat oplocks = no level2 oplocks = no change notify timeout = 300 lpq cache time = 30 winbind uid = 1-2 winbind gid = 1-2 winbind separator = + oplocks = no level2 oplocks = no ; deadtime = 60 wins proxy = yes lpq cache time = 30 change notify timeout
Re: [Samba] Samba kills network.
At 09:14 PM 4/5/2007 +0100, you wrote:
When i try to swap files between disks on my server using samba i get
errors: then windows reports The specified network name is no longer
available. Sometimes the copies are fine other times files just wont
copy. Hardware checks out fine. Ive even replaced the network cable
between server and switch thinking that might be causing the problem. Ive
included a ethereal cap of the network during one of these problems, and
my samba config as attachments the errors are as follows:
Apr 5 20:41:53 Ghost smbd[27010]: [2007/04/05 20:41:53, 0]
lib/util_sock.c:get_peer_addr(1229)
Apr 5 20:41:53 Ghost smbd[27010]: getpeername failed. Error was
Transport endpoint is not connected
Please Help im at a loss to what the problem is!
[global]
getwd cache = yes
socket options = TCP_NODELAY SO_SNDBUF=65536 SO_RCVBUF=65536
IPTOS_LOWDELAY
use sendfile = no
lock spin time = 15
lock spin count = 30
map to guest = bad user
log level = 1
security = user
os level = 64
local master = Yes
time server = Yes
domain master = yes
preferred master = yes
wins support = yes
domain logons = yes
dos filetimes = Yes
workgroup = Family
netbios name = fileserver
server string = Samba Server %v
printcap name = cups
load printers = yes
printing = cups
printer admin = root @adm @is
log file = /var/log/samba/log.%m
max log size = 50
;hosts allow = 192.168.1.0/24 127.0.0.1
interfaces = eth1 lo
bind interfaces only = yes
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
add user script = /usr/sbin/useradd -d /dev/null -g machines -c
'Machine Account' -s /bin/false -M %u
wins proxy = yes
dns proxy = no
logon path =
logon drive = U:
logon script = %U.bat
oplocks = no
level2 oplocks = no
change notify timeout = 300
lpq cache time = 30
winbind uid = 1-2
winbind gid = 1-2
winbind separator = +
oplocks = no
level2 oplocks = no
; deadtime = 60
wins proxy = yes
lpq cache time = 30
change notify timeout = 300
getwd cache = yes
dos filetimes = yes
domain logons = yes
obey pam restrictions = yes
unix password sync = Yes
pam password change = yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *Re*ype*new*UNIX*password*
%n\n \
*passwd:*all*authentication*tokens*updated*successfully*
add user script = /usr/sbin/useradd -s /bin/false '%u'
delete user script = /usr/sbin/userdel '%s'
add user to group script = /usr/bin/gpasswd -a '%u' '%g'
delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
set primary group script = /usr/sbin/usermod -g '%g' '%u'
add group script = /usr/sbin/groupadd %g getent group '%g'|awk
-F: '{print $3}'
delete group script = /usr/sbin/groupdel '%g'
add machine script = /usr/sbin/useradd -d /dev/null -g machines
-c 'Machine Account' -s /bin/false -M %u
[homes]
comment = Home Directories
browseable = no
writable = yes
oplocks = yes
level2 oplocks = yes
; use sendfile = yes
; preexec = echo %u, %G, %a, %m (%I)\ /tmp/.log
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
writable = no
read only = yes
guest ok = no
browseable = no
share modes = no
root preexec = /usr/bin/ntlogon -u %U -g %G -o %a -d
/var/lib/samba/netlogon/
root postexec = rm -f /var/lib/samba/netlogon/%U.bat
[www]
use sendfile = yes
comment = Web Site
path = /var/www
writeable = yes
valid users = @adm
force group = apache
force user = root
create mask = 3754
directory mask = 3754
force create mode = 3754
force directory mode = 3754
oplocks = Yes
level2 oplocks = yes
[logs]
comment = Server Log Files
path = /var/log
read only = yes
force group = root
force user = root
public = no
valid users = @adm
[etc]
comment = Server ETC Files
path = /etc
read only = yes
force group = root
force user = root
public = no
valid users = @adm
[Video's]
comment = Video's
path = /disks/sda
public = yes
only guest = yes
writable = yes
printable = no
oplocks = Yes
level2 oplocks = yes
use sendfile = yes
[Games]
comment = Games
path = /disks/hde
public = yes
only guest = yes
Re: [Samba] Samba kills network.
At 03:04 PM 4/5/2007 -0700, Jeremy Allison wrote: On Thu, Apr 05, 2007 at 04:15:33PM -0500, Tom Peters wrote: I have this problem all the time. Samba for me will cause the The specified network name no longer exists (that's how it's worded for me, not available) and copy a zero-length file to the destination drive. Reads from a Samba share are never any problem for me. If you immediately retry the operation, and immediately say Y to overwrite it, it will succeed. If you do the above for the first in a series of files to be copied to a Samba share, it will copy all the rest of them sucessfully. The other thing that gives this error away is the getpeername failed... ...transport endpoint not connected. I thought I had this fixed, but after months, it has recurred. The fix I tried was this (in smb.conf): smb ports = 139 The explanation I got was that Windows try to connect to a server over ports 443 and 139 nearly simultaneously, then use whichever one responds first. Samba replies to both, and it might be that Windows has already decided which it's going to use, and interprets the double reply as a failure. Use sendfile = no has also been suggested to me. Frankly, this is embarrassing, and has kept me from pushing Samba harder. When I ask about it, nobody seems to have a real answer. Easy enough to fix. Add : smb ports = 445 to the [global] section of your smb.conf. Pre-Windows 2000 clients won't be able to connect though. I tried that. Used 445, not 443 (oops). Did a load/unload of smbd. No change. Changed it to 139. Worked better, for a few months. Went back to old behavior, which is a lot like having no smb ports = in my conf file at all. - 844. My veal cutlet tried to beat the s**t out of my cup of coffee... the coffee just wasn't strong enough to defend himself. (Tom Waits) --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting)WEB: http://www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Disconnected network drive
At 06:30 PM 11/28/2006 -0500, Paul Abrahams wrote: I have a couple of Linux directories that are being exported via Samba running under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) Me too, only mine is SuSE 9.3 drive letter. In the My Computer list they initially show up as Disconnected Network Drive. Mine too. If I attempt to access a file within one of them, the access fails with an indication that the drive does not exist. Not mine. Sometimes they change from Disconnected network drive to Network drive upon access, sometimes they don't. But I never get errors. They are always accessible. (For example, if the drive letter is H:, doing H: from a C prompt gives that message.) However, if in Windows I click on the drive, I get to see its contents and the status changes to Network Drive. At that point the drive contents become available to my Windows applications. Put a new shortcut in your startup menu on the Winders machine. Make the command line consist of F: where F: is a drive letter of the Samba drive. After you create the shortcut, right click it again and choose properties. Select minimized instead of normal window on the shortcut tab. When you get around to it after bootup/login, close the minimized window this shortcut opens. I get this behavior on three different machines, all running Windows XP. In the Windows drive mapping, I've checked the Reconnect at Logon box, but that makes no difference. I always specify reconnect at Logon. But the username and password on the Winders machine are exactly the same as the samba username/password (I don't use a PDC) and before I made that change, I had similar problems. I'm guessing that the problem is on the Linux side since each Windows machine can access exported directories from other Windows machines without any difficulty. It's only the drives exported from Linux that have the problem. [Philosophy] Reality is that which, when you stop believing in it, doesn't go away. --Phillip K. Dick, 1928-1982 --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 3.0.21c and big wmv or mpg files
At 03:15 PM 4/1/2006 +0200, Thomas Bork wrote: Tom Peters wrote: Tell me, do you get this problem when you drag/n/drop a file into a folder on the samba share? And can you prevent this problem from occurring by the following procedure? I cannot see the problem here but heared from 2 users of 3.0.21c with this problem. Downloaded a file with 843 MB which reproducable triggered the error by one of the users - but not on my system. We are using the _same_ samba version (built by me) on the same distribution: http://www.eisfair.org/ http://www.pack-eis.de/index.php?p=samba I'm the maintainer of this samba package and therefore interested in to correct this. Click in the target window on the samba machine (this is on the XP desktop). Press F5 to refresh the view. Wait about a second. Immediately start your copy. When I do this, the errors, previously reported to the desktop and to my server log, don't occur. The user copies the file with: - right click to the local file and 'copy' - right click in the share and 'insert' This procedure is the same as drag-and-drop from WinXP point of view. In English I believe the options are 'copy' and 'paste' rather than 'copy' and 'insert' but it's does the same as drag and drop in this context. I've been told that it's a WinXP only issue, that it attempts to connect on ports 445 and 139 nearly simultaneously, and then proceeds to talk over whichever one answers first. I'm told that Win2k clients won't have this problem, and Win98 clients don't use port 445 so it doesn't arise there. How did you adjusted your clients? On tab 'WINS'/Netbios properties (all translated from german): TCP/IP properties/Default or TCP/IP properties/Enable Netbios over TCP/IP Up to this moment, they had been TCP/IP properties/Default. I have changed it to Enable NetBIOS over TCP/IP. While copying the wmv test file a have a cpu utilization of 95! percent (top) of smbd at the time, samba creates the sparse (?) file in the size needed for the test file. I don't believe this happens in my case. I am not certain. I know that when it fails, Windows clients see a 0 bytes file with the name of the destination in the target share. You have to erase or overwrite it when you try again. Maybe this is problematical on smaller systems. Samba is running here on an VMWARE on top of XP (the test client) with P4 3,2 GHz: deveis # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 3.20GHz stepping: 8 cpu MHz : 3193.393 cache size : 0 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss pni ds_cpl bogomips: 6370.09 By the user of the test file the sparse file with the correct size will be created but is complete empty... I would need to force a failure of this type and examine the size of the target file on the Linux side. WinXP says its empty and zero-length. der tom [Philosophy] I loathe people who keep dogs. They are cowards who haven't the guts to bite people themselves. --August Strindberg --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 3.0.21c and big wmv or mpg files
At 10:40 PM 3/29/2006 +0200, you wrote: Hi @all, are there any problems known with 3.0.21c and bigger video files (mpg and wmv greater than 700 MB)? Received the information that these files cannot copied from XP to Samba (W2K is okay). Error message is the well known: [2006/03/28 18:03:36, 0] lib/util_sock.c:get_peer_addr(1225)getpeername failed. Error was Transport endpoint is not connected I chased this elusive problem for a year. I'm still running 3.09-2.3 but I see it on other versions. Tell me, do you get this problem when you drag/n/drop a file into a folder on the samba share? And can you prevent this problem from occurring by the following procedure? Click in the target window on the samba machine (this is on the XP desktop). Press F5 to refresh the view. Wait about a second. Immediately start your copy. When I do this, the errors, previously reported to the desktop and to my server log, don't occur. I've been told that it's a WinXP only issue, that it attempts to connect on ports 445 and 139 nearly simultaneously, and then proceeds to talk over whichever one answers first. I'm told that Win2k clients won't have this problem, and Win98 clients don't use port 445 so it doesn't arise there. Anyone have evidence to the contrary (so far)? My thinking is that WinXP improperly responds to an attempt to open a conversation on a different port than the one Samba expects. Maybe the TCP stack on SuSE is more rigorous and respects the sequence numbers and considers a connection... ...a connection. Dunno. Need to get busy with Ethereal maybe. First thing I tried: In smb.com, add a line reading smb ports = 139 which I hoped would tell it just don't reply on port 445 at all. This did not help. Next thing I tried, rather a kludge, iptables -I INPUT 1 -p tcp --dport 445 -j DROP Hey guess what? I haven't had a single incidence of the error since. My explanation, as near as I can figure out, of what the rule does: iptables; firewall / packet filter -I INPUT 1 ; Insert into chain INPUT as rule #1 -p tcp --dport 445 ; a rule for packets whose protocol is tcp AND destination port is 445 -j DROP; if matches rule, Jump to target DROP The predefined target DROP is not another chain but actually means throw the packet away. I'm allowing port 139 through (by default) instead of 445 because I still have the odd Win98 machine laying about. That's my story, and I'm sticking to it. -Tom [Commentary] Despite of the cost of living, it remains popular. --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Transport endpoint not connected
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 it's a permanent cure yet, but in 15 minutes of testing, I can't make it fail. Usually I can. Is it true that using port 445 will exclude Win98 machines? Here's the plea for help I WAS going to send out. I'm puzzled by a persistent error that seems to be getting reported by smbd but is this a TCP/IP issue?? This is Samba 3.0.9-2.3-SUSE. I can read off any share on this machine all day/night with no issues. A large part of its reason to exist is serving up media files, and it does so without complaint, so long as you're just reading them. At random, attempts to copy files to a Samba share will fail. The failure is instantaneous. This can happen even seconds after copying a group of files to the same folder successfully. I'm typically using a drag and drop, or more precisely, copy-and-paste of the files as listed on screen, by name. Windows XP clients will report Cannot copy filename: The specified network name is no longer available. [Ok] This results in a zero-length file on the destination. An immediate retry, if you answer yes to ...exists, overwrite? always succeeds. I tried using a compare-and-copy utility that continues even if it encounters an error. It does get this error sometimes, on the first file copied, then you have to click ok but then it goes on and copies all the files, successfully. I used to have a very slow scsi raid array that was the destination of most of my file transfers. So I didn't actively pursue this issue too much. Now that I have faster SATA drives on a 3Ware card (I benchmarked them- the difference is dramatic) and the problem persists, I'm hoping someone can give me some help. Copying a number of files always succeeds if the first one succeeds, although I can sometimes make a copy of a number of files fail by attempting to start another copy to anywhere on the same share. I haven't tested the parameters of that effect yet. This appears in my messages file whenever this problem occurs: Mar 13 18:00:30 tolkien smbd[16594]: [2006/03/13 18:00:30, 0] lib/util_sock.c:get_peer_addr(1136) Mar 13 18:00:30 tolkien smbd[16594]: getpeername failed. Error was Transport endpoint is not connected Mar 13 18:00:30 tolkien smbd[16594]: [2006/03/13 18:00:30, 0] lib/util_sock.c:get_peer_addr(1136) Mar 13 18:00:30 tolkien smbd[16594]: getpeername failed. Error was Transport endpoint is not connected Mar 13 18:00:35 tolkien smbd[16594]: [2006/03/13 18:00:35, 0] lib/util_sock.c:get_peer_addr(1136) Mar 13 18:00:35 tolkien smbd[16594]: getpeername failed. Error was Transport endpoint is not connected Mar 13 18:00:35 tolkien smbd[16594]: [2006/03/13 18:00:35, 0] lib/util_sock.c:write_socket_data(430) Mar 13 18:00:35 tolkien smbd[16594]: write_socket_data: write failure. Error = Connection reset by peer Mar 13 18:00:35 tolkien smbd[16594]: [2006/03/13 18:00:35, 0] lib/util_sock.c:write_socket(455) Mar 13 18:00:35 tolkien smbd[16594]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer Mar 13 18:00:35 tolkien smbd[16594]: [2006/03/13 18:00:35, 0] lib/util_sock.c:send_smb(647) Mar 13 18:00:35 tolkien smbd[16594]: Error writing 4 bytes to client. -1. (Connection reset by peer) Someone please toss me a clue or three? Tom Contents of samba-log.xpmachineipaddress [2006/03/13 18:00:30, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 172.20.0.186 [2006/03/13 18:00:30, 2] lib/access.c:check_access(324) [2006/03/13 18:00:30, 0] lib/util_sock.c:get_peer_addr(1136) getpeername failed. Error was Transport endpoint is not connected [2006/03/13 18:00:30, 0] lib/util_sock.c:get_peer_addr(1136) getpeername failed. Error was Transport endpoint is not connected [2006/03/13 18:00:31, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 172.20.0.186 [2006/03/13 18:00:31, 2] lib/access.c:check_access(324) Allowed connection from 172.20.0.186 (172.20.0.186) [2006/03/13 18:00:31, 2] smbd/reply.c:reply_special(235) netbios connect: name1=TOLKIEN name2=ELROND [2006/03/13 18:00:31, 2] smbd/reply.c:reply_special(242) netbios connect: local=tolkien remote=elrond, name type = 0 [2006/03/13 18:00:35, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 0.0.0.0 Allowed connection from 0.0.0.0 (0.0.0.0) [2006/03/13 18:00:35, 2] smbd/reply.c:reply_special(235) netbios connect: name1=TOLKIEN name2=ELROND [2006/03/13 18:00:35, 2] smbd/reply.c:reply_special(242) netbios connect: local=tolkien remote=elrond, name type = 0 Contents of samba-log.elrond [2006/03/13 18:00:01, 2]
Re: [Samba] Sharing a Secondary Hard Drive
I installed a second hard drive on my Samba server box with the hopes of creating a share for the rest of my home network. It doesn't seem like Samba is able to read the drive for some reason, however. The new drive is mounted on /media/public. When I create a share directly to the drive and try to connect through the smbclient, I get an NT_STATUS_BAD_NETWORK_NAME error. Moving the share up a level to /media allows smbclient to connect, but the public folder does not even appear and trying to cd into it returns an NT_STATUS_ACCESS_DENIED message. The drive itself seems fine as I'm able to write to it using any of my accounts directly and I can ftp and scp into it, so I am completely stumped. Does any one else have any experience with this or know what may be the cause? I'm running Fedora Core 4 by the way, if that helps. I never have problems sharing drives like this, except when I forget to change the default permissions on the directory I'm sharing. Try chmod 777 /media and but first do something similar to the root of the drive itself. If you just set this up and created the share, most likely the drive or mount point was created with default permissions, which won't be r/w to the world. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Sharing a Secondary Hard Drive
At 03:10 PM 2/3/2006 +, Joe Cipale wrote: Justin McCullough wrote: I just recently installed a second hard drive in my Samba server with the hopes of sharing it with the rest of my home network. It seems like Samba can not get the correct permissions to the drive, however. I have the drive mounted under /media/public, and when I try to map a share directly to it and open the share with a client, I get an NT_STATUS_BAD_NETWORK_NAME error. When I map the share to /media and try the client again, I can see the cdrom folder, but not public. I have also tried scp and ftp using /media/public, and they both work fine, so it doesn't seem like a common case of poor permission settings. Has anyone else ever experienced this or know of a possible cause? I'm running Fedora Core 4 if that helps. Thanks in advance, Justin McCullough Have you exported the new drive under NFS yet? Done what now? Under Samba? To access it from an NT box?? I never have done any exporting. Just declare it a share in my samba conf file and -- oh yeah! You have to restart the daemons! rcsmb restart (or reload? never can remember) rcnmb restart Silly thing won't reload the conf file until you do that. Joe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba [Warfare] Tuez-les tous; Dieu reconnai^tra les siens. (More literally, this is Kill them all; God will recognize his own.) ? Amalric Arnaud, during the seige of Be'ziers (1209 AD)? --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] firewall
At 06:31 PM 11/25/2005 -0300, contacto_AGS wrote: It work's OK but. When I installed a wireless acces point Linksys it does not work. I disabled the firewall in the acces point but with no result. Can anybody help me??? Many so-called wireless access points (WAP) are in reality a router with a wireless access point attached internally. You haven't given much information here so it's very hard to help you. It doesn't work is not enough. Does it break your whole network? Or is it only equipment connected to the WAP that doesn't work? Or is it only wireless gear attached to the WAP that fails to gain connectivity? What model number Linksys WAP have you got there? Explain what your network looks like too, what's connected to what and using what ports. There's no way to tell from your message if it's a router/WAP or not. Most likely, it is. If so, everything connected to it is on a separate IP subnet from whatever is on its WAN port. Some of them don't care if the subnets are numbered the same: You can have 192.168.0.x on both sides, and they will be separate subnets, and the firmware is too dumb to object. Of course, routing between them is totally screwed up and confused. If you have a true WAP, without a router attached, or with routing turned off, then there's some other problem, like WEP key mismatch or configuration issues. Supply more info. [Government]Foreign aid might be defined as a transfer from poor people in rich countries to rich people in poor countries.--Douglas Casey, Classmate of W.J.Clinton at Georgetown U. (1992) --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Backup Tape
At 01:38 PM 11/16/2005 +0100, you wrote: Denis Vlasenko schrieb: On Wednesday 16 November 2005 12:34, Bruno Guerreiro wrote: Hi, not sure if this fits you, but have you tried Arkeia? http://www.arkeia.com/products/asb/ They have a free version for users with less than 50GB to backup. Best Regards, Bruno Guerreiro P.S. There will always be tar... ;-) Yes. At today's prices of hard disk space, I do not understand why one may need a specialized backup software. Just tar it, then nice -n 20 bzip2 it. 7zip / p7zip / 7za compresses even better and faster than bzip2. a couple of tapes cost nearly as much as a hard disk... Um, you can take it off-site and lock it in a safe deposit box? [Computing] LOAD EMACS,8,1 [EMAIL PROTECTED] (Sven C. Dack) Bei ihm selbst gesehen. --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Op-lock error
Samba 3.0.9-2.3 on Suse 9.2 I'm still getting errors copying to my samba box: Often the first attempt to copy to it fails seemingly before it's copied anything. When this happens, there is a zero-length file created with the right name. If I retry the copy immediately and reply Yes to overwrite the zero-length file, it usually proceeds without problems. Many times the copy just goes fine with no error. The error dialog that pops up is always the same: Specified network name no longer available. This may be new: This is the first time I've seen this in the messages file: Apr 14 16:33:35 tolkien smbd[26853]: oplock_break: end of file from client Apr 14 16:33:35 tolkien smbd[26853]: oplock_break failed for file TV/Odyssey5/Odyssey 5-1x16-Vanishing.Point.avi (dev = fd00, inode = 644, file_id = 7). Apr 14 16:33:35 tolkien smbd[26853]: [2005/04/14 16:33:35, 0] smbd/oplock.c:oplock_break(923) Apr 14 16:33:35 tolkien smbd[26853]: oplock_break: client failure in break - shutting down this smbd. Apr 14 16:34:07 tolkien smbd[26857]: [2005/04/14 16:34:07, 0] smbd/oplock.c:request_oplock_break(1055) Apr 14 16:34:07 tolkien smbd[26857]: request_oplock_break: no response received to oplock break request to pid 26853 on port 32883 for dev = fd00, inode = 644, file_id = 7 No, I take it back, there was a similar occurrence on April 2 copying a large file. I had oplocks=off in my smb.conf and commented that statement out in an attempt to wring a little more performance out of this dog. Do I need to turn oplocks off? Are they on by default? Is the global section the right place for the oplocks option? [Love] Love is like linen - often changed, the sweeter. --Phineas Fletcher (1584-1650) Sicelides III.v --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Domain master vs. workgroup master?? (messages about domain master browser)
Can anyone tell me what to do about the messages I'm getting, or should I ignore them? I think my SuSE 9.2 box is configured to expect a doman, and there isn't one, just a workgroup. Most things seem to be working ok, except for the messages: tolkien:/var/log # tail messages Apr 1 00:43:05 tolkien nmbd[3962]: Unable to sync browse lists in this workgroup. Apr 1 00:56:28 tolkien -- MARK -- Apr 1 00:58:13 tolkien nmbd[3962]: [2005/04/01 00:58:13, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353) Apr 1 00:58:13 tolkien nmbd[3962]: find_domain_master_name_query_fail: Apr 1 00:58:13 tolkien nmbd[3962]: Unable to find the Domain Master Browser name RIVENDELL1b for the workgroup RIVENDELL. Apr 1 00:58:13 tolkien nmbd[3962]: Unable to sync browse lists in this workgroup. Tolkien is the should be the Wins server. configuration: # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE # Date: 2004-10-05 [global] workgroup = rivendell printcap cache time = 750 cups options = raw printer admin = @ntadmin, root, administrator username map = /etc/samba/smbusers map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain master = no ldap idmap suffix = ou=Idmap ldap machine suffix = ou=Computers os level = 65 preferred master = yes ldap suffix = dc=example,dc=com log file = /var/log/samba/samba-log.%m log level = 2 max log size = 2000 hosts allow = 172.16.0.5/24 localhost # greater file safety, reduced performance, oplocks off # oplocks = off wins support = yes restrict anonymous = no max protocol = NT ldap ssl = No server signing = Auto # Gary Nutbeam suggests client use spnego = no client use spnego = no [homes] comment = Home Directories valid users = %S browseable = no read only = no inherit acls = yes [profiles] comment = Network Profiles Service path = /archive store dos attributes = yes create mask = 0600 directory mask = 0700 [users] comment = All users path = /home/ inherit acls = yes veto files = /aquota.user/groups/shares/ [groups] comment = All groups path = /home/groups read only = no inherit acls = yes [pdf] comment = PDF creator path = /var/tmp printable = yes print command = /usr/bin/smbprngenpdf -J '%J' -c %c -s %s -u '%u' -z %z create mask = 0600 [printers] comment = All Printers path = /var/tmp printable = yes create mask = 0600 browseable = no [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 [archive] comment = archived files path = /archive/ read only = no case sensitive = no msdfs proxy = no [movies] comment = movies-multimedia path = /movies/ read only = no case sensitive = no msdfs proxy = no write cache size = 393216 # Gary Nutbeam suggests use sendfile = no use sendfile = no [Philosophy] As long as war is regarded as wicked, it will always have its fascination. When it is looked upon as vulgar, it will cease to be popular. --Oscar Wilde --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] HELP Gethostbyaddr failed
I too have posted a message with this error in the logs but no one has addressed the issue. The subject of my message was: Copy to 3.0.9-2.3-SUSE dies after 1.2 gb copied Only in my case it occurs with 3.0.9 (I have not considered an upgrade to 3.0.11 yet). Does no one have a suggestion for mitigating this issue? Here is a section of my logfile: [2005/03/09 13:52:04, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 172.20.0.186 [2005/03/09 13:52:04, 2] lib/access.c:check_access(324) Allowed connection from 172.20.0.186 (172.20.0.186) [2005/03/09 13:52:04, 2] smbd/reply.c:reply_special(235) netbios connect: name1=TOLKIEN name2=ELROND [2005/03/09 13:52:04, 2] smbd/reply.c:reply_special(242) netbios connect: local=tolkien remote=elrond, name type = 0 [2005/03/09 14:23:12, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 172.20.0.186 I can only copy 1.2 to 1.4 gb of data to a share before a WinXP or Win2k client says that the network name is no longer available. But it is a transient condition-- if I try again, it will copy another gig to gig-and-a-half before failing again. At 01:30 PM 3/10/2005 -0700, RYAN vAN GINNEKEN wrote: Thank you everyone on this list i have gained access to the shared drive again. Still have errors in the logs that worry me. Also the server seems very slow to connect the first time a machine logs on and unresponsive to open files. I will start a new thread for this later when i have done some home work of my own as the documentation for samba is very good. Thank you crisis solved now i just need to some research on how beef up preformace a little. RYAN vAN GINNEKEN wrote: I did a make deinstall and a reinstall to upgrade samba from 3.0.9 to 3.0.11 last night at the office i work at and now i get this in the logs. I am sure this has been asswered 100 time on this list but no one can connect to the shared drives. This leave everyone point very angry fingers at me so please help here is the output of the logs. [2005/03/10 12:18:20, 1] lib/util_sock.c:get_peer_name(1109) Gethostbyaddr failed for 192.168.0.5 [2005/03/10 12:18:20, 0] lib/access.c:check_access(328) Denied connection from 192.168.0.5 (192.168.0.5) [2005/03/10 12:18:20, 1] smbd/process.c:process_smb(1084) Connection denied from 192.168.0.5 [2005/03/10 12:18:25, 1] lib/util_sock.c:get_peer_name(1109) Gethostbyaddr failed for 192.168.0.5 [2005/03/10 12:18:25, 0] lib/access.c:check_access(328) Denied connection from 192.168.0.5 (192.168.0.5) [2005/03/10 12:18:25, 1] smbd/process.c:process_smb(1084) Connection denied from 192.168.0.5 [Humor] Did Washington just flash a quarter for his ID? --Steven Wright --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, Cisco Certified CCNA -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Copy to 3.0.9-2.3-SUSE dies after 1.2 gb copied
I have Samba 3.0.9 on SuSE 9.2 on a P-III-500 with only 352mb of RAM. The share I'm copying to is on a SCSI RAID array handled by a Compaq Smart-2/P RAID Controller (rev 04) as identified by lspci. The RAID is all LVM and the share is ReiserFS-- maybe not the best choice for something which is so slow to write to. Anyhow, the problem is that when I copy to the share movies it will do about 1.2 to 1.4 gb and die-- my windows XP client (either one of them) reports The specified network name is no longer available and the only choice is to click OK. If I use a drag'n'drop copy, I'm all done. If I use a slightly smarter tool, one that apparently retries, I click ok and the copy takes off again, apparently none the worse. If I give up the first time it fails, the files it did manage to copy were between 133,122kb and 344,332kb in size. I was advised to try some smb.conf changes. In the global section, I added client use spnego = no. In the section for the movies share, I added use sendfile = no. Niether change seemed to make any difference. I also added write cache size = 262144 in that share. Also little help that I can tell-- maybe a little better. I'm slightly confused that I get two log files for the same machine, both seemingly updated concurrently, one called samba-log.172.20.0.186 and one called samba-log.elrond The one named for the machine name doesn't have any errors or warnings-- just file opens and closes. The one with the IP address has errors.This fragment is pretty representative: [2005/03/09 13:52:04, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 172.20.0.186 [2005/03/09 13:52:04, 2] lib/access.c:check_access(324) Allowed connection from 172.20.0.186 (172.20.0.186) [2005/03/09 13:52:04, 2] smbd/reply.c:reply_special(235) netbios connect: name1=TOLKIEN name2=ELROND [2005/03/09 13:52:04, 2] smbd/reply.c:reply_special(242) netbios connect: local=tolkien remote=elrond, name type = 0 [2005/03/09 14:23:12, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 172.20.0.186 [2005/03/09 14:23:12, 2] lib/access.c:check_access(324) Allowed connection from 172.20.0.186 (172.20.0.186) [2005/03/09 14:23:12, 2] smbd/reply.c:reply_special(235) netbios connect: name1=TOLKIEN name2=ELROND [2005/03/09 14:23:12, 2] smbd/reply.c:reply_special(242) netbios connect: local=tolkien remote=elrond, name type = 0 [2005/03/09 14:56:38, 1] lib/util_sock.c:get_peer_name(1095) Gethostbyaddr failed for 172.20.0.186 I also have stuff in my messages log, specifically, I see this every 15 minutes: Mar 9 16:21:08 tolkien nmbd[5713]: [2005/03/09 16:21:08, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353) Mar 9 16:21:08 tolkien nmbd[5713]: find_domain_master_name_query_fail: Mar 9 16:21:08 tolkien nmbd[5713]: Unable to find the Domain Master Browser name RIVENDELL1b for the workgroup RIVENDELL. Mar 9 16:21:08 tolkien nmbd[5713]: Unable to sync browse lists in this workgroup. Any clue what tuning I need to be doing here? I'm pretty new to Linux and Samba and need a clue. TIA, Tom [Praise] The only way to escape the personal corruption of praise is to go on working. --Albert Einstein --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, Cisco Certified CCNA -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Basic Samba functionality under SuSE 9.2
I'm trying to get Samba 3.0.9-2.3 to work under Suse 9.2. This my very first Linux install and I'm a little at sea here. There are so many things that could be wrong I don't know where to start. The Windows machine I'm using as a client has TCP/IP, file/printer sharing, and Client for MS networks. He can't see the linux machine's (Tolkien) shares, but he can ping him. This might be a name services issue because issuing a net command at the windows box to enumerate the shares (I think that's net view) of the form NET VIEW \\TOLKIEN results in a timeout and error, but NET VIEW \\172.20.0.5 results in a correct list of the shares I've configured on the box! C:\WINDOWSnet view \\172.20.0.5 Shared resources at \\172.20.0.5 Samba 3.0.9-2.3-SUSE Share name Type Used as Comment --- archive Diskarchived files (etc) I know the IP addresses look odd, I won't go into the reasons using a class B but that's worked properly for years, so that's not the issue. Layer 2 connectivity is good. I'm confused about the firewall on SuSE; it's enabled and maybe it shouldn't be. All boxes on this little network are on a switch which goes to a router, thence to my DSL modem. I'm not using the SuSE box as a gateway, it's just on another switch port like the Windows boxes. The firewall has the same interface defined as the inside port and the outside port. But the YAST GUI for configuring Samba has a checkbox for opening all appropriate firewall ports, and I did that. I went back to check and it's still checked. For grins, I portscanned tolkien. TCP ports open are: 21, 22, 25, 110, 139, 445. UDP ports: None. I tried this: net use k: \\172.20.0.5\archive It works! Well, almost. It prompts for username and password, and username and pw I use to login at the linux box doesn't work. root with his password works. I need to get some permissions issues ironed out later. -Tom [Philosophy] Man's loneliness is but his fear of life. --Eugene O'neil --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, Cisco Certified CCNA -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Basic Samba functionality under SuSE 9.2
At 08:00 PM 2/8/2005 +, you wrote: On Tuesday 08 February 2005 11:55 am, Tom Peters wrote: I'm trying to get Samba 3.0.9-2.3 to work under Suse 9.2. This my very first Linux install and I'm a little at sea here. There are so many things that could be wrong I don't know where to start. The Windows machine I'm using as a client has TCP/IP, file/printer sharing, and Client for MS networks. He can't see the linux machine's (Tolkien) shares, but he can ping him. This might be a name services issue because issuing a net command at the windows box to enumerate the shares (I think that's net view) of the form NET VIEW \\TOLKIEN results in a timeout and error, but NET VIEW \\172.20.0.5 results in a correct list of the shares I've configured on the box! C:\WINDOWSnet view \\172.20.0.5 Shared resources at \\172.20.0.5 Samba 3.0.9-2.3-SUSE Share name Type Used as Comment --- archive Diskarchived files I'm confused about the firewall on SuSE; it's enabled and maybe it shouldn't be. All boxes on this little network are on a switch which goes to a router, thence to my DSL modem. I'm not using the SuSE box as a gateway, it's just on another switch port like the Windows boxes. The firewall has the same interface defined as the inside port and the outside port. But the YAST GUI for configuring Samba has a checkbox for opening all appropriate firewall ports, and I did that. I went back to check and it's still checked. For grins, I portscanned tolkien. TCP ports open are: 21, 22, 25, 110, 139, 445. UDP ports: None. I tried this: net use k: \\172.20.0.5\archive It works! Well, almost. It prompts for username and password, and username and pw I use to login at the linux box doesn't work. root with his password works. I need to get some permissions issues ironed out later. You need to start nmbd on the Linux box. Make sure that it is not a local, domain, or preferred master, and that the OS level is low (5 or so). Misty Ok, thanks for that info. A few questions, remembering that this is my first Linux box: 1. Doesn't this seem to imply that nmbd is running already? tolkien:~ # ps -ef|grep nmbd root 4036 1 0 10:35 ?00:00:00 /usr/sbin/nmbd -D -s /etc/samba/ 2. There is a config step in YAST setup of Samba that asks, in a dialog called Base Settings, for Workgroup or Domain Name and Domain Controller. Under WG or DN I have Rivendell, which is the name of the workgroup that all the WIndows boxes use to talk to each other. It's not further qualified, it's just the one lowercase word. Under Domain controller, it's a pulldown, and the two choices are: Primary (PDC) and No DC and I picked Primary (PDC). Is that a bad choice? 3. I don't see where to set OS level or understand what you mean by that. You don't mean runlevel, I think. You can live to be a hundred if you give up all the things that make you want to live to be a hundred. -- Woody Allen --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, Cisco Certified CCNA -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba (old) and shared printers on MS Win 2003 SBS
This might be a rube question; if so I apologize in advance. Someone asked me to help and I don't have much info, but I have a limited window and have to be forearmed with as much information as possible before I set foot in the door. The guy that asked for help runs a Red Hat 6.2 box with the version of Samba that came with RH 6.2. I asked him what version of Samba it was. He didn't know. He's going to check Monday. He has this uneasy relationship with the IT people at the place. His apps on the RH box run a main mission function, but the windows boxes do everything else. Last week the IT folks decided they were going to sweep out all the Win98 and NT boxen and replace all the workstations with XP Pro and all the server(s) with Win2003 Small Biz. Prior to that, his Linux apps printed to shared printers connected to NT and maybe even Win98 workstations with ease. Now his stuff can't reach any shared printers. My first thought was that old versions of Samba don't know about Active Directory, but I don't know 1. if that's true or 2. if the presence of Win2003 server SBS necessarily implies AD. My second thought was that the arrogant twits just didn't bother to give his box required permissions to use the shared printers. Who'd design a business network with printers on the workstations anyhow? Whatever, any ideas where to begin? Can someone tell me how recent a version of Samba he could upgrade to, given that he's stuck with the kernel he's using now because of his apps? TIA, Tom [Computing] Minsky and I require every graduate student to take an oath at the grave of E.E. Doc Smith before he can receive a PhD in AI. --John McCarthy, Computer Science Department, Stanford, CA 94305 --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove nospam) N9QQB (amateur radio) HEY YOU (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2 N by 88° 6' 28.9 W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, Cisco Certified CCNA -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
