New answers tagged

0

You can't, as they are not domain joined. (as iis send the current logged on credential to the remote site, thus it fail and ask a login) A workaround would be to invest to use a broker (xenapp or rdp) to publish the website link. As after the first connection you can allow in the local client in the ipad to save the credential used after the first login. ...


3

If you want to connect to remote host, you need to use its name, not the localhost: ssh -L 5672:R:5672 G in this way, you should be able to access host R on localhost:5672.


2

Don't do this with traditional AD DS. If you have to go cloud-only, you should use the Azure Active Directory SaaS solution with Intune for management and Windows 10 on the desktop. You lose things like Kerberos, GPO, etc, but you gain a great amount of flexibility and have no infrastructure to manage. As I said, this isn't a 1:1 comparison of features ...


0

You are using the same IP address space 192.168.1.0/24 in your home as the public Wi-Fi is using that you are connected to. Therefore when you are connecting to 192.168.1.1, your computer opens connection with the default gateway in the public Wi-Fi, since it is directly connected according to your IP settings. To fix this, you need to change your home ...


0

Shrew is IPSec VPN client, which is may be limited by NAT existence between client(s) and server. If same NAT is traversed by both clients, that could be a good reason for the first session to stop working


2

Yes, you can change the peer IP address without create new Site-To-Site VPN In general you have to change two parameters. peer IP address tunnel group name According your link they changed only first setting. If you check your log file you have to find wrong tunnel group name or something like that. Anyway this is very good Step by Step guide for your ...


2

Well, your description is very vague A few things first you can check: Make sure the OpenVPN server has the sysctl variable net.ipv4.ip_forward set to 1. You can easily check this using sysctl net.ipv4.ip_forward. In case you need to set it, just to sysctl -w net.ipv4.ip_forward=1 or the server's /etc/sysctl.conf If you want to tunnel all your traffic ...


0

Swap the local and remote subnets round, in the VPN policy. if you are defining them on the FVS338. I'd also double check the Mode Config screen to confirm that there are plenty of remote IPs available.


0

Discussion Build and run vpnc on CoreOS? on forum CoreOS Dev suggested two solutions: Build the binary on Ubuntu and copy it to CoreOS. Run vpnc in its own container and run this container and the application container using the VPN within the same pod.


1

There is an impressive amount of junk to read through to find info about how to do things like this on CoreOS. From what I can tell, you should be creating a container for anything you want to run on this OS (as per it's design) unless you want to modify CoreOS itself. Perhaps this will help you create an application container https://coreos.com/blog/...


2

For me, I boil this down to security policy. We have written policy that no publicly accessible system will have inbound access to the intranet unless specific exception is authorized. We also have a policy that the DMZ will not have inbound access to our intranet and that our extranet does. For example, we have a web server with backend database that must ...


0

Right now in Azure there is no way to route traffic the way you described. You can either create a site to site link to each vnet (or a point to site connection for testing) You can invest in an Express route connection and use MPLS to swap routing information You could consider using one Vnet with multiple subnets instead of two Vnets, unless you have ...


0

From the docs: You can create additional VPN connections to other VPCs using the same customer gateway device. You can reuse the same customer gateway IP address for each of those VPN connections.


3

A database connection is a very critical part of any infrastructure as it usually contains much more data than the clients can/should see. You want to protect this as much as possible, which means that you want to prevent anyone from even attempting to connect to it and also want to completely encrypt the traffic so no one can eavesdrop on it, and optimally ...


1

It depends of the VPN that you are using... usually, Windows resolves everything through the VPN tunnel. Other solutions such as DirectAccess for example, let you define a NRPT to determine how a specific namespace should be resolved.


0

If you don't want to use a bridged VPN (they are more difficult to set up and less efficient, and not all VPN servers support them) then there are a few other options available: You can use Network Beacon to broadcast the same services back to your client that it would have received over Bonjour (e.g. printers and file servers). Probably most useful if you ...


0

Yes the cisco asa 5500 series can support l2tp/ipsec firewalls and the native windows client can be used to connect to them.


3

You have to add route to 123.4.5.6 trought your ISP gate. For example: route add -host 123.4.5.6 gw 192.168.0.1 According your Linux distribution put this rule for routing in appropriate config file.



Top 50 recent answers are included