Re: Mapped drives in clients lost when server down
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 Jan 2006 22:40:10 -0500
"Augie" <Augie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D2821D4E-17DA-4846-A826-4A3047D86DA2@xxxxxxxxxxxxxxxx
> Thanks, Jossie_2k, I shall give it a try.
> You are right, the server should not go down. But when testing I found
> this
> problem and the whole system became dependent on one computer, the server.
> And that was not the purpose, when I decided to change the concept from
> using
> workgroups to domains.
> A client workstation can always be replaced by one of the others, there
> are
> at least two that are at least two doing exactly the the same tasks.
> And the mapped drives are all in the client workstations. The clients
> save/fetch data to/from SQL and get user policies, but that is all.
Up to you of course...but rather than relying on eventually error-prone IDE
hard drives in a bunch of workstations with data scattered around them all,
I'd rather invest in good quality server hardware with hardware SCSI RAID,
dual power supplies, etc., store any data I cared about on it only, do
regular backups of everything, and treat workstations as interchangeable
objects that don't matter all that much when they crash or die.
>
>
> "Jossie_2k" wrote:
>
>> First : A server is not suspected to go down regular ....
>>
>> If I understand the situation, the network-drives are not on the server,
>> but
>> on other clients.
>>
>> What you can try, is mapping this drives using a small batch-file (Net
>> Use
>> [driveletter] [networkpath ex. \\computername\share]), and let this batch
>> run at every logon on a client computer. This can be done using a
>> shortcut
>> to this batch in the startup-folder, or by using sheduled tasks.
>>
>> (A batch-file you can create in Notepad, and save it with extension
>> *.bat)
>>
>> Hope this was helpfull.
>>
>>
>>
>> "Augie" <Augie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:23B691BA-4788-4292-980E-C4625FB12D60@xxxxxxxxxxxxxxxx
>> >I am fairly new to Windows Server and, as I have not got any formal
>> >training,
>> > run into minor problems from time to time.
>> > Now I have a small network, one 2003 SP1 server, with Acitive directory
>> > and
>> > DNS only, and 10 XP SP2 clients connected. The clients have network
>> > drives
>> > mapped to the other client's disks. This works fine as long as the
>> > server
>> > is
>> > on, but all network drives in the clients are lost if the server goes
>> > down.
>> > In this process application the server is only used to host a SQL
>> > server
>> > and
>> > make maintaining of user rights and desktops easier in the clients. It
>> > can
>> > be
>> > down without causing any bigger harm as long as the clients can log in
>> > and
>> > use the mapped drives. But the clients (or at least any 3 of them at
>> > any
>> > time) must work, and be able to access each other, no matter if the
>> > server
>> > is on or not.
>> > The whole network is isolated from the outer world, no plant network
>> > or
>> > internet is needed. I have tried to minimize the the security so far,
>> > everything is allowed.
>> > What could I do to make the network drives work in all situations?
>> >
>> > Regards
>> >
>>
>>
>>
.
- References:
- Re: Mapped drives in clients lost when server down
- From: Jossie_2k
- Re: Mapped drives in clients lost when server down
- Prev by Date: Re: Time Server [WildPacket]
- Next by Date: Re: MSDTC error when mocing FSMO ROLES
- Previous by thread: Re: Mapped drives in clients lost when server down
- Next by thread: Re: Mapped drives in clients lost when server down
- Index(es):
Relevant Pages
|
