| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4295.1 | | UTRTSC::SWEEP | I want a lolly... | Tue May 20 1997 05:58 | 4 |
| See prev. notes about window 95 session timeouts (default =
appr. 45 sec's).
ADrie
|
| 4295.2 | session didn't disconnect | VAXRIO::LORENA | | Thu May 22 1997 10:13 | 13 |
|
Adrie,
I didn't find the notes that you suggested in your reply.
If it possible, could you help me to find these notes or specific
parameter to configure the session timeout ?
I don't know if is a "session timeout" problem, because the customer
though couldn't copy the big files, he didn't lost the connection, that
is, he continue to access the network driver after the problem occur.
Thanks for you attention,
Regards,
Lorena
|
| 4295.3 | | VMSNET::P_NUNEZ | | Thu May 22 1997 11:32 | 14 |
| Careful Lorena. When the client has the copy problem, to see if it's
session was terminated, you can't check from the client - it will
re-establish the session automagically whenever you try to use the
connection again.
So after the client aborts the copy operation - BEFORE DOING ANYTHING
ELSE ON THE CLIENT - do $ NET SESSION \\client-computername and see if
the session is really still there...and if you know they connected over
DECnet do $ MC NCP SHOW KNOWN LINKS or, for IP (UCX) do UCX SH
DEVICE/PORT=139 and see if the transport session is also gone...
Paul
Paul
|
| 4295.4 | you are correct | VAXRIO::LORENA | | Thu May 22 1997 13:31 | 18 |
|
>> Careful Lorena. When the client has the copy problem, to see if it's
>> session was terminated, you can't check from the client - it will
>> re-establish the session automagically whenever you try to use the
>> connection again.
Paul, you are correct, the session at the problem moment disappear and
when he execute a simple "dir command"in the drive, the session
reconnect.
Based in this information, is it possible help me to find wich
parameter we need to increase to solve this problem ?
Regards,
Lorena
|
| 4295.5 | Search this conf. for "sesstimeout" | VMSNET::P_NUNEZ | | Thu May 22 1997 17:15 | 19 |
| Lorena,
Now it gets hard ;o). Though noone seems to be able to find a
documented source, try doing the following and see if it makes any
difference:
Add the following registry DWORD value:
Add new DWORD value named SessTimeout under
HKeyLocalMachine\System\CurrentControlSet\Services\Vxd\vnetsup
It has a min value : 10 and a max value : 30000
default value (if not specified): 45
You might try setting it to 90 or even 120 (seconds)...
Please report your findings.
Paul
|
| 4295.6 | the problem is solved | VAXRIO::LORENA | | Fri May 23 1997 08:14 | 8 |
|
Paul,
We tested with the values 90, 120 and didn't work, then we tested with
maximum value = 30000 (decimal) and it worked properly under Windows
Explorer. For your information, under MS-DOS prompt, the copy didn't work.
We consider the problem solved, and thanks e best regards for your
prompt help and attention,
Lorena
|