Samaba Issue with copying
I have recently set up samba to act as a domain controller. At first glance the setup seems to work fine however when I try to move or copy large files (800 meg +)from my desktop to the server I receive the following error after about one minute: "the specified network name is no longer available". I have ensured that the Suse firewall2 and WindowsXP firewall are turned off. Does anyone have any idea?
Router Specs: Netgear WiFi /w 4Wired Cat5 ports Firewall Status: On (Tried off as well) Server Specs: Suse 9.1 Linux RAID 5 Controller Samba 3.0.20a Domain Controller Firewall status: off Desktop Specs: Windows XP Pro Connecting to Domain is Successful Can copy/read and write files smaller than 800 mb Samba conf 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 if the # samba-doc package is installed. # Date: 09-25-2005 [global] netbios name = borg-queen workgroup = THE_BORG server string = Borg Server domain logons = yes logon path = \\borg-queen\%U # Browsing options os level = 34 local master = yes preferred master = yes domain master = yes winssupport = yes name resolve order = wins lmhosts hosts bcast # Security configuration options encrypt passwords = Yes passdb backend = smbpasswd hosts allow = 192.168.0. guest ok = no security = user # Debug logging information log level = 2 log file = /var/log/samba.log.%m max log size = 50 debug timestamp = yes [borgfiles] valid users = dominator, belladonna, mobile-dom, phone-dom, borg-queen comment = All Files path = /home/borg-queen/borg-files/ writeable = yes follow symlinks = yes wide links = yes map archive = yes map system = yes map hidden = yes delete readonly = yes [dominator] valid users = dominator, borg-queen path = /home/dominator/ writeable = yes follow symlinks = yes wide links = yes map archive = yes map system = yes map hidden = yes delete readonly = yes [belladonna] valid users = belladonna, borg-queen path = /home/belladonna/ writeable = yes follow symlinks = yes wide links = yes map archive = yes map system = yes map hidden = yes delete readonly = yes [mobile-dom] valid users = mobile-dom, borg-queen comment = All Files path = /home/mobile-dom/ writeable = yes follow symlinks = yes wide links = yes map archive = yes map system = yes map hidden = yes delete readonly = yes [netlogon] comment = The domain logon service path = /home/logon/ public = no writeable = no browsable = no [profile] comment = User profiles path = /home/profile create mode = 0600 directory mode = 0700 writeable = yes browsable = no |
FYI my samba no domain but look at ur smb.conf , take a look if samba understand this word
" winssupport = yes" there could be space |
seems to be some hardware issue, faulty hardware, mayb network card
|
Quote:
|
From my own experiences it is probably hardware related. It could be a bad cable, port or NIC. I would try and rule these factors out....
|
(didnt mean to post this)
|
(or post this)
|
Just a thought: but you may want to up you 'OS level' on your Samba server to '=65' since if I have read my manuals correctly Windows XP has a permanent and unadjustable setting of '60' and it is just possible that during a large file copy (which doubtless is taking some time) there is a LAN message coming on from the XP machine that wants to believe that it is the master server - and it probably throws a hissy-fit when it gets no response or acknowledgement.
I have one XP (Tablet PC) and two W2k (one desktop, one laptop) and a laptop 64-bit SuSe 9.3 or (dualboot) OpenSuSe 10 beta4 (64-bit) running as a Samba Server and I don't have the problems you are encountering. HTH |
All times are GMT -5. The time now is 02:33 PM. |