New answers tagged

0

try this helped me : 1. Logon to the Remote Desktop Services Session Host computer as an administrator 2. Start--Run gpedit.msc 3. In the left pane, under Computer Configuration, navigate to following: Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment 4. In the right pane, double-click ...


0

The real answer is : Publish a vpn endpoint. This can be behind building NAT (it is better in a publicly visible endpoint). From remote, you vpn to your network and then rdp over the vpn. Making RDP publicly accessible is a bad bad idea.


2

To get this setup working, is it simply a case of asking the people who own the building to forward port 1194 to the ip address they have assigned our router? Yes.* Or is it potentially more complicated than that? No.* Also, if we want to remote desktop in to one of our pcs, is it just a case of getting them to forward port 3389 to our router ...


0

The most effective way to validate the effective policy is to run gpresult /h gpresult.html or use the Group Policy Modeling Wizard. Also, you can't logon with a user account in your local domain to a computer in a remote domain without some kind of trust.


0

You can use auto-scaling with 'max instances' set to 1. If the only server fails, it'll be terminated and new server created in different or the same AZ, but only in the same region. If http healthcheck isn't enough then you can create a custom one. Make sure you have all necessary data on s3 or somewhere else and that you are deploying the data during ...


0

@Oskar, We have a very similar VMware based SQL Server setup and had this same issue however for us this freeze up would happen only for the very first remote connection made since the last time the Server had restarted. It mattered not what user we used to connect or if we used RDP or VMware's on remote connectivity. The very first remote login attempt ...


0

I had a similar problem. I resolved it by upgrading the driver on my NIC. Perhaps that will resolve your issue, too.


0

I agree with everyone else that if you aren't allowing traffic to the server through your firewall there is nothing to worry about. If you want to use Windows Firewall to block it though you can create a new Inbound Rule (the default will block Edge Traversal), allow port 3389, and from there you can limit the external and internal subnets that are able to ...


2

Then the obvious answer is to disable outside access to your RDP port (typically 3389). This question is a bit surprising since the only ways it could be reached from the outside would be if the server was directly connected to the Internet (not firewalled), or if you had previously set a port forwarding rule in your firewall configuration.



Top 50 recent answers are included