MOSS 2007 Central Admin inaccessible?
Hi, For no apparent reason, I cannot access Central Admin for my farm any more...I get a DNS error, even while on the console of the central admin machine. Trying FQDN, servername and "localhost" all returns the same error. The site is running, but cannot be browsed via IIS. Please help!!! cheers, Steve.
July 2nd, 2010 2:40am

Update is, I've managed to access the site via: http://localhost:30976/default.aspx but still doesn't work with http://<hostname>:30976 anyone have any idea why? DNS for the host is fine (it can resolve the name to itself) ???? thanks, Steve.
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2010 3:51am

Being able to access the site via default.aspx but not without is often the result of faulty AAM (Alternate Access Methods) settings. make sure that your default site in AAM is set to http://servername:30976 (AAM is accessible via Central Admin; Operations and then its in the right-hand column2010 Books: SPF 2010; SPS 2010; SPD 2010; InfoPath 2010; Workflow etc. 2007 Books: WSS 3.0; MOSS 2007; SPD 2007; InfoPath 2007; PerformancePoint; SSRS; Workflow Both lists also include books in French; German; Spanish with even more languages in the 2007 list.
July 2nd, 2010 5:49am

thanks Mike. Just checked AAM and it is correct (http://servername:30976). I didn't change this, so I wasn't surprised. all very weird...
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2010 6:03am

Well there's always the unlikely possibility that default.aspx is not on the list of access options for the site in IIS but that would mean that it has been deleted from there manually. Worth checking if you have nothing else but - as I said - unlikely.2010 Books: SPF 2010; SPS 2010; SPD 2010; InfoPath 2010; Workflow etc. 2007 Books: WSS 3.0; MOSS 2007; SPD 2007; InfoPath 2007; PerformancePoint; SSRS; Workflow Both lists also include books in French; German; Spanish with even more languages in the 2007 list.
July 2nd, 2010 6:08am

checked and ok. hmm..
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2010 7:19am

Hi Wigneys, Please post the exact error into the forum. Did you enable IPV6 on your central admin, if so, disable it and check the effect. Check whether you have enough permission? What is your authentication method? NTLM or Kerberos? Did you configure SSL for your central admin? If so, disable it and then check the effect. Check whether there are two servers have the same IP address? How many servers do you have? What roles are they? For example, WFE or Index. Post the content of the hosts file into the forum for further analyze. Re-run SharePoint configure wizard, then check the effect. Regards, Rock Wang Microsoft Online Community Support
July 5th, 2010 8:11am

Hi Rock, It's a 404 error. No IPV6, kerberos authentication, only one server with this IP address. I don't think it's permissions because I can access the site via a "localhost:port/default.aspx" URL. No SSL. I have 1 x database server, 1 x WFE (also hosts central admin), 1 x Index/crawl server. I've re-run the sp configure wizard with no change... thanks, Steve.
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2010 12:48pm

Hi Steve, Please ensure that the default website is not started.Stoping the Default Website within IIS does solve the issue. within IIS>>Sites>>Defaultwebsite(stop the same). Hope this helps you, worked for me.. :) Regards
August 12th, 2010 12:33pm

thanks for responding. My default site was stopped anyway... Steve.
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2010 9:10am

Hi, If DNS is giving you that problem, have you tried scavenging for old/stale resource records? The last option you have is to run SharePoint Products and Technologies Configuration Wizard and see if it solves the problem. If it doesn't, then the problem is not SharePoint related, it's OS based. You should then consider repairing your protocol stacks http://support.microsoft.com/kb/317518. Then another thing to check (just to be able to narrow down a bit more) attempt connection by using the IP address:port method from the same machine and from another client machine. You've only got one life; help as many people as you can, and enjoy it while it lasts.
August 20th, 2010 10:05am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics