5

Windows 2008. cannot connect via RDP anymore after changes to Firewall prot settings

view full story
linux-howto

http://serverfault.com – After successfully changing default RDP port on remote Windows 2008 R2, I configured that inbound rule to apply only to authenticated connections (because i needed to assign ONLY specific users to be able to remotely connect). Once I selected the option (something like that) "allow this rule only to authenticated connections".. the remote server disconnected me and I can no longer reach server via RDP. How can I access again? Any advice for me please? (HowTos)

u85500's picture
Submitted by u85500 on 03/22/2012 – Made popular on 03/22/2012

Stories similar to Windows 2008. cannot connect via RDP anymore after changes to Firewall prot settings

I come from a Unix background but got the task of configuring a Windows firewall on a public facing server.

I find awkward that any nmap scan I perform against the public IP reports all TCP ports from 1 to 65389 as open regardless of the Windows default rule of not allowing Inbound connections that do not match a rule.

I even got locked out of remote desktop after selecting "Block All Connection

I am very stupid. I applied a windows firewall rule that blocks all tcp connection and thus kicking me out of remote desktop on a dedicated server. I managed to get into recovery via VNC, which is basically a windows xp recovery system. I have access to the physical files of the Windows Server 2008 R2 installation, but I don't know how to disable the firewall so I can reboot from recovery and conn

I have Windows 2008 box and would like to set port forward rule in Windows Firewall for MSSQL Server.

I'm trying to setup an FTP server on Windows 2008 Server. I can connect locally:

C:\>ftp localhost Connected to WebHead1 220 Microsoft FTP Service

However, when I try to connect from remote, it doesn't work:

~>ftp x.x.x.x ftp: Can't connect to `x.x.x.x': Operation timed out ftp: Can't connect to `x.x.x.x'

I've tried everything I can think of with the settings.

I am using Visual Studio 2012 and Windows Server 2012 and want to do a web deploy / publish to the IIS server installed there. It complains that it cannot reach the server and suggests to:

You can ping the remote machine That the msdepsvc or wmsvc service is started on the remote server. Your firewall is not blocking incoming connections of your ports on the destination.

I have a Windows Server 2008 R2 machine with SQL Server 2008 R2 Enterprise installed.

Summary: how do I create an RDC connection from a Windows 2008 server to another server?

Our client will only allow us to connect to their server via a static IP address (which is fair enough), but unfortunately as we're a very small company we don't have one in the office.

As a work around, we had the connection working through our old Windows 2003 server (dynamic-cloud from 1and1). ..

Using the mstsc.exe client shipped by default with recent versions of Windows (i.e.

I've got an SBS 2011 Essentials server which runs fine. However, after I configured VPN on it - something rather strange happened.

The server's IP is 192.168.16.2, and it is set up to hand out IP addresses in the range from 192.168.16.246 - 192.168.16.255. This also works well, but the weird thing is that I am now only able to connect remotely (RDP) against 192.168.16.246.