|
Home > Archive > microsoft.public.exchange2000.admin > August 2002 > e2k clustering
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| I'm currently running my e2k in a cluster --
active/passive. When I do a failover, the shared drives
(q:[quorum], d:[e2k data], and m:[exchange's virtual
drive]) sometimes doesn't show up in windows explorer --
even after hitting refresh. I can't even get to those
drives in a command prompt. Though it doesn't seem to be
causing a problem, atleast not to my knowledge, is this
normal?? There are no errors reported in the event log. I
haven't failed over for awhile and don't really think its
a good idea to do it just to test it. Just wondering if
anyone seen this before and does it cause any problems???
Also, I know I should run to log files in another shared
drive but that will come at a later time since budgeting
is an issue right now. Thanks!
| |
| Simon Walsh 2002-08-14, 3:23 am |
| Are you using Terminal Services?
If so there is a known issue with drive letters and TS.
S
"john" <john@jjj.com> wrote in message
news:220e01c2435c$5e065240$3ae
f2ecf@TKMSFTNGXA09...
> I'm currently running my e2k in a cluster --
> active/passive. When I do a failover, the shared drives
> (q:[quorum], d:[e2k data], and m:[exchange's virtual
> drive]) sometimes doesn't show up in windows explorer --
> even after hitting refresh. I can't even get to those
> drives in a command prompt. Though it doesn't seem to be
> causing a problem, atleast not to my knowledge, is this
> normal?? There are no errors reported in the event log. I
> haven't failed over for awhile and don't really think its
> a good idea to do it just to test it. Just wondering if
> anyone seen this before and does it cause any problems???
> Also, I know I should run to log files in another shared
> drive but that will come at a later time since budgeting
> is an issue right now. Thanks!
| |
|
| Yes, I'm using terminal services when I noticed this.
Would I see the shared drives if I actually logged on
using the console itself?
>-----Original Message-----
>Are you using Terminal Services?
>If so there is a known issue with drive letters and TS.
>
>S
>"john" <john@jjj.com> wrote in message
> news:220e01c2435c$5e065240$3ae
f2ecf@TKMSFTNGXA09...
>> I'm currently running my e2k in a cluster --
>> active/passive. When I do a failover, the shared drives
>> (q:[quorum], d:[e2k data], and m:[exchange's virtual
>> drive]) sometimes doesn't show up in windows explorer -
-
>> even after hitting refresh. I can't even get to those
>> drives in a command prompt. Though it doesn't seem to
be
>> causing a problem, atleast not to my knowledge, is this
>> normal?? There are no errors reported in the event
log. I
>> haven't failed over for awhile and don't really think
its
>> a good idea to do it just to test it. Just wondering if
>> anyone seen this before and does it cause any
problems???
>> Also, I know I should run to log files in another
shared
>> drive but that will come at a later time since
budgeting
>> is an issue right now. Thanks!
>
>
>.
>
|
|
|
|
|