DFS Protocol Details

[Don McCall]

Hi Michael,
Some (most MS) clients do dfs referral cacheing.  I have seen this before myself.  In fact some older clients cache persists even AFTER a local client logoff - see MSKB article: 
http://support.microsoft.com/default.aspx?scid=kb;en-us;327408
 
So if the client already has the dfs share cached, it will go straight to the target, and you won't see the PATH_NOT_COVERED...
Hope this helps,
Don
Michael B Allen <mba2000 at ioplex.com> 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?

Thanks,
Mike

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com