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.
Related
Set up is:
Windows 10 Pro 64 bit
All Hyper-V and Container features turned on
Full Sql Server, standard port 1433
Visual Studio 2017
Docker Community Edition Version 18.03.1-ce-win65 (17513)
Stock Windows 10 Firewall rules and security Polices
No additional anti-virus or security
I built a POC .net core 2.1 service in VS2017, added docker support. For test purposes I am trying to connect to the Sql Server from the service. I understand it runs in its own private network. When I run the service as a standalone outside of docker, it connects to Sql fine, so all that is working. Inside of the container it can't connect. I'm specifying the IP of vEthernet (nat).
If I turn off Windows Firewall, then it can connect. When I turn on firewall logging, I can see the packets are being dropped.
In network and sharing, my PC appears in the Network / Private Network group and the vEthernet (default switch) and vEthernet (nat) appear in the Unidentified / Private network group. Access type is No network access.
My PC is connected to the internet via a wi-fi router, so I don't want to open up a big fat security hole, but I'd like the container to be able to connect.
I can't specify the IP of the container since that is dynamic.
How should I set things up to let the containers connect to the Sql?
Maybe, Hyper-V is not connected to the local sever. Open Hyper-V Manager and connect to server...
I have an Azure Vmware Server with VS Studio 2017 community installed.
I want to connect the VS 2017 to my Mac for IOS Development.
I have enabled the remote login on my Mac but I am not able to connect using the Mac agent
Any help is appreciated.
Mac agent use port 22 to connect with client computer. We need to enable this port on Windows Firewall and Network Security Group for your Azure VM.
Steps to enable a port on Windows Firewall.
Step 1, open Windows Firewall by inputting 'wf.msc' in Run window.
Step 2, add new rule for both inbound rules and outbound rules. In the specific port box, input 22.
Steps to enable SSH on Network Security Group.
Step 1, open the Network Security Group of your VM.
Step 2, add new rule for both inbound security rules and outbound security rules.
Please also make sure that your Mac machine has a public IP address and the port 22 is not disabled by any software.
I have been debugging my software by connecting an iphone which is on the same network. Then I use fiddler on my desktop/server and set it to Allow Remote Connection (instructions here). I had this configuration working under Windows Server 2012, since I've upgraded my server to Server 2016 I am no longer able to get the phone to connect to the proxy server at xx.xx.xx.xx:8888. I checked "Allowed Apps" in the Windows Firewall but I don't see anything that looks relevant in there.
I am able to connect to the web server I have running on my server 2016 from my phone so they are able to talk to each other. I just can't access the fiddler proxy server.
Fiddler says it is online and appears to be working correctly.
I'm using Fiddler v4.6.20171.7553.
Is there some setting in windows firewall that might be blocking my proxy server connection?
I figured it out. I changed the firewall settings in Windows firewall to ask me if an app was going to be blocked. After restarting fiddler I was prompted and I said yes, allow this app to go through the firewall and then it started working.
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'm trying to reach a TFS server (either via VS2015 or Web) from my Windows 10 dev box with no luck. I keep getting timeout error
This server is on a remote network that I access via VPN.
I've tried on different Win10 boxes, and it is the same problem.
People in the local network (no vpn) also tried on Windows 10 with no luck
If I access the server on a Windows 7 dev box, everything is OK.
I am able to access a different TFS server (located on my domain network) correctly; same port and protocol.
I disabled the computer firewall
Any clue?
Try to use the IP Address such as http://xxx.xxx.xx.xx:8080/tfs instead of http://compandyname:8080/tfs