Win 2000 Cluster: Lose drive mapping during a reboot. Help!

[Branden Willis]

Okay, simply put, we are running into a problem where we lose our
drive mappings when we reboot a node of our cluster. When the node
comes back up we do a failover to move the resource groups back to the
desired node, but the drives do not show up in Windows Explorer. The
physical drives still appear in Disk Management, and are still
accessible via UNC connection (\\servername\sharname). Plus Exchange
is still functioning. So the drives are still working.
If the second node of the cluster is rebooted and the resources
moved there, the problem duplicates itself on that node. The only way
to restore the drive mappings is to completely shut down the cluster
and then bring it back up. These servers are in production, so
repeatedly bringing the cluster all the way down is something that we
can't be doing all the time.
Its a Windows 2000 SP4, 2-node cluster. Exchange 2000 SP3 is
running on the cluster, and both nodes are also DC's. There is
anti-virus software installed, but this problem began happening before
that software was installed. I have scoured the MS knowledge base
looking for answers, and didn't find anything useful. Help!

 

[Russel Rodenbeck]

Branden:
I'm running into the exact same issue. Did you find a solution, other
than restarting the whole cluster?

Russel

 

[Russel Rodenbeck]

Brandon:
In my case, it was just a terminal server issue. As you described,
the drives were owned by the node, but couldn't be seen.
I logged out of Terminal Server and then reconnected. The drives now
are visible.

Russel

 

[Branden Willis]

Russel,
Yeah, that ended up being the problem with us too. A coworker
swore that he tried reconnecting to Terminal Server, so I didn't
double check that solution.