Author Topic: Multicommander freeze when network disconnected  (Read 3329 times)

lemonwidz

  • Junior Member
  • **
  • Posts: 12
    • View Profile
Multicommander freeze when network disconnected
« on: February 26, 2016, 01:13:22 »
* bellow is my situation

1. Open network shared folder like 192.168.x.x\example\folder
2. then change my windows network. (ex, external network <-> local network)
3. (changed network is can't access 192.168.x.x)
4. then.... multicommander freeze.
5. I have to close multicommander force. T_T
6. And run multicommander again.

* It often happens these things.

I think multicommander try to connect to disconnected network, again, again, again....

How about add timeout setting?

Or already have?
« Last Edit: February 26, 2016, 01:15:47 by lemonwidz »

Mathias (Author)

  • Administrator
  • VIP Member
  • *****
  • Posts: 3888
    • View Profile
    • Multi Commander
Re: Multicommander freeze when network disconnected
« Reply #1 on: February 26, 2016, 10:44:03 »
MC does not really care if it is network or not. When accessing a \\server\share\path ( or mapped path ) MC are using it as a normal path. Windows is handling all networking.
Problem is that you are going from one type of network to another. And Windows does not know that it does not have access anymore.
Problem is that network can be slow, So it will takes a while before windows give up and time out.
MC do not have any control off this.