The fact that you can't ping your DNS/ Domain controller from the the vFiler, if its running in the default ipspace, is why your CIFS setup fails. You need the vFiler to be able to connect the DC to join the domain..
Hi Vijay, ok. well it looks like a config/network config issue. At a guess I would say you are using multi VIF's, or are you using LACP.
You need to amend the setup of NAS01 and either create the IPSpace add it to the vFiler and setup the routing.. or assign the correct routing to interface VIF1-31, tag it with the correct VLAN and IP address and then make sure that the physical NIC's used in this VIF are connected to the correct ports on your switch and that the ports on the switch are in the correct VLAN's and then test. Also if you are using a HA cluster for the vFiler's then you need identical/correct RC and Network configs otherwise if NAS01/NAS02 performs a takeover, then it will fail. Make sure the config is manually added to each RC file if needed.
If your network guys can see the traffic from VIF1-31, using the current config.. and you can PING the default gateway of this network/VLAN from the CLI of vFiler, then the routing on the vFiler is correct and your network guys need to trace where they have the traffic routing to!
Re-run the vFiler config wizard, through FilerView and reconfigure it to use the correct interface. This is the easiest way to do this, as I have spent many hours doing it by the CLI and Filerview is faster for some things.
Once that is done, your vFiler should be using the correct interface in the correct default IP space.
After that check the config of the interface and the VLAN's. If they are correct, and the vFiler Routing table is correct, get your Network guys to check the switchport config... and run pings and traceroutes from the vFiler.
These are the only things that generally affect the vFiler connectivity after spending a while working with them.. If this doesnt work, delete it and start again from a fresh and check configs and spelling/typo's, IP's or incorrect sub net masks..
hmm.. either way, you could just delete the vFiler and recreate a new from scratch, new vol0 for the vFiler etc.. or re run the vFiler wizard and change the interface, delete all the routes in the vFiler routing table and try again.
if neither work, there must be a real BURT with your version of ONTAP perhaps.