Hi, Ben
For existing connections, if the client was originaly connected to the bad
server, any attempt to read or write will fail:
"DFS failover is only performed when a client opens a file or folder. If a
client has files or folders open and attempts to read or write to them when
the target server is unavailable, the application will receive a failure on
that operation. "
from technet:
http://technet2.microsoft.com/window....mspx?mfr=true
For new connections it should failover. I found some information on technet.
Hope it helps to figure out the problem...
http://technet2.microsoft.com/window....mspx?mfr=true
http://technet2.microsoft.com/window....mspx?mfr=true
(info on some failover options introduced in SP1)
--Malu
"Ben L" <> wrote in message
news:88e385d3-0ca9-4d59-9ae5-...
> Is there an information about dfs fail over? If one server is down
> hosting a dfs folder, how can I force all client connections to choose
> the other redundant server?
>
> \\domain\user\share1 -> \\server1\share01$
> \\domain\user\share1 -> \\server2\share01$
>
> win2003r2 enterprise for both servers.
>
> Currently, both existing and new connections choose the failed server
> and result in either "storage not available" or "permission denied"
> errors.
>
> I should point out, that in the latest failure, server1 didn't go down
> completely, but the dfs service shutdown, and required a restart of
> the server service.
>
> Any advice?
>
> Ben.