Client Hangs when I am not connected to my company's VPN

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Client Hangs when I am not connected to my company's VPN

Post by deauxver » Fri Sep 25, 2020 3:18 pm

I have EVERYTHING set to search my hard drive as well as a bunch of select network drives and other PCs on my company's network which are only accessible when I am connected by their VPN. Most times, when I disconnect from VPN, I can no longer use EVERYTHING because it freezes. I understand it cannot search those remote locations when I am disconnected, but I'd like it to not freeze when it cannot connect to them, so that I can still search my local drives.
I have tried exiting (and even quitting the process in Task Manager) from EVERYTHING prior to disconnecting from VPN, but in most cases, I still cannot restart EVERYTHING without it hanging.
There have been rare occassions when I have been able to use EVERYTHING when not connected to VPN (perhaps after a restart or some fresh instance where I have not yet connected to the VPN) but on most occassions the only way I can un-freeze EVERYTHING is by re-connecting to the VPN.

Is there a setting I can make that will prevent this problem, and allow me to easily go on using EVERYTHING to search my local drives even after I have disconnected from company VPN?
~deauxver

NotNull
Posts: 2335
Joined: Wed May 24, 2017 9:22 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by NotNull » Sat Sep 26, 2020 7:57 pm

First guess: Everything is still updating it's folder indexes when you disconnect.

The default update for folder indexes is scheduled to take place at 03:00 AM. If Everything misses aschedule, it will try to catch up the first tie Everything is running *and* the olders are available.

As a first test, I would:
- Go o Menu:Tools => Options => Indexes => Folders
- In the Folders box, select the first folder
- Select the Never rescan radio button
- repaet for all other folder indexes.
- Click OK button

Does this fix your issue?

There are ways to streamline your folder update schedule, but this would be a good first step.

deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by deauxver » Mon Sep 28, 2020 3:03 pm

I checked "never rescan" on all of my listed folders (have about 10 of them, so this would be a pain to do every time I disconnect from VPN, even so....). After OK'ing the preferences box, I then disconnected from my VPN.

But, the program still hung up at that time, after a minute or so I reconnected to the VPN and EVERYTHING some seconds later un-hung and went back to being usable.

Two further comments: After a long while of being "hung", EVERYTHING eventually becomes usable. But it might be hours or more of disconnection from VPN, I don't know how long it really takes for EVERYTHING to stop "complaining" about not being connected, I have never been able to wait that long when I actually need to search something off VPN.

Before disconnecting from VPN, I did on multiple occassions verify that none of the network folders was currently indicated as "scanning". It does not seem to matter, just the disconnection from VPN triggers the "hang" condition.

void
Site Admin
Posts: 5731
Joined: Fri Oct 16, 2009 11:31 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by void » Wed Sep 30, 2020 2:23 am

This could be the 'Attempt to monitor changes' option for your Folder index.

-If reading changes to your VPN drive fails, Everything will re-read changes to your VPN drive every 30 seconds.

Please try increasing this delay:
  • In Everything, type in the following search and press ENTER:
    /monitor_retry_delay=3600000
    If successful, you should see monitor_retry_delay=3600000 in the status bar for a few seconds.
    where 3600000 is the number of milliseconds to wait before reattempting to monitor changes.
    (3600000 = 1 hour)
    The default value is 30000 (30 seconds)
If that doesn't help, please try unchecking 'Attempt to monitor changes':
  • In Everything, from the Tools menu, click Options.
  • Click the Folders tab on the left.
  • Select your VPN drive
  • Uncheck Attempt to monitor changes.
  • Click OK.
if the issue still persists, could you please send some debug output:
  • In Everything, type in the following search and press ENTER:
    /debug
  • This will show a debug console.
  • What is shown in the debug console when Everything appears unresponsive?
To close the debug console:
  • In Everything, type in the following search and press ENTER:
    /debug

deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by deauxver » Thu Oct 01, 2020 3:53 pm

