topic SnapDrive RPC error SME DFM possible .Net issue in Network and Storage Protocols https://community.netapp.com/t5/Network-and-Storage-Protocols/SnapDrive-RPC-error-SME-DFM-possible-Net-issue/m-p/4732#M457 <HTML><HEAD></HEAD><BODY><P>We've run into a major SnapDrive issue.&nbsp; Our department recently move some filers from one datacenter to another.&nbsp; With the new datacenter came new Ip addresses and new names for the filers.&nbsp; Servers were also move but have kept the same IP addresses and names.&nbsp; The filers are now on a different subnet from the servers but can talk.&nbsp; The LUNs connect fine to the server and there is no issue there but we cannot manage the LUNs at all.&nbsp; Here is the error we are getting.</P><P></P><P><IMG src="http://community.netapp.com/legacyfs/online/18962_snapdrive_error.png" width="450" /></P><P>Snapdrive is pointing to the old IP address for e0M.&nbsp; We have updated preferred IP, deleted all DNS records of the old names/IP's, run cifs setup with new names, edited host files, uninstalled, reinstalled snapdrive and .net, rebooted and called Support.&nbsp; Two days of troubleshoooting and SnapDrive still points to old IP when it wants to use zapi via RPC, HTTP or HTTPS.&nbsp; In fact,&nbsp; If I try to run snapdrive from any server to this filer it fails.</P><P></P><P>The issue is with the filer or the DFM server.</P><P></P><P>We have a clustered exchange environment and all servers use DFM for RBAC controlled backups.</P><P></P><P>Any ideas?&nbsp; Has anyone ever seen this before?</P></BODY></HTML> Thu, 05 Jun 2025 06:09:07 GMT CASTROJSEC 2025-06-05T06:09:07Z SnapDrive RPC error SME DFM possible .Net issue https://community.netapp.com/t5/Network-and-Storage-Protocols/SnapDrive-RPC-error-SME-DFM-possible-Net-issue/m-p/4732#M457 <HTML><HEAD></HEAD><BODY><P>We've run into a major SnapDrive issue.&nbsp; Our department recently move some filers from one datacenter to another.&nbsp; With the new datacenter came new Ip addresses and new names for the filers.&nbsp; Servers were also move but have kept the same IP addresses and names.&nbsp; The filers are now on a different subnet from the servers but can talk.&nbsp; The LUNs connect fine to the server and there is no issue there but we cannot manage the LUNs at all.&nbsp; Here is the error we are getting.</P><P></P><P><IMG src="http://community.netapp.com/legacyfs/online/18962_snapdrive_error.png" width="450" /></P><P>Snapdrive is pointing to the old IP address for e0M.&nbsp; We have updated preferred IP, deleted all DNS records of the old names/IP's, run cifs setup with new names, edited host files, uninstalled, reinstalled snapdrive and .net, rebooted and called Support.&nbsp; Two days of troubleshoooting and SnapDrive still points to old IP when it wants to use zapi via RPC, HTTP or HTTPS.&nbsp; In fact,&nbsp; If I try to run snapdrive from any server to this filer it fails.</P><P></P><P>The issue is with the filer or the DFM server.</P><P></P><P>We have a clustered exchange environment and all servers use DFM for RBAC controlled backups.</P><P></P><P>Any ideas?&nbsp; Has anyone ever seen this before?</P></BODY></HTML> Thu, 05 Jun 2025 06:09:07 GMT https://community.netapp.com/t5/Network-and-Storage-Protocols/SnapDrive-RPC-error-SME-DFM-possible-Net-issue/m-p/4732#M457 CASTROJSEC 2025-06-05T06:09:07Z Re: SnapDrive RPC error SME DFM possible .Net issue https://community.netapp.com/t5/Network-and-Storage-Protocols/SnapDrive-RPC-error-SME-DFM-possible-Net-issue/m-p/4737#M458 <HTML><HEAD></HEAD><BODY><P>Solved!&nbsp; The issue was with the accesscontrol file.&nbsp; Our SME backups use DFM for RBAC contol.&nbsp; The old accesscontrol files still had the old ip's.&nbsp; I used storacl.exe to update the files.&nbsp; Issue gone.&nbsp; Backups working.</P></BODY></HTML> Wed, 27 Feb 2013 20:35:57 GMT https://community.netapp.com/t5/Network-and-Storage-Protocols/SnapDrive-RPC-error-SME-DFM-possible-Net-issue/m-p/4737#M458 CASTROJSEC 2013-02-27T20:35:57Z