• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 471
  • Last Modified:

MS Virtual Server 2005 R2, Cannot access the Administration Website

I have installed VS2005 R2 on a Win2003 server with no errors. When I try to open the Admn Website I get "You are not authorized to view this page" msg and HTTP Error 403 - Forbidden: Access is denied. Is this an issue with IE, IIS or VS2005 security? I initially got a logon screen and logged in as administrator.

Any help would be appreciated.
John
0
johnconti
Asked:
johnconti
  • 5
  • 3
  • 3
  • +1
1 Solution
 
oBdACommented:
Are you starting the admin page from the machine itself while being logged on through RDP? Then add the URL you're accessing to the list of trusted sites, and make sure that "Automatically send logon credentials" (or similar, not using an English version) in the IE settings is set to "Trusted Zone only"; in other words: make sure the logon dialog pops up, do NOT use automatic logon.
0
 
johncontiAuthor Commented:
I am trying to connect on the same machine that VM2005 is installed on.  I am not logged on through RDP. I am not using automatic login.

The login address is:   http://dell-xps2.jc.lcl:1024/VirtualServer/VSWebApp.exe?view=1 
0
 
GinEricCommented:
Interesting, I had that problem until I initialized IIS.  In the Internet Information Servics [IIS] manager, once I added a website, www2, set the port to 8080, it worked.  Although neither the default website nor the www2 one is actually started or running [Apache2 is running on port 80 though].

I also put in the real computername as host.domain.tld, rather than localhost or the way you have it, then, simply calling an http of computerame.domain.tld:1024 brought up a login prompt.  With the proper credentials, it logged right in.
Execute for scripts permission had to also be on, I believe, in the properties of the default and www2 websites.  What you have above is also an executeable, VSWebApp.exe with the question mark followed by the view=1, which tells the virtual server which script to execute; fairly sure of that.

You should have gotten a login prompt; if not, it's your IIS Configuration, probably for that site, which, in our case was not default, rather, www2, even though that is not even used and both the default and www2 are not even running.

Strange way to configure it, but it works.

0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
johncontiAuthor Commented:
Sorry for not getting back sooner, this project had to wait.  Since then I installed VM on another Win2003 server set up as a member server and the VM Admin website worked fine. I also did the following:
- Checked the IIS security settings on both and they matched
- Created a website on IIS on the bad server and it worked fine, but VM Admin still not working
- Execute script permission was set to on

Is there a problem installing VM on a DC?

Any ideas would be appreciated!
John Conti
0
 
rindiCommented:
Probably there is a problem when installing on a DC. I don't use the m$ stuff though, I prefer vmware, much better. Anyway, even vmware warns you when you try to install on a DC, I guess the m$ version just "forgets" to warn you.
0
 
johncontiAuthor Commented:
Thanks rindi, I will try uninstalling and reinstalling VS. Maybe this could solve the mystery.
0
 
GinEricCommented:
Installed Virtual Server again; this time the 64-bit version.  no problem, except that I had to configure the port.

"You are not authorized to view this page" we get this whenever we create a new directory and try to access it.  Permissions to do with whether or not you're allowed to browse as a directory, or, whether or not you have a default index page [index.html index.php index.asp and so on].

We get it both in IIS and Apache.  It is Windows security that is preventing it.  Most likely the DCOM or other permissions under Component Services and the various user, group, and application permissions.

The only time we find this problem is when the server is given the Domain Controller role.
0
 
rindiCommented:
Johnconti, what's the status?
0
 
johncontiAuthor Commented:
Demoting the server to a member server fixed the problem.
Thanks for your help,
John
0
 
rindiCommented:
your welcome
0
 
GinEricCommented:
Makes sense; you give it role of Domain Controller, then install whatever webserver, no one has permissions.  You demote it, but now your webserver is in the registry, so the new role recognises it.  Understand the dichotomy here?
0
 
johncontiAuthor Commented:
I do. Fortunately I have other DC on the network to takeover the roles.
Thanks,
John
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 5
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now