I developed a web app, published it to the File System and try to setup the IIS to make it available to a Virtual Machine with XP and a IE8.
Everything is fine in my computer, I can see the website, but from the VM I can't and it's because the setting "Enable remote connections" in the management tab in the Site in the IIS is not checked.
The problem is that option (view image)Manage does not appear under my Site in the IIS.
I already added all the features related with this but nothing works.
It is a asp.net application.
Any guesses?
Thanks
Solved it,
The Network Address Translation option they give in the setting will work.
Just need to access the address that both machines are using for the bridge, so you will have to go to look at the network configuration
Related
I am new at SharePoint and have installed and configured everything, on the local machine (where SharePoint is installed), I connect with the PC name, and everything is working, I can access the front-end and the Central Administration. I have a dns record that points to the ip of the computer. So on another machine, I use the url (intranet.domain.com) to connect. Central Administration works (intranet.domain.com:12548) but when I try to access the front-end (Port 80 - intranet.domain.com) I get the following on my screen
I presume something on my IIS is not setup correctly.
Any advise how I can fix this?
Turns out, I need to create a new Web Application for the new Site Collection
I have Remote Desktop Services running on Windows Server 2012 R2. This feature is still working just fine. I can log into the RD Web page, and access all of my remote applications that I have published.
However, I can no longer manage the deployment. When I launch server manager, and navigate to Remote Desktop Services, I see a message "A Remote Desktop Services deployment does not exist in the server pool. To create a deployment, run the Add Roles and Features Wizard and select the Remote Desktop Services installation option."
When I click manage > Add Roles and Features. The RD Web components are showing as installed. This just started happening recently. Does anyone know why?
I fixed it! I'm not sure why this fixed it, but disabling the options for IPv6 worked. Basically, go into your NIC adapter properties, and uncheck the box next to IPv6.
I created a Azure VM in DevTestLab using base Windows Server 2016 DataCenter. Then I enabled web server role referencing this.
It seems there is some issue with IIS 10 as I am not able to access default website on this server. To verify further, I also tried to host a website with single html page but same issue "Page can't be displayed."
I gave a try with chrome browser and able to browse localhost website on chrome. So IIS 10 seems good on VM. Initially I guess was IIS 10 not configured properly but now it seems proxy on IE not allowing website content getting displayed. Now I am able to proceed with chrome and will reach out our network team if required.
I'm pretty new to Hyper-V so go easy on me if this is an obvious question. I would like to access my host machine's IIS through a Hyper-V VM so that I can view webpages I'm creating in Visual Studio within my VM. I have enabled the network switch to share internet connection however I'm unsure as to how I can allow IIS through to my VM. Is this simply a firewall/port issue or is there a more advanced solution needed?
Since you already have a switch attached to the VM, I don't see anything that is required to be done on the VM, but I would ping the host from VM and make sure that works.
If you are running the website just out of Visual Studio, which would inturn be running IIS Express and not the IIS on the host, you should follow the instructions here to configure IIS express and host to accept requests from non local addresses: http://johan.driessen.se/posts/Accessing-an-IIS-Express-site-from-a-remote-computer.
I've just installed Microsoft SQL Server Express 2008 (with Reporting Services).
My installation is side by side with SQL Server 2005.
So far creating reports and testing them in the development environment has worked fine, however I can't get the web server or report manager working.
In the Reporting Services Configuration Manager, it appears that they have been configured and have a working address (eg: http://mymachine:8080/ReportServer_EXPRESS2008/ and http://mymachine:8080/Reports_EXPRESS2008/).
The Virtual Directories don't exist in IIS, and clicking on the links in the config manager results in a "The page cannot be found".
If I create the Virtual Directories in IIS, and then use Reporting Services Configuration Manager to modify the two sites, Reporting Services Configuration Manager appears to be working correctly (all the right messages appear, indicating that it created the new site and dropped the old site successfully). However, it only drops the existing Virtual Directory and does not create a new one.
Has anyone had this problem before and/or know of a possible solution?
Basically, Reporting Services 2008 doesn't use IIS anymore.
By coincidence (or default?), I already had IIS (with Reporting Services 2005) running off port 8080. Reporting Services 2008 also wanted to run off port 8080.
It appears that the new IIS free address reservation system doesn't work in this situation. Changing the port number fixes the problem.