From: Abramson, Stuart (SAbramson@Wabtec.com)
Date: Fri Dec 19 2003 - 08:19:54 EST
hpux-admins:
Robert Glenn had the same answer as us:
Here's what the problem was. I almost don't believe it.
We saw "connection reset by peer" in the samba log for our Windows
workstation. We found corresponding "connection reset by peer" in
UNIXHOST:/var/adm/syslog/syslog.log
The problem was that "Autonegotiation" was set to "on" in the Windows
workstation NIC card, and that allowed the windows workstation to
renegotiate LAN speed periodically, and he would do it right in the middle
of our SAMBA session! (I'm not a Windows guy..)
So, our Windows guy set the NIC card to "100 Full / autonegotiate off", and
now we're fine.
I almost don't believe it...
Here's the syslog records:
Dec 17 10:22:31 wcshps06 smbd[29075]: read_data: read failure for 19168.
Error = Connection reset by peer
Dec 17 10:25:21 wcshps06 smbd[6423]: read_data: read failure for 39608.
Error = Connection reset by peer
Dec 17 10:35:02 wcshps06 smbd[6599]: read_data: read failure for 39608.
Error = Connection reset by peer
Dec 17 10:52:06 wcshps06 smbd[7506]: read_data: read failure for 43704.
Error = Connection reset by peer
Stuart
_____
From: Glenn, Robert [mailto:Robert.Glenn@csoconline.com]
Sent: Thursday, December 18, 2003 6:31 PM
To: Abramson, Stuart
Subject: RE: [HPADM] Samba problem: "Cannot Copy File. The path is too d
eep."
This may not apply in your situation, but we just recently moved our
servers to another LAN and got the same error message. Our server NICs were
set with Autoneg turned ON, and we had to change Autoneg to OFF and set
Speed to 100. That solved our problem.
-----Original Message-----
From: Abramson, Stuart [mailto:SAbramson@Wabtec.com]
Sent: Wednesday, December 17, 2003 7:48 AM
To: Hpux-Admin (hpux-admin@dutchworks.nl)
Subject: [HPADM] Samba problem: "Cannot Copy File. The path is too deep."
Hpux-admins:
We set up samba on several of our HP-UX servers.
One of our uses has a problem on his Windows client:
If he copies a file from C:\blah.blah to X:\customer\1.0\reports\US
he gets the above error:
"Cannot Copy File. The path is too deep."
If he copies a file from C:\blah.blah to Y:\customer\1.0\reports\US
it works just fine
where "X" is one UNIX server and
"Y" is another UNIX server
In short the "X" SAMBA or server file systems aren't set up right, and I
guess the "Y" server/file systems are set up correctly.
So, where will I look for this problem?
I'm going to start checking EVERYTHING: SAMBA setup and file system
permissions all the up/down the tree.
Stuart
Stuart Abramson | Off: 412/825-1434 | Cell: 412/417-1567 | email:
sabramson@wabtec.com
***** CONFIDENTIALITY NOTE *****
The content contained in this e-mail transmission is legally privileged and
confidential information intended only for the use of the individual or
entity named herein. If the reader of this transmission is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this transmission is strictly prohibited.
***** CONFIDENTIALITY NOTE *****
The content contained in this e-mail transmission is legally privileged and confidential information intended only for the use of the individual or entity named herein. If the reader of this transmission is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this transmission is strictly prohibited.
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:37 EDT