Network drives configuration

[TedL1972]

I use many network drives which I access through XYPlorer. When the computer is active there are no problems however when I lock the screen and I resume the session after some time (1/2 hour or so) inevitably XYPlorer will not respond immediately. It will take up to 1/2 minutes to "wake up" and all the NW drives get disconnected. I have to F5 every single one of them several times before they get reconnected.

I tried to find a setting that will fix this without success so far.

Is there a configuration setting that will keep the drives always connected after the screen has been locked?

[highend]

And you did already experiment with the existing settings under Configuration | General | Safety Belts, Network | Network?

E.g. if they don't require authentication each time they are accessed, I would try to select all 4...

[TedL1972]

Yes! That did it, thank you.

I selected all of the 4 under: Configuration | General | Safety Belts, Network | Network

So far I went back 3 times after a lock screen and there was no disconnected drive and no need to F5.

[TedL1972]

Overall the problem is mostly solved but I want to mention that now that I have used it several
times I noticed that when the lock screen is on for some hours there is still a "not responding problem"
for about 10 to 20 seconds. Most of the drives remain connected except one but sometimes all are
still connected.

I wonder if using Exit (Saving) every time would make a difference. I will try this next.

[highend]

Experiment with
Configuration | General | Startup & Exit | No network browsing on startup
and if necessary:
Configuration | General | Startup & Exit | Reconnect mapped network drives on startup
when you do that...

[TedL1972]

I did but XYplorer had become unstable, long lags when switching tabs,
general slow in going from one document to another etc.

After much experimenting I found out that the problem was caused by
"Pre-check availability of servers" under General|Safety Belts, Network|
and after unchecking this all seemed to come back to "normal speed".

I will try this now for a bit and will report if handled or not.

[admin]

Thanks for the info.

I'm starting to think that "Pre-check availability of servers" and "Fast network enumeration" should be removed from UI. For most users they make things really slow.

[TedL1972]

OK, I have now been running with "Fast network enumeration" and "Pre-check availability of servers"
unchecked for a whole day and it is the best response so far.

So perhaps removing them would be wise.

However, there is still a disconnection of drives problem after locked screen for a longish time even though
after a few seconds of refreshing they come back on. Not sure if this is normal i.e. would happen with
any other program or just peculiar to XYplorer. I know that it rarely happens with Explorer (Microsoft)
so I am just providing the data for info.

[admin]

Thanks for the info. Hard to say. Network is a bitch.

[TedL1972]

You're welcome and thanks to you and Highend for the always valuable tips!

I had another thought on the network problem and for that I just need to
clarify the term "startup" as used in General|Startup|No network browsing on startup
(which I have it currently checked).

Does startup in this case mean a computer start up i.e. pc re-boot or
any start up - E.g. resuming a session after a screen lock of an hour or a log off?

[highend]

On XY startup...

[Filehero]

Does startup in this case mean a computer start up i.e. pc re-boot or
any start up - E.g. resuming a session after a screen lock of an hour or a log off?

A start of a (new) XYplorer session - which is implicit part of a pc reboot or a windows log-off/log-on cycle (which translates to a new windows user session w/o previous reboot).
A simple windows re-login after the Windows lock-screen only restores access to the (still) running Windows user session including all opened applications. XYplorer, like any other running program, will not execute any automatically triggered "re-network browsing" in those cases (*) without any additional "special actions" covering this case.

/e: too late, too verbose ...

[TedL1972]

Thanks for the clarification.

I have run the application with both "No network browsing on startup" checked and unchecked and
it didn't seem to make any difference. The disconnection problem after resuming a locked screen
session is still present and it lasts about 10 seconds on average.
Nothing major just a little bit annoying.