Multiple SNAC Network Providers causes beremote to crash when trying to expand the resources of a remote server

Article:TECH73013  |  Created: 2009-01-31  |  Updated: 2010-01-04  |  Article URL http://www.symantec.com/docs/TECH73013
Article Type
Technical Solution


Environment

Problem



Multiple SNAC Network Providers causes beremote to crash when trying to expand the resources of a remote server

Error



An error was encountered while attempting to browse the contents of . A network connection to the server could not be established.

Solution



With SEP installed on a remote server that you intend to backup, you may observe the above error message shown in Figure A when attempting to expand the remote server's resources in a new backup job selection list.
[Figure A]:
 

You may also observe on the remote machine the following crash of the Remote Agent for Windows Servers service (beremote.exe) in ntdll.dll or bedscomn.dll as shown in the event ID in Figure B:
[Figure B]:
 

As a preliminary step, check the steps mentioned in Technote article 303025 in the "Related Documents" section of this page, so that connectivity issues, port issues/conflicts, and possible conflicting 3rd party applications can be eliminated. If after doing so the problem persists, then please check the following two registry keys named "HwOrder" and "Order":
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NetworkProvider\HwOrder
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NetworkProvider\Order
Upon checking the value of the ProviderOrder registry key in each of the above keys, you may find numerous "SnacNP" entries as shown in [Figure C]:
[Figure C]:
 
The actual value may display the "SnacNP" entry up to, and possibly more than 61 times. An example of an incorrect registry key can be seen below:
SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,SnacNp,RDPNP,LanmanWorkstation,WebClient
Compared with a normal entry on another server with SEP installed, the following should be seen:
RDPNP,LanmanWorkstation,WebClient

[RESOLUTION]:
Schedule some downtime for the affected remote server, remove all "SnacNP" entries, and restart the server.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes
  • 1: On the remote server, open the Windows Registry Editor
  • 2: Modify the value of the ProviderOrder registry key located in the HwOrder and Order locations (see above) to show the following: RDPNP,LanmanWorkstation,WebClient
  • 3: Restart the server
Afterwards, attempt again to browse the remote server's resources.



Legacy ID



329199


Article URL http://www.symantec.com/docs/TECH73013


Terms of use for this information are found in Legal Notices