DFS Protocol Details

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael B Allen wrote:

> I'm seeing some DFS behavior that I cannot explain. Instead 
> of the usual try > PATH_NOT_COVERED > referral > try w/ new
> target style protocol, captures show that the clients already
> know the target is in DFS. At first I thought operators simply
> were not capturing the PATH_NOT_COVERED part
> but now I think there must be some additional protocol. 
> Does anyone know how these clients populate their DFS mappings?
> What am I missing here?

Are you sure the client is not just caching the information?
There's some dfs management rpcs, but I haven't looked at
those.  It's possible I suppose that the clients could also
get the dfs topology from AD.

Don't know if this helps or not.



cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDA25UIR7qMdg1EfYRAhftAJ9jyML3ZCCVe6dt2N+8ocgJksqvqACfUqj2
BhoZ4JVV/IhbvbLV01IlSyE=
=xgPR
-----END PGP SIGNATURE-----