LanMan shares disappear on reboot

NTFSD
1

I’m having a problem with shares being persistent across reboots
with my fsd.

The drives for my FSD can be shared (say via explorer), but when I
reboot, sometimes (but not always) I don’t get the “hand” icon, nor
does the share show up via ‘net share’. I can see that the share
exists in the registry as hklm/ccs/services/lanmanserver/shares.

The FSD requires some lengthy TCP communication to mount, so it can take
a while for the filesystem to actually become active. However, the
handling of IRP_MOUNT_VOLUME happens quickly at boot time. The “real”
mount of
the filesystem is deferred until all the network connections are up.
I’m thinking that I’m in some sort of race; when the decision as to
whether
a drive is activate or not is made, my FSD is still initializing so
Lanman gives up on the FSD and doesn’t bother to mark the drive as
shared.

Short of walking through lanmanserver/shares and re-exporting shares
that
are for my FSD, anyone have any ideas as to why this might be happening?

Thanks.

2

SRV will not restore the share if the path is not available. Hence, you ARE
in a race condition.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Peter Lawthers [mailto:xxxxx@lawthers.com]
Sent: Tuesday, May 21, 2002 4:45 PM
To: File Systems Developers
Subject: [ntfsd] LanMan shares disappear on reboot

I’m having a problem with shares being persistent across reboots
with my fsd.

The drives for my FSD can be shared (say via explorer), but when I
reboot, sometimes (but not always) I don’t get the “hand” icon, nor
does the share show up via ‘net share’. I can see that the share
exists in the registry as hklm/ccs/services/lanmanserver/shares.

The FSD requires some lengthy TCP communication to mount, so it can take
a while for the filesystem to actually become active. However, the
handling of IRP_MOUNT_VOLUME happens quickly at boot time. The “real”
mount of
the filesystem is deferred until all the network connections are up.
I’m thinking that I’m in some sort of race; when the decision as to
whether
a drive is activate or not is made, my FSD is still initializing so
Lanman gives up on the FSD and doesn’t bother to mark the drive as
shared.

Short of walking through lanmanserver/shares and re-exporting shares
that
are for my FSD, anyone have any ideas as to why this might be happening?

Thanks.

You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%

3

Try to restart lanmanserver service after your drives are mounted.

If the shares are in registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares

and your drives are accesible, the service will create them.

Kristian