I have a new installation of System Center 2007 R2 on a Win2k3 SP2 Server. I've only got 500 clients. My server is also running Active Directory. I'm running SQL 2005. All the System Center components are installed on the same box. Unfortunately I'm getting 404 errors when I try run reports and I can't seem to push the client to the site server. When I type http://localhost/sms_mp/.sms_aut?mplist in IE, I see my server info, but when I use my server name instead of localhost, I get the 404 error. This is not a DNS issue, I can ping the server by name. Also I have some other websites running on this server that work fine. I am running IE's enhanced security, but I added the site to my intranet sites and I still have an issue. I even tried the address in Firefox just to be sure. I only have one NIC in my server. I ran a repair on it just to make sure it wasn't some freaky arp cache problem, but no luck. I also made sure my proxy settings were empty. I don't have windows firewall running, I do have Symantec Endpoint's firewall, but I disabled it and the issue did not go away. I am stumped. This should be an easy problem, but I can't get it. Any ideas?

My Rsetup.log doesn't show any errors. I also think that this is probably an IIS issue. I'm running IIS version 6. I can't seem to find anything that doesn't look right. This server is also running another website without any issue.

Yes, I did confirm that my ports were the same.

My personal opinion is that you shouldn't be running a DC, websites and SCCM on one server. Are you stating that you are running symantec firewall on the SCCM server which is also the DC? Can you get to reports if you go to localhost/SMSReporting_XXX? What happens when you try to do mplist from a remote machine using the server name? How about mplist from a remote machine using the IP address of the server? John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

John, good questions. I agree that we shouldn't have all this stuff on one server. Its currently a test environment. We plan to migrate some components to other servers once we get it working. We're running Symantec Endpoint Protection on the server, it includes a firewall component. The firewall is basically configured to allow and log all traffic. I can access the reports by going to localhost/SMSReporting_MEH. If I use mplist from a remote machine I get a 404, doesn't matter if I'm using name or IP.

I think you may have two seperate issues. 1. You can't get to mplist no matter how you try. This seems like the MP is broken. 2. You can get to reports using localhost but not machine name. This sounds like DNS but you still didn't tell me what happens from a remote machine by name and by IP. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

I feel so stupid. I had a custom website using the same port. I wound up changing the port of the custom website because I couldn't get system center working with a different port. There must be something else that you have to do besides changing the port number in site properties and IIS. Thank you all for your assistance.