MS Firewall

UAG: MS Firewall does not start and stays in "starting" state in nUAG Appliance

Posted Thu, 06/17/2010 - 06:59 by inder

On few occassions you may encounter an issue wherein the nUAG appliance when started and joined to the domain for the first time will take long time to start and when it starts the MS Firewall service stays in "starting" state. This problem occurs mostly when user has not followed the quick start guide properly and continued with the steps one after the other. Two ways to resolve it;

#1 If you have already configured the nUAG appliance and now the MS Firewall service is not starting.

Iron Networks is an OEM provider of software-defined converged network, compute & storage virtualization infrastructure platforms for cloud-optimized modern data centers. The IronPOD solutions are OpenStack, VMWare and Microsoft Fast-Track validated turnkey cloud and storage building blocks, built on industry standard commodity hardware, quick to deploy at large-scale and easy to distribute as a single low-cost rack level SKU. IronPOD enterprise level support services and systems are available via qualified partners globally to help enterprises efficiently build private cloud environments, and service providers build public cloud offerings.

sales@ironnetworks.com +(1) 877-895-6277

Managed Private & Hybrid Clouds, Branches and Devices SolutionsMicrosoft Azure Cloud, Infrastructure-as-a-Service (IaaS), System Center & Mobility Deployment Experts!

Subscribe by email

Blog Category

MS Firewall

UAG: MS Firewall does not start and stays in "starting" state in nUAG Appliance