I did try setting the retry delay to 1 hour as you suggested, but it did not make a difference. This is probably because I already was not using "attempt to monitor changes" on any of the drives I have mapped (I've never checked that box in the past).
I enabled the debug console and then disconnected from VPN. The console output eventually stopped (last line of output was "update m 0 5167056"), and I captured it both as text and (for the last visible section of screen) as a screen dump (attached), in case seeing the colors on the final outputs is helpful.

I did also capture some of the text from the rapidly scrolling console output once I reconnected to the VPN and output resumed, but I don't know if that information is useful. There was a lot of it and I am not sure I was able to capture back to the beginning once it reconnected. There must be a way to save the logs automatically but I have not yet done so.

Code: Select all

DB_WAIT: _db_ready_proc waited 0.000180 seconds
update m 0 5167056
update index C:
USN BASIC_INFO_CHANGE DeerPark_NAD_Inventory.xlsx
updated C: in 0.001260 seconds
processed usn records in 0.000051 seconds
resume ntfs monitor 0
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000164 seconds
update m 0 5167056
update index C:
USN BASIC_INFO_CHANGE CLOSE DeerPark_NAD_Inventory.xlsx
updated C: in 0.001521 seconds
resume ntfs monitor 0
processed usn records in 0.000046 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000087 seconds
update m 0 5167056
update index C:
USN DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION CLOSE ldcpu.data
updated C: in 0.004028 seconds
resume ntfs monitor 0
processed usn records in 0.000478 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000234 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND FirewallEventMonitor.log
updated C: in 0.002956 seconds
resume ntfs monitor 0
processed usn records in 0.000756 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000074 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND DATA_OVERWRITE FirewallEventMonitor.log
USN DATA_EXTEND DATA_OVERWRITE CLOSE FirewallEventMonitor.log
updated C: in 0.002753 seconds
processed usn records in 0.000083 seconds
resume ntfs monitor 0
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000328 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND LocalSch.log
USN DATA_EXTEND CLOSE LocalSch.log
updated C: in 0.002546 seconds
resume ntfs monitor 0
processed usn records in 0.001376 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000181 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND LocalSch.log
USN DATA_EXTEND CLOSE LocalSch.log
USN DATA_EXTEND purgefile.log
USN DATA_EXTEND CLOSE purgefile.log
USN DATA_EXTEND purgefile.log
USN DATA_EXTEND CLOSE purgefile.log
USN DATA_EXTEND purgefile.log
USN DATA_EXTEND CLOSE purgefile.log
USN DATA_EXTEND purgefile.log
USN DATA_EXTEND CLOSE purgefile.log
USN DATA_EXTEND purgefile.log
USN DATA_EXTEND CLOSE purgefile.log
USN DATA_TRUNCATION broker.conf.xml
USN DATA_EXTEND DATA_TRUNCATION broker.conf.xml
USN DATA_EXTEND DATA_TRUNCATION CLOSE broker.conf.xml
USN DATA_EXTEND purgefile.log
USN DATA_EXTEND CLOSE purgefile.log
USN DATA_EXTEND purgefile.log
USN DATA_EXTEND CLOSE purgefile.log
USN DELETE CLOSE preferredservers.dat
USN CREATE stats.db-journal
USN CREATE DATA_EXTEND stats.db-journal
USN CREATE DATA_EXTEND CLOSE stats.db-journal
USN DELETE CLOSE stats.db-journal
updated C: in 0.014908 seconds
resume ntfs monitor 0
processed usn records in 0.003065 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000256 seconds
update m 0 5167056
update index C:
USN DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION CLOSE ldcpu.data
USN CREATE Olktmp.png
USN CREATE DATA_EXTEND Olktmp.png
USN CREATE DATA_EXTEND CLOSE Olktmp.png
USN DELETE CLOSE microsoft-office-outlook-exe-15_34863_0.png
USN CREATE microsoft-office-outlook-exe-15_34958_0.png
USN CREATE DATA_EXTEND microsoft-office-outlook-exe-15_34958_0.png
USN CREATE DATA_EXTEND DATA_OVERWRITE microsoft-office-outlook-exe-15_34958_0.png
USN CREATE BASIC_INFO_CHANGE DATA_EXTEND DATA_OVERWRITE microsoft-office-outlook-exe-15_34958_0.png
USN CREATE BASIC_INFO_CHANGE DATA_EXTEND DATA_OVERWRITE CLOSE microsoft-office-outlook-exe-15_34958_0.png
updated C: in 0.008273 seconds
resume ntfs monitor 0
processed usn records in 0.002563 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000088 seconds
update m 0 5167056
update index C:
USN DATA_TRUNCATION 7374657068656e2e736d6574616e6140636f6e74696e656e74616c2d636f72706f726174696f6e2e636f6d.tmp
USN DATA_EXTEND DATA_TRUNCATION 7374657068656e2e736d6574616e6140636f6e74696e656e74616c2d636f72706f726174696f6e2e636f6d.tmp
USN DATA_EXTEND DATA_TRUNCATION CLOSE 7374657068656e2e736d6574616e6140636f6e74696e656e74616c2d636f72706f726174696f6e2e636f6d.tmp
updated C: in 0.004383 seconds
resume ntfs monitor 0
processed usn records in 0.000735 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000195 seconds
update m 0 5167056
update index C:
USN DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION CLOSE ldcpu.data
updated C: in 0.004070 seconds
resume ntfs monitor 0
processed usn records in 0.000488 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000125 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND FirewallEventMonitor.log
updated C: in 0.002276 seconds
resume ntfs monitor 0
processed usn records in 0.001009 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000152 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND DATA_OVERWRITE FirewallEventMonitor.log
USN DATA_EXTEND DATA_OVERWRITE CLOSE FirewallEventMonitor.log
USN DELETE CLOSE Olktmp.png
updated C: in 0.004394 seconds
resume ntfs monitor 0
processed usn records in 0.001161 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000184 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND LocalSch.log
USN DATA_EXTEND CLOSE LocalSch.log
updated C: in 0.002458 seconds
resume ntfs monitor 0
processed usn records in 0.000745 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000086 seconds
update m 0 5167056
update index C:
USN CREATE EVERYTHING_debug_console_contents.txt
USN CREATE CLOSE EVERYTHING_debug_console_contents.txt
USN DELETE CLOSE EVERYTHING_debug_console_contents.txt
updated C: in 0.002873 seconds
resume ntfs monitor 0
processed usn records in 0.001772 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000220 seconds
update m 0 5167056
update index C:
USN CREATE EVERYTHING_debug_console_contents.txt
USN CREATE DATA_EXTEND EVERYTHING_debug_console_contents.txt
USN CREATE DATA_EXTEND CLOSE EVERYTHING_debug_console_contents.txt
USN DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION CLOSE ldcpu.data
updated C: in 0.005762 seconds
resume ntfs monitor 0
processed usn records in 0.001216 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000113 seconds
update m 0 5167056
update index C:
USN DATA_OVERWRITE edbtmp.jtx
USN RENAME_OLD_NAME DATA_OVERWRITE edb.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE edb3F6A0.jtx
USN RENAME_OLD_NAME DATA_OVERWRITE edbtmp.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE edb.jtx
USN RENAME_OLD_NAME edb3F69C.jtx
USN RENAME_NEW_NAME edbtmp.jtx
USN RENAME_NEW_NAME CLOSE edbtmp.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE CLOSE edb3F6A0.jtx
updated C: in 0.005469 seconds
resume ntfs monitor 0
processed usn records in 0.005229 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000167 seconds
update m 0 5167056
update index C:
USN DATA_OVERWRITE edb.jcp
USN DATA_OVERWRITE CLOSE edb.jcp
updated C: in 0.002715 seconds
resume ntfs monitor 0
processed usn records in 0.000436 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000097 seconds
update m 0 5167056
update index C:
USN DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION CLOSE ldcpu.data
updated C: in 0.003803 seconds
resume ntfs monitor 0
processed usn records in 0.000904 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000231 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND FirewallEventMonitor.log
updated C: in 0.002623 seconds
resume ntfs monitor 0
processed usn records in 0.000873 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000078 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND DATA_OVERWRITE FirewallEventMonitor.log
USN DATA_EXTEND DATA_OVERWRITE CLOSE FirewallEventMonitor.log
updated C: in 0.002913 seconds
resume ntfs monitor 0
processed usn records in 0.000071 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000149 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND LocalSch.log
USN DATA_EXTEND CLOSE LocalSch.log
updated C: in 0.002624 seconds
resume ntfs monitor 0
processed usn records in 0.001051 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000107 seconds
update m 0 5167056
update index C:
USN DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION CLOSE ldcpu.data
updated C: in 0.003402 seconds
resume ntfs monitor 0
processed usn records in 0.000657 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000170 seconds
update m 0 5167056
update index C:
USN DATA_EXTEND FirewallEventMonitor.log
updated C: in 0.002160 seconds
resume ntfs monitor 0
processed usn records in 0.000978 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000124 seconds
update m 0 5167056
update index C:
USN DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION ldcpu.data
USN DATA_EXTEND DATA_TRUNCATION CLOSE ldcpu.data
USN DATA_EXTEND DATA_OVERWRITE FirewallEventMonitor.log
USN DATA_EXTEND DATA_OVERWRITE CLOSE FirewallEventMonitor.log
USN CREATE 9443.db-journal
USN CREATE DATA_EXTEND 9443.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE 9443.db-journal
USN DATA_OVERWRITE 9443.db
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE 9443.db-journal
USN DELETE CLOSE 9443.db-journal
USN DATA_OVERWRITE CLOSE 9443.db
USN DATA_TRUNCATION 9443.json
USN DATA_EXTEND DATA_TRUNCATION 9443.json
USN DATA_EXTEND DATA_TRUNCATION CLOSE 9443.json
updated C: in 0.014084 seconds
resume ntfs monitor 0
processed usn records in 0.002797 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000185 seconds
WM_DEVICECHANGE 0000000000000007 0000000000000000
config volume: \\?\Volume{} | C: |  | 1
add volume: \\?\Volume{} | C: |
config volume: \\?\Volume{} | D: |  | 1
add volume: \\?\Volume{} | D: |
VEH 781577248
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
GetVolumePathNamesForVolumeName C:
add found ntfs volume: \\?\Volume{} | C: |  | 0000000021bc9940
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
GetVolumePathNamesForVolumeName D:
add found ntfs volume: \\?\Volume{} | D: |  | 0000000021bc96c0
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
QueryDosDevice C: \Device\HarddiskVolume4
QueryDosDevice D: \Device\HarddiskVolume5
QueryDosDevice E: \Device\HarddiskVolume2
QueryDosDevice O: \Device\Mup\DfsClient\;O:...
update m 0 5167056
Attachments
EVERYTHING_debug_console_contents 2020-10-01 103711.jpg
EVERYTHING_debug_console_contents 2020-10-01 103711.jpg (277.29 KiB) Viewed 1050 times
Last edited by void on Fri Oct 02, 2020 6:48 am, edited 3 times in total.

void
Site Admin
Posts: 5731
Joined: Fri Oct 16, 2009 11:31 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by void » Fri Oct 02, 2020 7:01 am

Thanks for the debug logs.

Everything was notified about a device change.
Looks like Everything is hanging when gathering online volumes after the device change notification.

Everything might be trying to determine if the O: drive is a NTFS or ReFS volume.

Please try disabling auto include new volumes:
  • In Everything, from the Tools menu, click Options.
  • Click the NTFS tab on the left.
  • Uncheck Automatically include new fixed volumes.
  • Uncheck Automatically include removable fixed volumes.
  • Click the ReFS tab on the left.
  • Uncheck Automatically include new fixed volumes.
  • Uncheck Automatically include removable fixed volumes.
  • Click OK.
Does the issue persist?

deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by deauxver » Mon Oct 05, 2020 3:54 pm

Yes, unfortunately, it seems to persist even after unchecking the first box on both NTFS and ReFS pages. (the second one was already unchecked). I made more debug outputs, having selected "verbose" mode.

I did the same thing I provided last time; the first blob of text is from the instance where I disconnected from VPN and logged until the output froze. Separated by a bunch of spaces, the second blob of text is as quickly as I could capture the output after I reconnected to VPN and it started scrolling again. I'll paste it below again, since I don't think this forum will let me attach the actual TXT file.

Code: Select all

Everything
Version 1.4.1.935 (x64)
Windows NT 6.2
Processors 8
IsAdmin 0
AppData 1
Service 1
cmdline "C:\Program Files\Everything\Everything.exe"
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 0000000000080cda, current focus 0000000000080cda
update m 0 5235472
update index C:
USN DATA_EXTEND FirewallEventMonitor.log
USN DATA_EXTEND CLOSE FirewallEventMonitor.log
updated C: in 0.003414 seconds
resume ntfs monitor 0
processed usn records in 0.000720 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000164 seconds
update m 0 5235472
update index C:
USN DATA_OVERWRITE edb.jcp
USN DATA_OVERWRITE CLOSE edb.jcp
USN DATA_OVERWRITE edbtmp.jtx
USN RENAME_OLD_NAME DATA_OVERWRITE edb.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE edb004A5.jtx
USN RENAME_OLD_NAME DATA_OVERWRITE edbtmp.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE edb.jtx
USN RENAME_OLD_NAME edb004A1.jtx
USN RENAME_NEW_NAME edbtmp.jtx
USN RENAME_NEW_NAME CLOSE edbtmp.jtx
updated C: in 0.007525 seconds
resume ntfs monitor 0
processed usn records in 0.004942 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000236 seconds
update m 0 5235472
update index C:
USN RENAME_NEW_NAME DATA_OVERWRITE CLOSE edb004A5.jtx
USN DATA_OVERWRITE edb.jcp
USN DATA_OVERWRITE CLOSE edb.jcp
USN DATA_OVERWRITE edbtmp.jtx
USN RENAME_OLD_NAME DATA_OVERWRITE edb.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE edb004A6.jtx
USN RENAME_OLD_NAME DATA_OVERWRITE edbtmp.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE edb.jtx
USN CREATE edbtmp.jtx
USN CREATE DATA_EXTEND edbtmp.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE CLOSE edb004A6.jtx
USN CREATE DATA_EXTEND DATA_OVERWRITE edbtmp.jtx
USN DATA_OVERWRITE edb.jcp
USN DATA_OVERWRITE CLOSE edb.jcp
USN RENAME_OLD_NAME DATA_OVERWRITE edb.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE edb004A7.jtx
USN CREATE RENAME_OLD_NAME DATA_EXTEND DATA_OVERWRITE edbtmp.jtx
USN CREATE RENAME_NEW_NAME DATA_EXTEND DATA_OVERWRITE edb.jtx
USN RENAME_OLD_NAME edb004A2.jtx
USN RENAME_NEW_NAME edbtmp.jtx
USN RENAME_NEW_NAME CLOSE edbtmp.jtx
USN RENAME_NEW_NAME DATA_OVERWRITE CLOSE edb004A7.jtx
USN DATA_OVERWRITE edb.jcp
USN DATA_OVERWRITE CLOSE edb.jcp
updated C: in 0.025878 seconds
resume ntfs monitor 0
processed usn records in 0.005712 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000184 seconds
when ready 11 000000000000002d 0000000000000000
update m 0 5235472
update index C:
USN DELETE CLOSE system.xml
USN CREATE system.xml
USN CREATE DATA_EXTEND system.xml
USN CREATE DATA_EXTEND CLOSE system.xml
updated C: in 0.006973 seconds
resume ntfs monitor 0
processed usn records in 0.001521 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000180 seconds
update m 0 5235472
update index C:
USN DATA_EXTEND SelfElectController.log
USN DATA_EXTEND CLOSE SelfElectController.log
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN DATA_EXTEND FirewallEventMonitor.log
USN DATA_EXTEND CLOSE FirewallEventMonitor.log
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
updated C: in 0.021702 seconds
resume ntfs monitor 0
processed usn records in 0.001500 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000087 seconds
update m 0 5235472
update index C:
USN CREATE ~WRS{EC3F8F06-44D4-44CD-995C-0F1055BEE24F}.tmp
USN CREATE DATA_EXTEND ~WRS{EC3F8F06-44D4-44CD-995C-0F1055BEE24F}.tmp
updated C: in 0.003220 seconds
resume ntfs monitor 0
processed usn records in 0.001091 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000175 seconds
update m 0 5235472
update index C:
USN DATA_OVERWRITE edb.jcp
USN DATA_OVERWRITE CLOSE edb.jcp
updated C: in 0.003441 seconds
resume ntfs monitor 0
processed usn records in 0.000371 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000084 seconds
update m 0 5235472
update index C:
USN DATA_EXTEND SymTrackServiceDebugLog.dbg
USN DATA_EXTEND DATA_OVERWRITE SymTrackServiceDebugLog.dbg
USN DATA_EXTEND DATA_OVERWRITE CLOSE SymTrackServiceDebugLog.dbg
updated C: in 0.005366 seconds
resume ntfs monitor 0
processed usn records in 0.000704 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000526 seconds
update m 0 5235472
update index C:
USN CREATE Olktmp.png
USN CREATE DATA_EXTEND Olktmp.png
USN CREATE DATA_EXTEND CLOSE Olktmp.png
updated C: in 0.007044 seconds
resume ntfs monitor 0
processed usn records in 0.001015 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000157 seconds
WM_DEVICECHANGE 0000000000000007 0000000000000000
config volume: \\?\Volume{} | C: |  | 1
add volume: \\?\Volume{} | C: |
config volume: \\?\Volume{} | D: |  | 1
add volume: \\?\Volume{} | D: |
VEH 5068272
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
GetVolumePathNamesForVolumeName C:
add found ntfs volume: \\?\Volume{} | C: |  | 000000002618aed0
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
GetVolumePathNamesForVolumeName D:
add found ntfs volume: \\?\Volume{} | D: |  | 000000002618a610
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
QueryDosDevice C: \Device\HarddiskVolume4
QueryDosDevice D: \Device\HarddiskVolume5
QueryDosDevice O: \Device\Mup\DfsClient\;...
update m 0 5235472
















USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN DELETE CLOSE mc_2020100510463525002310000334C.txml
USN DELETE CLOSE mc_2020100510463543075050000334C.txml
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN SECURITY_CHANGE Logs
USN SECURITY_CHANGE CLOSE Logs
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN DATA_TRUNCATION Agent.ini
USN DATA_EXTEND DATA_TRUNCATION Agent.ini
USN DATA_EXTEND DATA_TRUNCATION CLOSE Agent.ini
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE temp-index
USN CREATE DATA_EXTEND temp-index
USN CREATE DATA_EXTEND CLOSE temp-index
USN BASIC_INFO_CHANGE temp-index
USN BASIC_INFO_CHANGE SECURITY_CHANGE temp-index
USN CREATE the-real-index~RF14944f.TMP
USN CREATE CLOSE the-real-index~RF14944f.TMP
USN DELETE CLOSE the-real-index~RF14944f.TMP
USN RENAME_OLD_NAME the-real-index
USN RENAME_NEW_NAME the-real-index~RF14944f.TMP
USN RENAME_OLD_NAME BASIC_INFO_CHANGE SECURITY_CHANGE temp-index
USN RENAME_NEW_NAME BASIC_INFO_CHANGE SECURITY_CHANGE the-real-index
USN RENAME_NEW_NAME CLOSE the-real-index~RF14944f.TMP
USN RENAME_NEW_NAME BASIC_INFO_CHANGE SECURITY_CHANGE CLOSE the-real-index
USN DELETE CLOSE the-real-index~RF14944f.TMP
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN RENAME_OLD_NAME 2020100510463561350020000334C.txml
USN RENAME_NEW_NAME mc_2020100510463561350020000334C.txml
USN RENAME_NEW_NAME CLOSE mc_2020100510463561350020000334C.txml
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
updated C: in 0.109728 seconds
resume ntfs monitor 0
processed usn records in 0.024553 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000278 seconds
update m 0 5235472
update index C:
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE mapolicy.db-journal
USN CREATE DATA_EXTEND mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE mapolicy.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE mapolicy.db-journal
USN DELETE CLOSE mapolicy.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
updated C: in 0.062188 seconds
resume ntfs monitor 0
processed usn records in 0.013855 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000350 seconds
update m 0 5235472
update index C:
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN DELETE CLOSE mc_2020100510463561350020000334C.txml
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
USN CREATE ma.db-journal
USN CREATE DATA_EXTEND ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE ma.db-journal
USN CREATE DATA_EXTEND DATA_OVERWRITE CLOSE ma.db-journal
USN DELETE CLOSE ma.db-journal
updated C: in 0.016291 seconds
resume ntfs monitor 0
processed usn records in 0.006504 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000144 seconds
update m 0 5235472
update index C:
USN DELETE CLOSE {292CE27B-A952-4DF0-8C10-11C258C3C093} - OProcSessId.dat
updated C: in 0.001430 seconds
resume ntfs monitor 0
processed usn records in 0.001044 seconds
DB_WAIT: _db_ready_proc waiting...
DB_WAIT: _db_ready_proc waited 0.000123 seconds
Last edited by therube on Mon Oct 05, 2020 7:26 pm, edited 1 time in total.

deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by deauxver » Tue Oct 20, 2020 4:34 pm

Any other thoughts based on that last log?

As I probably noted earlier, if the PC has been off VPN for a long time (or perhaps, never connected since a reboot of the PC), EVERYTHING works just fine and searches the local drive as if nothing is wrong. It is only for a certain (ableit intolerably long) duration after disconnecting from a VPN session that the tool is unusable. I have never figured out how long that period is, however, since I just reconnect to VPN when I need to do even a local search during that time. Fortunately I am doing most stuff in the home office these days and reconnecting to VPN at those times is not an issue :)

