I set up a single Server installation of TFS 2015
SQL Server+Sharepoint Foundation 2013+TFS 2015 on one machine.
The Server has multiple IPs and each installation is listening on an different IP.
Sharepoint uses to IPs one for the normal SP-Sites and one for Central Administration. All IPs have an FQDN registered. The Sharepoint sites (Sharepoint - 80 and Central Administration) are configured to use HTTPS only and use the FQDNs. I could not get the SharePoint Web Services to run HTTPS only so I stick with default settings.
I also disabled the disabled the loopback check for the FQDNs so that the FQDN can be used on the same server. When running the TFS Configuration Wizard all went fine till the SharePoint settings. TFS keeps telling me that he cannot access the SharePoint websites or Central Administration. The urls are working with a browser from the same machine an I am out of ideas why TFS can't connect to SharePoint using the FQDNs. Using the machine name is not an option since "SharePoint - 80" and "Central Administration" running on the same port just different IPs.
Are there any settings I could try to make things work?
Related
We have a REST API which is working with Azure CosmosDB. This Azure CosmosDB account has enabled firewall, which allowing traffic from xxx.xxx.xxx.xxx IP address(which is our OpenVPN server).
On client/developer's side we have OpenVPN client which is pushing route to xxx.xxx.xxx.xxx CosmosDB via VPN interface. When we build and run this REST API app in Visual Studio via IIS Express, the app is ignoring network route to CosmosDB and even ignoring changes in ..\system32\drivers\etc\hosts file(we have internal VNET ip conigured on that CosmosDB account).
Response status code does not indicate success: Forbidden (403); Substatus: 0; ActivityId: $someActivityId; Reason: (Message: {"Errors":["Request originated from IP yyy.yyy.yyy.yyy through public internet. This is blocked by your Cosmos DB account firewall settings. More info: https://aka.ms/cosmosdb-tsg-forbidden"]}
But if we run same app in IIS Server(in our case its a IIS 10) network route and hosts file change also working fine. Also network routing works when we using Microsoft Azure Storage Explorer or powershell az module. It's not working only when the app is hosted by IIS Express.
Its only working via VPN, if VPN is set as default gateway. In our case we don't want to use VPN as gateway for all traffic.
Does IIS Express has any restrictions which may cause this? Is there any workaround?
I created a console application (Asp.Net core Kestrel) which host a web site and copied it to a Windows Server. Browsing http://hostname:5000/ locally on the server works. However, it got This site can’t be reachedu _hostname_ refused to connect. when browsing the site on another machine.
I already created an inbound firewall rule.
I tried create a website in IIS on the server with port 5009. And the website can be remotely accessed.
I'm sharing a wifi connection from a Windows computer to a Mac through their ethernet adaptors, and I'm trying to setup IIS Express so it listens for requests being made from my Mac to the Windows ethernet address on port 64550. I'm getting a status 503 Service Unavailable error on Mac when attempting the request, however.
I'm not really sure what to bind IIS Express to. I've tried *:64550:localhost, *:64550:127.0.0.1, and *:64550:<ethernet-adaptor-address> with no luck.
I should note that I have also setup the advanced internet sharing settings in Windows to allow access to the service, where the internal/external ports are set to 64550 and each of the ip addresses just mentioned I've tried using as the service host ip, so I believe there should be a firewall rule created allowing access.
I should also note that I'm able to successfully make requests to IIS Express with a different network configuration, where both computers access internet through same wifi router and the router forwards requests to 64550 to Windows computer.
I'm using Windows 10, Mac OS 10, and Visual Studio Community 2015 (.NET Framework 4.6) with IIS Express version 10.0.10557.1000.
I have the following configuration:
Windows 7 Enterprise x64 Host running VMWare Workstation v11.0.0 build 2305329
Client (VM) is Windows Server 2008 r2 x64
Symantec Endpoint Protection client (unmanaged) v12.1.5337.5000
using Collabnet Subversion Edge v5.0.1-4144.7
I can connect to subversion's admin port of 3343/4434 from the host computer, however when attempting to connect to the client from two external servers, I get page cannot be displayed. I can connect to the default web port of 80 and get the default IIS 7 page.
I think this may be a firewall configuration situation, however I have tried opening all tcp/udp ports in both windows firewall rules and SEP rules and I still am unable to connect.
I might be able to get it working if I install TFS on port 8080 and uninstall TFS. But I really would rather not.
Check the Advanced/Profiles section of the firewall rule for "CollabNet Subversion Edge Console". This defaults to Public but you many need Domain and/or Private too.
I am now in the process of transferring my servers to windows azure. I created a virtual machine (2008 R2) and installed IIS 7.5. I then transferred one of the site (DNN) and configured it to with it's own apppool (4.0) and granted permission for this app pool to read and write.
I have two domains: one internal, which I defined in the HOST file, and one public (mydomain.com). The internal domain works fine however with the external domain I'm getting:
500 - Internal server error. There is a problem with the resource you
are looking for, and it cannot be displayed.
Perhaps, you haven't set up endpoints for the server on the portal to allow HTTP traffic? In other words, did you open up port 80 on the Azure portal for this VM?
Check out how to do that here - https://www.windowsazure.com/en-us/manage/windows/how-to-guides/setup-endpoints/