Mail Archives: opendos/2001/03/20/14:43:07
On 2001-03-20, Alain wrote:
> The problem is that if I reset machine B. When it reboots it
> maps again it's I: do machines A's C:\ but machine A cannot
> access machine B anymore! Is there a way of making that
> connection again (or not loosing it) without exiting the
> program that is running in machine A?
At the moment I don´t have a working PNW network here
for testing (I´m in the process to recover from a totally
unexplainable headcrash of my server harddisk - a just
three months old Maxtor drive... very good to have backups,
but still much work to recreate the original very special
partition setup).
But IIRC adding the following to NET.CFG might help
(you must ensure that AUTO.VLM is loaded for this
to work):
NETWARE DOS REQUESTER
AUTO RECONNECT = ON
This should reestablish everything except for
file-specific stuff, that is, you should have the
same mappings and captures as before without
a need to exit the application and run your
log-in script again, but if your application had
a file open on the server, the application will
have to reopen it again and the contents of the
transmission buffer will be lost, of course.
I´m sure this works in case of a physical lost
connection for a couple of minutes (timeout
can be controlled by another directive), but
I´m not completely sure if it also works when
rebooting the server.
I would also try to increase the
timeout and retry values a bit:
NETWARE DOS REQUESTER
AUTO RETRY = 0..3640 <0>
BIND RECONNECT = ON | <OFF>
BROADCAST RETRIES =1..255 <3>
BROADCAST TIMEOUT=1.255 <2>
Please tell us, if this helps, so we can all learn...
Matthias
------------------------------------------------------------
Matthias Paul, Ubierstrasse 28, D-50321 Bruehl, Germany
<Matthias DOT Paul AT post DOT rwth-aachen DOT de> <mpaul AT drdos DOT org>
http://www.uni-bonn.de/~uzs180/mpdokeng.html
------------------------------------------------------------
My homepage has moved, please update your pointers.
- Raw text -