| Title: | TeamLinks for Windows |
| Notice: | Kit and ECO locations: See replies to note 8. o note 8. |
| Moderator: | ORION::chayna.zko.dec.com::tamara::eppes AN |
| Created: | Mon Aug 28 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2238 |
| Total number of notes: | 9650 |
Hello, all
Our customer is using both teamlink V2.5 and V2.7 under mailworks server
for digital unix..
They got the problem as below when sending document attached on client.
error message :
It was impossible to attch one of the attachments of this message
Error writing to the file.
An error occured while writing the file. the storage area for file
Cabinet service may be full.
The message can still be sent or served without this attachment.
Attachement name : C\QQ12.DOC
CFCDEBUG.LOG : writing error
We found that this problem occurs only under slip usage and they used to send
with dial up modem through slip line but a small size document(about 1000 byte)
have no problem.
They have no problem when receiving the document although size is a large.
They setup slip on decserver 700 and digital unix 3.2c and alpha 3500.
We tested another method by FTP of WIN 95. we found that ftp have
the problem,too.
C:\WINDOWS> FTP server
ftp> get filename( file size > 1000 byte)
error message : rl_recv : blocking call cancelled
ftp> get filename( file size < 1000 byte)
no problem( file copy completed)
thanks and regards
j.s park
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2083.1 | TAMARA::redear.zko.dec.com::tamara::cummings | Jerry Cummings, TeamLinks | Tue Mar 25 1997 12:23 | 4 | |
I'll see if Peter Flanagan can take a look at this one. Have you started looking at ftp help? Jerry | |||||
| 2083.2 | Looks like a hardware/stack problem | XANADU::FLANAGAN | Tue Mar 25 1997 13:02 | 20 | |
Hi J.S.,
This appears to be a problem with the TCP/IP stack or the network
not TeamLinks, since ftp fails as well. That said, to help isolate it
I suggest you try:
1. Try sending known ascii text files via ftp(i.e. no control characters) to
see if it is a network transparency problem. Special characters
can cause flow control problems (XON/XOFF). If these files work
then it is probably a communications setting on the
equipment attached to the destination modem.
2. Does it occur on all PC's? Are they all running W95? What TCP/IP
stack are you running? The built-in MS dialup? Have you tried
a public domain TCP/IP dialup like Trumpet?
3. What TCP/IP vendor are you using on the server side? They should
be able to offer some suggestions if ftp is failing.
/ Peter
| |||||