<div>Yup Ryan you rock that's what it was...I had the proxy host name configured to something that didn't resolve the way my dns was setup. Let me ask you should the proxy host name resolve the the rfc 1918 address or the public address from the cuma server point of view?</div>
<div> </div>
<div>Dane<br><br></div>
<div class="gmail_quote">On Thu, Dec 3, 2009 at 12:36 PM, Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Did you really name your CUMA server localhost?<br><br>The only time I've seen that before is with CUCM servers when you enable DHCP on the server and it can't pull a hostname from DNS or the DHCP server. The platform will set localhost to the hostname and this breaks all kinds of things.<br>
<br>The most common cause of the managed service not starting is that the "Proxy Host Name" won't resolve via DNS. Check System Management->Network Properties.<br><br>-Ryan<br>
<div class="im"><br>On Dec 3, 2009, at 12:28 PM, Dane Newman wrote:<br><br>As shown in the screen shot the managed server service wont start up. I have went through each of the enterprise adapters and verified each one is working correctly with the test button. I have even tried deleting them to get it to come up but it refuses to come up. Does anyone have any advice?<br>
<br>Dane<br></div><start.jpg>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>