void
Site Admin
Posts: 5731
Joined: Fri Oct 16, 2009 11:31 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by void » Wed Oct 21, 2020 10:34 am

Thanks for the debug logs.

Looks like Everything is hanging when checking volume information on the O: drive.

When the VPN is disconnected, is the O: drive listed in Explorer?

When the VPN is disconnected, from a command prompt, what does the following command show:
fsutil fsinfo drivetype o:
fsutil fsinfo volumeinfo o:

deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by deauxver » Wed Oct 21, 2020 3:28 pm

I attached three screen dumps, one of the Command Prompt as you requested, and two captures of the Windows Explorer, all after disconnecting from VPN.
I noted that the O: drive appears in Windows explorer when disconnected from VPN, and as the second Explorer capture shows, it does not indicate as "disconnected network drive" as do some of the others. But, it is actually disconnected when off of VPN, of that I am sure - it is an internal company location.
The second Windows Explorer capture shows a green "progress" bar at the top, and it took many minutes for it to become fully extended to the rightmost edge, or "completed" it's scan or whatever it was doing, perhaps because of this rogue network drive which is not really connected.
Afterwards, the O: drive still lists as "Network Drive" with no indication of being disconnected like the others.
Is there some Windows Explorer or system setting that should be used to change the status of the O: drive when not connected to VPN?
Attachments
WindowsExplorerVPNdisconnected 2020-10-21 101740.jpg
WindowsExplorerVPNdisconnected 2020-10-21 101740.jpg (69.91 KiB) Viewed 142 times
WindowsExplorerVPNdisconnected 2020-10-21 101125.jpg
WindowsExplorerVPNdisconnected 2020-10-21 101125.jpg (35.17 KiB) Viewed 142 times
CommandPromptVPNdisconnected 2020-10-21 101005.jpg
CommandPromptVPNdisconnected 2020-10-21 101005.jpg (20.7 KiB) Viewed 142 times

