G
Guest
Hi,
We have a laptop that is having real problems when logging on, it sits for
at least 10 minutes while 'preparing network connections...'. It's then
another 10 minutes after the user logs on until the desktop loads. While we
were waiting for the desktop to load, I launched taskmanager, and from there
ran sysinternals filemon, which logged a huge number (14,000+) of
LanmanRedirector FAILURE's. I have pasted a couple of the entries below.
Does anyone know why this error would be occurring?
134 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FBB
143 10:20:56 mobsync.exe:2244 FASTIO_DEVICE_CONTROL \Device\LanmanRedirector
FAILURE IOCTL: 0x140FCF
150 10:20:56 mobsync.exe:2244 FASTIO_DEVICE_CONTROL \Device\LanmanRedirector
FAILURE IOCTL: 0x140FBB
155 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FCF
162 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FBB
167 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FCF
168 10:20:56 mobsync.exe:2244 FASTIO_DEVICE_CONTROL \Device\LanmanRedirector
FAILURE IOCTL: 0x140FCF
Another error the user is getting, is that once the system has eventually
loaded, and they get a problem with explorer, where it will hang, usually
permentally (we've left it for at least an hour and it's never come back),
using filemon (I don't have an example log at the moment) it looks like
explorer is trying to access "H:\<username>\\shell32.dll" which is strange,
firstly because shell32.dll is located in %systemroot%\system32. Secondly,
the users H: drive is mapped to \\server\home\<username> and this seems to
be looking for another folder called <username> user the already mapped H:
drive. I've used regmon to look though the registry and filter for
H:\<username> but nothing shows up, I also filtered for shell32, and that
only shows up as %systemroot%\system32
Can anyone suggest why LanmanRedirector is causing a problem, and why
explorer would be trying to access a non existent folder?
Cheers
Ben
We have a laptop that is having real problems when logging on, it sits for
at least 10 minutes while 'preparing network connections...'. It's then
another 10 minutes after the user logs on until the desktop loads. While we
were waiting for the desktop to load, I launched taskmanager, and from there
ran sysinternals filemon, which logged a huge number (14,000+) of
LanmanRedirector FAILURE's. I have pasted a couple of the entries below.
Does anyone know why this error would be occurring?
134 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FBB
143 10:20:56 mobsync.exe:2244 FASTIO_DEVICE_CONTROL \Device\LanmanRedirector
FAILURE IOCTL: 0x140FCF
150 10:20:56 mobsync.exe:2244 FASTIO_DEVICE_CONTROL \Device\LanmanRedirector
FAILURE IOCTL: 0x140FBB
155 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FCF
162 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FBB
167 10:20:56 explorer.exe:3524 FASTIO_DEVICE_CONTROL
\Device\LanmanRedirector FAILURE IOCTL: 0x140FCF
168 10:20:56 mobsync.exe:2244 FASTIO_DEVICE_CONTROL \Device\LanmanRedirector
FAILURE IOCTL: 0x140FCF
Another error the user is getting, is that once the system has eventually
loaded, and they get a problem with explorer, where it will hang, usually
permentally (we've left it for at least an hour and it's never come back),
using filemon (I don't have an example log at the moment) it looks like
explorer is trying to access "H:\<username>\\shell32.dll" which is strange,
firstly because shell32.dll is located in %systemroot%\system32. Secondly,
the users H: drive is mapped to \\server\home\<username> and this seems to
be looking for another folder called <username> user the already mapped H:
drive. I've used regmon to look though the registry and filter for
H:\<username> but nothing shows up, I also filtered for shell32, and that
only shows up as %systemroot%\system32
Can anyone suggest why LanmanRedirector is causing a problem, and why
explorer would be trying to access a non existent folder?
Cheers
Ben