Re: [WinMac] NTserver4.0 drops mac shares occasionally: Help!
Dan Schwartz(expresso[at]snip.net)
Wed, 17 Mar 1999 12:21:56 -0500
Hello, Bob!
I've seen this before, and the "root" of your problem is just that: Making
the root level of the volume MacFile available. First off, it's lousy for
security; and secondly this can cause the problems you are seeing.
Here's how to fix this:
1) Shut down File Server for Macintosh;
2) Create a single folder at the root level of the NTFS volume with the
same share name as the SFM share name as the root level SFM volume;
3) Move all the files and folders (except the one created above) from the
root level to this new Folder;
3) Restart File Server for Macintosh and then share this single folder. It
will take a few minutes to rebuild the Desktop files (which is good), and
you can watch the progress in the Event Viewer.
This trick is brought to you by NT's Native Transactional File System's
streaming capability: Whether or not Services for Macintosh is enabled, you
can move and copy Mac files from one NTFS location to another *on the same
machine* because NTFS preserves the two streams used for handling the dual
fork Mac files.
Yours truly,
Daniel L. Schwartz,
Electrical Engineer.
Dan's Macintosh Consulting
239 Great Road
Maple Shade, NJ 08052
609-642-7666
-----------------------------------------------------------------
At 09:14 PM 3/16/99 -0500, you wrote:
>
>This is a problem that has been nagging us for months without solution.
>We are running NT server 4.0 sp3 on a workgroup. Occasionally, the macs
>lose connection to the server, which has shared an entire drive for the macs
>to see. After it happens, when you look at the volumes menu option in the
>Macfile menu on the server, the directory that was shared is there but it
>has a line through it. (Its no longer available on the network).
>
>It can be deleted, but if a new share is created, we get some message like:
>One or more devices is not working. Rebooting the server brings the shares
>back, but stopping and starting file services for mac does not.
>
>The most recent time it happenned, we did in fact accidentally turn off a
>hub then turn it back on. The hub is connected via thinnet and I know
>thinnet can cause floosiness in a network (we are getting rid of it soon).
>But to the best of our knowledge the problem has occurred in the past with
>no wiring or other network disturbances. Any ideas?
>
>thanks,
>bob
-----------------------------------------------------------------
<mailto:expresso@snip.net, Dan@Hemnet.com>
ALTERNATE: <mailto:expresso@workmail.com>
Webmaster for <http://www.faulknerstudios.com>
**Your Corel Solution Partner**
**Your UltraBac Solution Source**
-----------------------------------------------------------------
* Windows-MacOS Cooperation List *
This archive was generated by hypermail 2.0b2
on Wed Mar 17 1999 - 11:16:25 PST
|