therube
Posts: 2718
Joined: Thu Sep 03, 2009 6:48 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by therube » Wed Oct 21, 2020 4:03 pm

(Seems fsutil won't work like that on an actual "foreign" system.
It would give limited information with a locally mapped, same system, drive letter.)

therube
Posts: 2718
Joined: Thu Sep 03, 2009 6:48 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by therube » Wed Oct 21, 2020 7:22 pm

Are you able to run the fsutil commands directly on the system where O: (\\auto.contiwan.com) resides?

deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by deauxver » Wed Oct 21, 2020 8:46 pm

No, I cannot even switch my drive to "O:"; that system is on some remote computer elsewhere in the company network. I only have physical access to my PC.

I did try un-mapping that remote drive (O:) from my PC (which I could only do gracefully while still connected to VPN) and then logged off, and EVERYTHING did not hang. But, I would have to re-map that drive (and any other drive that needed to be un-mapped for the same reason) each time I log back on. Not the best solution, but might be workable if I could "script" the un-mapping and re-mapping procedure. Perhaps there is a feature within Windows that would allow such an action to be done manually or even automatically, but I do not know of it yet.

void
Site Admin
Posts: 5731
Joined: Fri Oct 16, 2009 11:31 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by void » Wed Oct 21, 2020 9:20 pm

