similar to: smbmounts hang around after windows client disconnects

Hey, I have slow access when I first open shares. If I reboot my XP box and then go to access a share, it takes a good 10 seconds for files to come up, even after I've typed in my username and password. Once accessed it runs fine and is fast. But, if I don't access it for 30 minutes, when I access it again it sits for like 10 good seconds before it does anything. This is very annoying.

I have a samba version 3.024 server joined to a ADS as a "Workstation or server" acting as a file/print server. It is a Debian 4.0 amd64 up to date with stable. ftp works just fine so not network, must be samba config. vary slow file transfer when copying file from one computer but copy from two or more at the same time speed is 10 times faster. You will be copying a 600MG file with one

Hello, Last week I have detected with Zabbix that a member of my Samba domain had been downloading at a rate of around 8 Mbps for two days and a half. When asking the person to whom belonged the machine, he didn't know he was downloading anything but he said he had observed his machine had slowed down since then. I took a tcpdump of the traffic before terminating his session on Windows

I''m having a silly little problem with migrations.  All I''m trying to do is to add an SSN column to my Employees table.  I generated a migration which looks like: class AddSsn < ActiveRecord::Migration def self.up     add_column :employees, :ssn, :string end def self.down     remove_column :employees, :ssn   end end When I run this, however, I get: >rake

Would really appreciate it if someone could tell me why this is happening: I override ssn method of AR class so I can encrypt/decrypt to/from the db: class Person < ActiveRecord::Base def ssn=(value) write_attribute(:borrower_ssn, Crypto.encrypt(self.encryption_key, value)) write_attribute(:borrower_ssn_final_four, value[5,4]) end def ssn # this begin - rescue can be

Hey Guys and Gals, I'm wondering if the quotas.c file is supposed to fix the problem where a Linux x86 system running with the quota software causes corrupt files to be written by Windows clients. I compiled it in and it didn't seem to make a difference for the following problem. In other words, if I enable quotas on my RH6.2 / 2.2.16-22 kernel box and then write a file via Samba/Windows

Before wasting a lot of time going at this in the wrong list, I would like to confirm whether my thinking is on or off base with respect to source and destination ports. Samba is being blocked by fw2loc even though I have accept rules set up. I believe I can explain why, but I could be wrong. I think that for some reason, samba is sourcing stuff on the commonly used port 137, but trying to send

for months, we keep fighting issues with smbd (now at released 2.2.6), config is with spoolss, domain logon, and the client in question is an NT4 machine. server is a i386/linux 2.2.19 For a very long time, we thought it was related to oplocks, but now after having them disabled, it still is there. Level 3 Log is as follows: [2002/10/22 17:08:18, 3] smbd/ipc.c:reply_trans(480) trans

Hi list, I am encountering a problem in connecting a Windows 2003 to a Samba 3.0.21b server. The Samba server is configured to have a security = share option, so that no password is needed. I can connect to the server by typing "net use z: \\192.168.51.1\data", and it is successful. However, if I try to do "dir z:", no file found! Same behaviour are found in Windows

Hello, I would like to ask you if its possible to run Samba on an other port than 137-139? I tried once to edit the "/etc/services" File. The lines: ... netbios-ns 137/tcp netbios-ns 137/udp netbios-dgm 138/tcp netbios-dgm 138/udp netbios-ssn 139/tcp netbios-ssn 139/udp ... I changed it to: ... netbios-ns 6998/tcp netbios-ns 6998/udp netbios-dgm 6999/tcp netbios-dgm 6999/udp

I'm currently running version 2.0.7 of samba(CIFS9000). I have HPUX 11.x installed on the samba server. When I try to run this from inetd it doesn't work. I can run a startup script that runs the smbd as a daemon and it works fine. But if I try to run it from inetd it won't start. The previous version of Samba 1.9.18p10 that I had on this server worked fine. Is this a bug in

Hi team, one small query, Is netbios-ns,netbios-dgm and netbios-ssn ports 137,138,139 need to be open to communicate with windows from linux. what was the use of these services??

I run samba 2.2.8a on my openbsd 3.4 box, installed from a package. All i need is the ability to mount disks form winxp boxes so i only run smbd, at 139/tcp. I tried scanning the box with nessus, and it came up with some results that got me curious. Since i dont know very much about the smb protocol I thought i should ask here. Have searched the archives but found only old posts, concering

My WinXP clients are able to map a network drive on my samba server. However, it takes 30 seconds to do so, and accessing the contents of the shared drive is also quite slow. Linux (smbclient) and Windows 2000 clients are able to map the share instantly, and access files without delay. I am using Linux 2.4.5, with samba 2.2.3a compiled from source on the server. The delay is consistent at 30

I began with Samba 1.9.18.p10. on SunOs 5.6. I try backup PC(Windows95) with this: smbclient \\\\pcbig\\test .. .. smb:\> recurse smb:\> directory recursion is now on smb:\> tar c /dev/rmt/0 .... Until it is OK. But restore has error: smb:\> tar x /dev/rmt/0 smb:\> restore tar file \test1.txt of size 70 bytes smb:\> Updating creation date on \testfolder1\ smb:\> ERRDOS - 50

Sorry if this is such a basic question but I couldn't find anything about this in the FAQs/HowTos/Digest. I've compiled samba-1.9.18p3 on SunOS4.1.3_U1. When I tried to run smbd via inetd.conf (SIGHUP), I always get the following on the console. inetd[590]: netbios-ssn/tcp: unknown service I've edited the /etc/services to add: netbios-ssn 139/tcp And the /etc/inetd/conf with

Hello, I already setup a samba server as PDC for windows client to logon and working fine now with the following config: - redhat 7.3 - samba 2.2.7a Then I try to access the samba share from Redhat 8, I can use smbclient to access the share without problem but I can't access the share with "KDE's Konqueror" (smb://NetbiosName/), it can show all shares, when I double one of

Over the past 2 days, my smbd processes are multiplying worse than rabbits. At least with rabbits it's easy to tell why you wind up with so many... Here's the setup: Samba version 3.2.8-0.24 installed via rpm on a FC6 box with 2 nics, both on the same subnet. The samba server acts as a PDC in a mixed environment but mostly windows pc's running xp. It is used mostly for file

Having trouble with Samba. The config file passes the test (testparm) The Server seems to be upa and running fine (smbclient -L localhost) But can't seem to connect to it from other computers (running 2000 or 98) They were able to connect once though. What should be listed on port 139 in services. We have : netbios-ssn Does this sound right? Appreciate any help/suggestions!! Regards, Andrew

Our Client software used samba protocol,If there is no firewall case , this protocol work properly from remote site.All of firwall configuration open ( this mean is all of port open ). Samba work very well, but if some constrain put in, it doesn't work. 1)I would like to know about port usage of samba protocol. I think snmpd, nmpd daemon used some port number. i can see /etc/service file.