Greetings,
My knowledge about drivers, including filter drivers, is reasonably
good. My knowledge about network file system drivers (redirectors) is
pretty basic.
I have inherited a network file system driver that is behaving poorly
with “NET USE …” and with Windows Explorer “Map Network Drive…”
On XP:
Either mapping method works. The drive letter becomes usable. When I
unmap, the driver letter goes away but is not removed from the system.
NET USE shows that it’s still there. I am unable to re-map because it’s
still in use.
On Server 2008:
Both mapping methods work (sort of) but if I use one, say NET USE, I
don’t see the effect in Windows Explorer. The reverse is also true. I
believe the failure to go away exists here as well.
Can some kind person fill in the blanks:
“You need to go look at the code associated with the _______ function.
Or maybe the ______ function.”
I will then go do my homework and come back if I get stuck.
Thank you,
Mickey.
This is not my thing, but the behavior you’re describing on W2K8 is
normal, albeit incredibly irritating. That is, mapping via ‘NET USE’
does not result in a driver appearing in Explorer, at least in my
experience; not sure about the other direction.
Good luck,
mm
Mickey Lane wrote:
Greetings,
My knowledge about drivers, including filter drivers, is reasonably
good. My knowledge about network file system drivers (redirectors) is
pretty basic.
I have inherited a network file system driver that is behaving poorly
with “NET USE …” and with Windows Explorer “Map Network Drive…”
On XP:
Either mapping method works. The drive letter becomes usable. When I
unmap, the driver letter goes away but is not removed from the system.
NET USE shows that it’s still there. I am unable to re-map because it’s
still in use.
On Server 2008:
Both mapping methods work (sort of) but if I use one, say NET USE, I
don’t see the effect in Windows Explorer. The reverse is also true. I
believe the failure to go away exists here as well.
Can some kind person fill in the blanks:
“You need to go look at the code associated with the _______ function.
Or maybe the ______ function.”
I will then go do my homework and come back if I get stuck.
Thank you,
Mickey.
Martin O’Brien wrote:
This is not my thing, but the behavior you’re describing on W2K8 is
normal, albeit incredibly irritating. That is, mapping via ‘NET USE’
does not result in a driver appearing in Explorer, at least in my
experience; not sure about the other direction.
Good luck,
Interesting and yes, irritating.
When I map the letter using Windows Explorer, I do see the drive letter
but I also see a red X indicating it’s not functional. I can sometimes
see directories and files on the other end of the connection. (Server
2008 only)
Thanks,
The rest of it is not my department.
Good luck,
mm
Mickey Lane wrote:
Martin O’Brien wrote:
> This is not my thing, but the behavior you’re describing on W2K8 is
> normal, albeit incredibly irritating. That is, mapping via ‘NET USE’
> does not result in a driver appearing in Explorer, at least in my
> experience; not sure about the other direction.
>
>
> Good luck,
>
Interesting and yes, irritating.
When I map the letter using Windows Explorer, I do see the drive letter
but I also see a red X indicating it’s not functional. I can sometimes
see directories and files on the other end of the connection. (Server
2008 only)
Thanks,
Mickey Lane wrote:
Greetings,
My knowledge about drivers, including filter drivers, is reasonably
good. My knowledge about network file system drivers (redirectors) is
pretty basic.
I have inherited a network file system driver that is behaving poorly
with “NET USE …” and with Windows Explorer “Map Network Drive…”
This is almost all related to the network provider. It is a problem in
the connected, context and globalnet enumerations not correctly being
processed as well as others functions in the NP dll not being
implemented. Of course, almost zero documentation exists but there are
tid bits thrown around in the SDK and WDK docs.
Of course, every redirector is different so make no assumptions about
how things are handled in the sample providers vs. how they should be
handled in the np you have.
Pete
On XP:
Either mapping method works. The drive letter becomes usable. When I
unmap, the driver letter goes away but is not removed from the system.
NET USE shows that it’s still there. I am unable to re-map because it’s
still in use.
On Server 2008:
Both mapping methods work (sort of) but if I use one, say NET USE, I
don’t see the effect in Windows Explorer. The reverse is also true. I
believe the failure to go away exists here as well.
Can some kind person fill in the blanks:
“You need to go look at the code associated with the _______ function.
Or maybe the ______ function.”
I will then go do my homework and come back if I get stuck.
Thank you,
Mickey.
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295