Thanks for the screenshots.

The admin command prompt will not be able to see your O: drive.

From a regular command prompt (not an elevated command prompt):

When the VPN is disconnected, what do the following command show:
fsutil fsinfo drivetype o:
fsutil fsinfo volumeinfo o:

Does this hang? -this would confirm reading the volumeinfo is hanging.

deauxver
Posts: 8
Joined: Fri Sep 25, 2020 3:01 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by deauxver » Thu Oct 22, 2020 2:48 pm

The attached CMD window capture (non-Admin prompt) shows, in green is with the VPN connected, and in red is after disconnecting. The second command did not return anything for several minutes, and eventually (not shown) it returned something like "network (or drive) not found". So I guess it hanged on that second command when not connected to VPN.
Attachments
CommandPromptNon-Admin_VPNconnected-then-disconnected.jpg
green when connected, red when disconnected from VPN
CommandPromptNon-Admin_VPNconnected-then-disconnected.jpg (41.19 KiB) Viewed 88 times

void
Site Admin
Posts: 5731
Joined: Fri Oct 16, 2009 11:31 pm

Re: Client Hangs when I am not connected to my company's VPN

Post by void » Fri Oct 23, 2020 5:07 am

Thanks for the fsinfo information.

Odd fsutil fsinfo drivetype reports a remote/network drive as Windows reports the drive as a harddrive to Everything.

I've added a ini setting scan_volume_drive_letters to disable scanning of these drives to the latest nightly build.

Please try disabling scan_volume_drive_letters:
  • In Everything, type in the following search and press ENTER:
    /scan_volume_drive_letters=0
    Type in the following search and press ENTER:
    /restart
Note: This will prevent Everything from trying to access volume information for each drive letter and only access volumes reported from Windows.
Note: Disabling this option will prevent Everything from finding most encrypted volumes.

Does disabling scan_volume_drive_letters help with the hanging?

Post Reply