Network share failover...

Here's the information.

I have a User Share we'll call Shared on one server (Win2k3) we'll call
Server1
All clients are running XP.
We have a second server (Win2k3 Server2) that will share the files being
served by
Server1 in the event of a server failure.

We have a CNAME Alias that points to active server sharing the files (we'll
call
FS1).

The issue is that when we have tested the failover to Server2 and repoint
the FS1 record to Server2 (TTL is set to 1 minute on the CNAME Alias) the
users who had been accessing \\FS1\Shared get the updated IP address so that
FS1 resolves to Server2 but if they try to access \\FS1\Shared that traffic
is going to Server1.

Now I am not sure why this is. The old DNS name/IP Address is being cached
somewhere on the client. I tried changing the setting "net config server
/autodisconnect:-1" to see if that had any effect, and it doesn't. And doing
"ipconfig /flushdns" has no effect either. At this point we can't implement
clustering and I would like to get this failover to work.

Does anyone have any ideas what is causing this and if there is a
workaround/fix?

Not sure but do you have a WINS Server? Seen similar stuff when using WINS
and DNS. DNS will update but WINS might still point to old IP

"Joe" wrote:

> Here's the information.
>
> I have a User Share we'll call Shared on one server (Win2k3) we'll call
> Server1
> All clients are running XP.
> We have a second server (Win2k3 Server2) that will share the files being
> served by
> Server1 in the event of a server failure.
>
> We have a CNAME Alias that points to active server sharing the files (we'll
> call
> FS1).
>
> The issue is that when we have tested the failover to Server2 and repoint
> the FS1 record to Server2 (TTL is set to 1 minute on the CNAME Alias) the
> users who had been accessing \\FS1\Shared get the updated IP address so that
> FS1 resolves to Server2 but if they try to access \\FS1\Shared that traffic
> is going to Server1.
>
> Now I am not sure why this is. The old DNS name/IP Address is being cached
> somewhere on the client. I tried changing the setting "net config server
> /autodisconnect:-1" to see if that had any effect, and it doesn't. And doing
> "ipconfig /flushdns" has no effect either. At this point we can't implement
> clustering and I would like to get this failover to work.
>
> Does anyone have any ideas what is causing this and if there is a
> workaround/fix?