New error when trying to run BES Client Deployment Wizard

(imported topic written by Marty23)

I just started getting the following status message when I try to push out the BES Client using the Deployment Wizard and I can’t find any inforation in the Knowledge base.

“No network provider accepted the given network path.”

Can someone tell me what this means?

(imported comment written by brolly3391)

Marty,

This generic error usually means that either the network cannot resolve machine name to IP or that the machine is turned off or otherwise unreachable through the network at this time.

Try pinging the machine. If it does not respond, chances are that the deployment tool will not be able to see it either.

Cheers,

Brolly

(imported comment written by ErnieF91)

We see this message when the Forward DNS record does not match the Reverse Lookup record. Try pinging the name and then use the results in a “ping -a” command.

(imported comment written by BenKus)

Hey guys,

The BES Client Deployment Tool relies on Windows RPC communication, which is often problematic for various reasons. We have found that the Microsoft “RPC Ping” tools are particularly handy at isolating RPC issues: http://support.microsoft.com/kb/167260/EN-US/

Ben

(imported comment written by Doug_Coburn)

Hey Marty,

This error message is actually being thrown out by Windows and the BES Client Deploy Tool is just showing the output. Generally when I see this error message it is because the computer you are running the tool can not contact the Domain Controller correctly or no information on that hostname is registered with the DC.

I found a website with some tips on how to resolve this problem

http://www.chicagotech.net/troubleshooting/systemerror67.htm

Doug

(imported comment written by Bjowah91)

Marty,

If your using a Microsoft dynamic DNS you must perhaps apply ageing on the subnets. We have had some problems when clients are not correctly shutdown and they don’t unregister their names from DNS. If DHCP now gives the ip address of the client to a new machine the DNS record is updated with the new name but the old is still in the DNS database and you end up with dubbel entries. If you do a name lookup on the machine now you will have a round robin effect in the answer.

We have therefor set the ageing to saven days to clean up old records in DNS.