"Access denied" error message when you try to connect to the Virtual Server 2005 Administration Web site in Windows Server 2003 Service Pack 1 or Windows XP Service Pack 2

Article ID : 888749
Last Review : January 12, 2005

SYMPTOMS
When you run Microsoft Virtual Server 2005 on Microsoft Windows Server 2003 Service Pack 1 (SP1) or on Microsoft Windows XP Service Pack 2 (SP2), and you try to connect to the Administration Web site, you may receive the following error message:
Access denied.
When this problem occurs, an event that is similar to the following may be recorded in the System log:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10017
Date: Date
Time: Time
User: User_Name
Computer: Computer_Name
Description: The application-specific permission settings do not grant Activation permission for the COM Server application with CLSID {DA3111BC-1BD7-4884-A535-8470D36028F7} to the user User_Name SID User_SID. This security permission can be modified using the Component Services administrative tool.

RESOLUTION
To resolve this problem, reset the DCOM permissions for authenticated users. To do this, follow these steps:1. Click Start, point to All Programs, point to Administrative Tools, and then click Component Services.
2. Expand Component Services, expand Computers, expand My Computer, and then expand DCOM Config.
3. Right-click Virtual Server, click Properties, and then click the Security tab.
4. In the Launch and Activation Permissions area, click Customize, and then click Edit.
5. In the Group or user names list, click Authenticated Users.
6. In the Permissions for Authenticated Users list, click to select the Allow check box next to Launch Permission, and then click OK.
7. In the Access Permissions area, click Customize, and then click Edit.
8. In the Group or user names list, click Authenticated Users.
9. In the Permissions for Authenticated Users list, click to select the Allow check box next to Access Permission, and then click OK.
10. Click Apply, click OK, and then quit Component Services.

APPLIES TO

• Microsoft Virtual Server 2005 Standard Edition, when used with:
• Microsoft Windows Server 2003 Service Pack 1
• Microsoft Windows XP Professional SP2

Keywords: kbtshoot kbprb KB888749

I believe that XPSP2 has a couple of changes that make it challenging to
host a website:
1. Firewall is on by default and blocks port 80 access
2. Localhost does not work by default

Both issues have been well discussed on the web and can easily be searched
for.

Just because portqry or netstat shows a port is listened on does *not* mean
it is actually accessible.

I run VS on XPSP2 without issue after I open the VS website port and allow
vssrvc.exe access on the firewall so that remote access (via scripting)
works.