This isa configuration of Remote Services for serving remote apps in windows 2016 server via rdp:
host1 - Session Host - Collection1 - notepad
host2 - Session Host - Collection1 - notepad
broker1 - Broker + Web Server
If I connect from an external client via rdp I can execute notepad remotely on the less loaded host, thats correct as I have the load balancer equally for both hosts. The flow is to go to the broker, and the broker will redirect you to the hostN. I can retrieve the rdp file from remote web server.
What I cant do is to, inside host1 and for new sessions, connect via rdp locally to run an app on that host. It always goes to the broker to decide where to go. Even if I specify full address as localhost it can go to host1 or host2, it is not deterministic.
Is there any option to specify remote app host and skip broker Load Balancing?
Many thanks.
Answering my own question:
you can disable the GPO setting Use RD Connection Broker load balancing which is under Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\RD Connection Broker. Make sure that the GPO is linked to the OU of your RD Session Host servers.
Related
I have a webservice exposed to the LAN. I have Virtual Machines on this network that I allow external access through Citrix.
From the remoting PC, I need the ability to pivot that connection to port forward the webservice allowing me to access the API. Currently, it is possible to access the webserver like so:
Dev PC --> VM (RDP) --> Webserver
I need to use this connection so I can connect to it like so where --> represents the connection through the VM rather than physically on the VM:
Dev PC --> Webserver
What I have tried:
I have added an entry to my Dev PC hosts file pointing at the LAN IPV4 of the webserver like so:
some.webserver.local 10.10.13.3
I am now reading the Citrix documentation on the gateway connection but cannot find any information on how to make this possible.
Has anyone done this before and knows the solution? Any help apprecicated
I have problem about connect ftp with my server ubuntu throw port 21 at google cloud vm.
i did install vsftp service my ubuntu, and setup rule allow firewall access port 21 on google cloud ,but still can't connect
enter image description here
Do you have selinux or iptables enabled on your server ?. What are the contents of the vsftpd.log file.
Are you able to telnet to your server on port 21 from your local computer ?
Also you need to open more ports in your firewall for the FTP. Port 21 is used for setting up FTP connection, but the data transfer takes place over other ports depending on whether your FTP server is configured in active mode or passive mode.
In active mode, the data transfer takes place over port 20. Active mode is used when the FTP server can connect to the FTP client from port 20. If the client does not allow incoming connections, then passive mode may be used. In Passive mode, the data transfer takes place over a range of ports which is configured on the FTP server. These ports need to be opened on the server.
If your VSFTP server is using Active mode, then you have to open port 20 on the Google Cloud firewall. If your server is using Passive mode then you need to open the ports that are configured on the server for Passive mode.
Read this link for more information on how FTP works: https://en.wikipedia.org/wiki/File_Transfer_Protocol
I was only provided an Amazon EC2 Window Instance: ec2-54-200-63-126.us-west-2.compute.amazonaws.com.
When I try to connect to it by using Remote Desktop Connection. It notify that:
Rmote Desktop can't connect to the remote computer for one of these reason:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
I had searched for an hour and see that I have config something with this instance?
Is there any guide, blog, website for config new instance to be connected?
Have you configured a security group (basically a firewall) for the server that has the RDP port open?
I have a couple of ec2 machines and need to inquire about any RDP sessions (connections) to those machines. I have tried various methods but I get access denied or 'RPC server is unavailable' messages. Although port 3389 is opened.
Here is the report on the methods I have tried:
RDP - works.
Ping - unable to ping.
Terminal Services - says 'Server not found'.
Query session - says 'RPC server is unavailable'.
Get-TSSession (Terminal Services module in power shell) - says 'RPC server is unavailable'.
I believe I had a problem either understanding the terminal services correct or the ec2 instance. Help would be much appreciated.
You're on EC2, so you have security groups to contend with as well as the local firewalls on the instances.
For remote management of those windows machines, you are going to want to ensure your security group settings allow inbound access to TCP 139, TCP 445, UDP 137, UDP 138, and that the local firewalls on those machines allow inbound as well.
DO NOT open those ports to the world--only allow access from well-known static IP addresses, or use VPC.
i wan to install FTP service on my amazon Ec2 window instance,
i have some questions regarding this.
which is a good FTP demon to install on EC2 service for windows on EC2 instance.
can we install FTP same as we can do on window server with window CD.
any tutorial or videos of installation and configuration FTp on Ec2 server which help we?
kindly help me in this regards. Thanks
Here you will find a great tutorial that explains also the inner workings and problems you might encounter trying to setup an ftp server on amazon EC2 instance.
It also explains why just opening port 21 on the amazon firewall will not work. The example there uses the free filezilla ftp server and client but any can be used.
http://me-ol-blog.blogspot.com/2011/03/how-to-install-ftp-server-on-amazon-aws.html
Edited (24-sep-2013):
Because the best policy practice for stackoverflow says not to rely on links, i copied the info from my blog to here:
How to install an FTP Server on amazon AWS EC2
This seems to be a big issue as people usually waste a lot of time on this.
The problem lies with 2 elements: the security group settings & the ftp server settings.
FTP is not considered a good solution for passing files between EC2 instances and your computer as it is not firewall "friendly" - you can't just open port 21/TCP on the amazon security group settings because the server is actually sitting on a NAT address and when an ftp client connects to an FTP server using PASV mode then the server tells the client which port and which address to use for the data stream (like directory listing).
If you want an alternate easy solution for transferring files between yourself and the EC2 instance then setup a dropbox on both machines - it doesn't get easier than this... :)
If you still want to set up an FTP server on your EC2 instance then read on...
Typically, people just try to open port 21 and then try to connect and get something similar to:
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD
Response: 425 Can't open data connection.
The solution is (and for this example I will explain how to perform the setting on FileZilla FTP server on windows):
1. FileZilla FTP server: Edit-> settings -> Passive mode settings:
(x) Retrieve external IP from:
http://ip.filezilla-project.org/ip.php
[ this tells the ftp server to perform a 'whatismyip' and give that to the ftp client, you can also specifically put the address DNS name you use in your remote desktop in the "Use the following IP:", e.g., ec2-6-100-129-60.compute-1.amazonaws.com ]
(x) Use custom port range:
1024-1048
[ these are the ports that will be given to the ftp client - we will open them in the following step in the Firewall ]
2. Amazon security groups: open ports -
a. Custom TCP rule , Port range:21
b. Custom TCP rule, Port range:1024-1048
3. Turn off the windows firewall on the EC2 machine (you don't need it - you have the amazon firewall)
That's it, and just as side note, you don't need to use Elastic IP feature for this to work.
Also don't forget to set your client to use PASV mode (which is typically the default).
You can verify this works by reading the answer the server gives the client when it enters PASV mode:
Command: PASV
Response: 227 Entering Passive Mode (174,149,71,102,4,7)
This response means: "Yo FTP client, use 174.149.71.102 and port 4*256+7=1031"
The Windows EC2 instances are all Windows Server 2008. The easiest thing to do would be to enable the built-in FTP functionality.
See http://www.youtube.com/watch?v=QsGPqkobCs8.
Many people are suggesting to 'Turn off' the Firewall on Windows. It seems easy to get away from confused firewall configuration, but long run it's not good security practice.
Blog may help to configure the FTP step by step with IIS 7.x
http://clouditops.blogspot.in/2016/12/ftp-configuration-on-aws-iis-7x-server.html