Wow. Way to insult one of the most knowledgeble, and helpful, contributors to this list.
You keep saying it is DFS, but then you state that connecting to the FQDN or IP does the same thing. So yes, semantics is important. If you see the problem via FQDN you are bypassing DFS. So the problem is not DFS. Ken is right - there is no "fix" until the underlying root cause is identified. On Thu, Jul 9, 2009 at 11:34 AM, Steph Balog <[email protected]> wrote: > (quoting Ken below) > > Ken (you dont happen to work at a university do you?) > > I did use wireshark, I was using wireshark when it was ethereal, and > probably using it long before most on this list have been working. I HAVE > stated the issue. Windows XP and 2003 clients are experiencing slow > connectivity to shares on a windows 2008 server. Regardless of whether it is > through dfs or not. Windows vista client and windows 7 clients do not. > The issue looks to be a a client one. Perhaps something to do with how the > OLDER client handle talking smb to the NEWER server. That is the ISSUE KEN. > My question was if ANYONE has seen such an issue. There is an ISSUE KEN. > > And fyi, wireshark did not show me anything but smb traffic being initiated > the server responding, and then nothing. It didnt show errors, it didnt show > drops. It is not a network issue, it is not a traffic issue. So again KEN, > unless you can add something useful to this conversation, please refrain > from your semantics. And hopefully someone else may have experienced this > and can offer me some isight. > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
