Unable to connect to the remote server

[matehall]

Hi.
Background: Trying to migrat between two on-premise azue devops. Firewall opend for 443 for the target server, no firewall for the source server.
Configuration is verified that it works between two devops installation that is not behind a firewall.
PAT or Prompt doesn't matter.

I suspect that there are some other ports that needs to be opened somewhere but I don't know where and I don't know what to search for or ask for by our network admins.

Given the error message below does anyone have any idea's what I'm missing? OBS, Url and ip are fake because of security reasons.

MigrationClient: Connecting to https://devops.something.com/collectionName
[08:27:26 ERR] Unable to configure store
Microsoft.TeamFoundation.TeamFoundationServiceUnavailableException: TF400324: Azure DevOps services are not available from server https://devops.something.com/collectionName
Technical information (for administrator):

Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions :443 ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions :443

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.SendRequestAndGetResponse(HttpWebRequest webRequest, WebException& webException)
--- End of inner exception stack trace ---
at Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.ReadResponse(HttpWebResponse webResponse, WebException webException)
at Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.SendRequest()
at Microsoft.TeamFoundation.Client.Channels.TfsHttpRequestChannel.Request(TfsMessage message, TimeSpan timeout)
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)
at Microsoft.TeamFoundation.Framework.Client.LocationWebService.Connect(Int32 connectOptions, Int32 lastChangeId, Int32 features)
at Microsoft.TeamFoundation.Framework.Client.FrameworkServerDataProvider.Connect(ConnectOptions connectOptions)
at Microsoft.TeamFoundation.Client.TfsConnection.EnsureProviderConnected()
at MigrationTools._EngineV1.Clients.TfsMigrationClient.GetDependantTfsCollection(NetworkCredential credentials) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel_EngineV1\Clients\TfsMigrationClient.cs:line 151

[MrHinsh]

Do you have the required proxy settings?

[matehall]

I don't know. I don't know if there is a proxy. I don't have direct access to the infrastructure or the installation. I know DevOps is on one network and I'm on another. Port 443 and 22 has been opened between them so I can access DevOps UI and clone repos via https and ssh. As far as I know there are no problem using it as intended. We two new DevOps installations. One is behind a load balanser and one is not but the problem is the same on both.
I apricate all hints I can get so I can start to understand what to look for and ask for.

[MrHinsh]

This is a local networking issue and your corporate networking support team should be able to debug. There is nothing I can see from here to help.

The most likely cause is an authenticated proxy and the machine that you are using does not have the proxy built in. The APIs that we use are the same ones that Visual Studio uses.. over http and https.

The next most likely cause is a firewall blocking the http or https requests for some reason.

[matehall]

Thank you for the help! At least now I have something so I can start asking the right question towards our network support.

[matehall]

Just want to thank you for the answer, it helped getting us on the right track! We never found out exactly what was wrong, but it is something in the "network" and we found a way around it.