| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
HI All.
Please any help is welcome.
Problem: Copying large >1mb files from a WFW (ms tcp16) to a PAthworks
server 5.0de3 . copy stops with access denied, at server side show
session of this user gets message net2312 and in a couple of seconds
the session is restarted, if the costumer makes the same copy from dos
(outside windows) everithing its ok. !!!!!
Copying to another server , also 5.0de3, is ok
Pathworks logs dont show any error
What could be the reason (from the server side) to reach this situation
Thanks in advance Josep.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4136.1 | VMSNET::P_NUNEZ | Fri Jan 31 1997 09:21 | 25 | ||
Josep,
It could be the system where it's failing is simply slower than the
v5.0d eco3 server where it's working. Not sure if WfW behaves same as
other MS clients, but Win95 and WinNT file copies can time out due to
the manner in which they request the file open/creation. They force
PATHWORKS to allocate the entire space before writing the first byte to
the file. Disk fragmentation can also affect the time it takes
pathworks to allocate the space. It may work from DOS because DOS
doesn't request the same type of file open as WfW.
The session drops because the client redirector sets a timeout on the
smb request - that timer expires before PATHWORKS can complete the
transaction.
But wait for someone to confirm the above as, again, I'm not sure if
WfW uses the same file creation methods as Win95/WinNT clients.
In the mean time, you might post details about the two servers and
check the disk on the failing server for fragmentation (or try copying
to a disk you know isn't fragmented).
HTH,
Paul
| |||||
| 4136.2 | more data | BARNA::DSMAIL | Fri Jan 31 1997 13:43 | 10 | |
Thanks for your fast answer.
here comes some more date , excusme for hide some info preveusly.
Booth servers are in fact a cluster , that share the system disk
the customer doesnt conect to the alias due to MS tcp problems, he
conect to the single node name, and copying same data from the same
source, gets dropped session depending on the server he conects to.
So I think it cant be a fragmentation problem.
thanks for your help
Josep .
| |||||
| 4136.3 | solved ? | BARNA::DSMAIL | Fri Feb 07 1997 11:07 | 3 | |
After resetting the faulty node the problem was gone !!!
Customer says that system was rebooted after upgrade !!!!
I cant find any explanation Josep
| |||||