- #Private profile redirector driver#
- #Private profile redirector code#
- #Private profile redirector windows#
+0x038 CurrentByteOffset : _LARGE_INTEGER 0x0ĬreateOptions: ( FILE_OPEN_REPARSE_POINT | FILE_NON_DIRECTORY_FILE | FILE_SYNCHRONOUS_IO_NONALERT | FILE_SEQUENTIAL_ONLY )Ī file name before RxCanonicalizeNameAndObtainNetRoot() call: +0x030 FileName : _UNICODE_STRING "\ F:00000000002c8383\tl-ws-node2\Profile Storage\User004\Start Menu\Programs\Accessories\Synchronize.lnk"
+0x004 DeviceObject : 0x8985b7e8 _DEVICE_OBJECT WARNING: Frame IP not in any known module. At that time my PreCreate() mini-filter callback routine had already been completed and passed this request to a lower driver, i.e. All structures and other information were captured while in RxCommonCreate() and lower routines. I'm putting down some info that perhaps will be useful to shed some light on this strange problem. It's worth to mention that this failed operation is retried four times then and every time it fails.
#Private profile redirector code#
When I log on to the client machine using the remote desktop, the client machine begins to transfer profile files from the file server machine, and then at some point of time the operation fails on some file with an error code STATUS_BAD_NETWORK_PATH.
#Private profile redirector windows#
In this experiment there are three machines (all with Windows Server 2003 installed): a file server which contains a user profile, a client machine with my mini-filter installed which the above profile is copied to, and yet another machine which is used for a connection to the client machine via the remote desktop.
#Private profile redirector driver#
Everything was fine, but when I tried to test a profile roaming on Windows Server 2003 machines, my driver began to fail steadily on a single file. I develop some kind of an FS mini-filter driver and some days ago I began to perform various tests. Recently I faced some odd problem with a redirector.
0 kommentar(er)
