Unable to access Sharepoint Central Admin and SSP Admin from non-server machines


I've installed MOSS 2007 SP2 on Windows Server 2008 Standard R2 x64. I am able to reach the Central Admin and SSP admin on the server itself - but not from any other machine.

The Web application is listening on port 50000 for the CA and 51000 for the SSP admin. I am trying to access the sites using the following URL: http://servername:50000 and http://servername:51000.

Both of these URL's work from the server itself - but i get a "This page cannot be displayed" message when I try to access from any other machine (logged in as domain admin). I suspect some kind of DNS or Alternate Access Mapping issue? When I do a nslookup for the servername on the client machine I get the correct (and only) ip of the server. Same results when I run nslookup on the server.

Bindings in IIS 7 are set to listen for IP * and port 50000 (CA web app) and 51000 (SSP admin web app) on the http protocol, and the host name field is left blank.
Who is Participating?
OestoneeConnect With a Mentor Commented:
Server 2008 R2 has 3 firewalls..... disable all three. Also disable User Account Controls and enable Remote management (disabled out of the box)
Can you reach the server pages through ip address? If you can the problem is within DNS, else probably it has something to do with your network firewall or with MOSS permitions.
cegelandAuthor Commented:
Same problem when I try accessing by IP... The server is a domain server with out-of-the-box settings for firewall. The only thing I've done is disabling the IE Enhanced Security Config.

Which MOSS permission could cause this problem?
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

When accessing the server locally, set up an alternate access mapping for Central Admin that is compatible with a FQDN in DNS that the other domain member machines recognize.  Make sure your DNS is working properly and that other machines are using this DNS server.  Also, try using the Full domain name:50000 when accessing remote.  For the SSP, I always use a full url for the SSPs.  For example:  IntranetSSP.domainname.com  ExtranetSSP.domainname.com
cegelandAuthor Commented:
I've tested my DNS using nslookup, and the name FQDN I've created an alternate access mapping for resolves to the correct IP - all machines are automatically assigned the only DNS server via DHCP.

Do I have to make any changes to the "Bindings" menu in IIS 7?
cegelandAuthor Commented:
Creating an inbound rule for port 50000 and 51000 using TCP did the trick :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.