Do you have the appropriate credentials configured as part of the WAFS Core Cluster group?
What OS is the file server running you are trying to access?
Assuming the credentials are configured correctly and you are accessing a Microsoft server, see CSCsg79612 for a potential issue.
Yes, I tested the credentials with the windows-domain diagnostics wbinfo "-a Username%Password" command succesfully.
I'm using Windows Server 2003 SP1.
I've applied this patch described in this article. I will uninstall it and test again.
I've deployed in the wild and the only issue I know of is on domain controllers with the digital signing of SMB connections always (I think should be off), this was always the issue wafs as well. I was advised to set the username and password for accessing the server and then you can browse from within the GUI.
Not sure if that helps but we had it working with 4-0-1 ok.
I believe this problem is caused by Bug CSCsg76670 (solved in release train 3, build 3.0.9, but not yet in release 4).
Workaround can be temporary remove Microsoft patch MS06-063 (923414) from file servers (C:\WINDOWS\$NtUninstallKB923414$\spuninst\spuninst.e
Does anyone know when will come a build of WAAS 4 solving BUG CSCsg76670?
Did anyone ever come up with a solution to this problem? I am currently using the latest IOS and still get the same error message. I can not browse the file server. Is enabling WINS on the domain a requirement for this to work?
The bug referenced in my previous post was resolved in the WAAS 4.0.7 release.
Have you tried including the domain name in the credentials you configure on the WAFS Core Cluster?
Thanks for your response. Yes, I did add the domain name to the credentials and it still didn't work. Also, I just noticed that when I do a show tfo conn summ on the core WAE, the output gives a remote IP of the core and a local IP of the egde WAE. Am I missing anything here?
Would it be possible for you to provide a packet capture from the WAFS Core when this browsing takes place? You can email the capture to email@example.com if you don't want to post it here.