Mission to Remote Desktop INTO Windows Server 2012 (standalone).
Situation:
Error message:
Additional info:
Question:
Is this a fault of beta software on the 2012 server, or is there a new way of getting RDC to work that I am missing?
slhck
167k4848 gold badges467467 silver badges483483 bronze badges
Guy ThomasGuy Thomas
2,63099 gold badges2828 silver badges4747 bronze badges
11 Answers
I have noticed that sometime enabling remote desktop does not correctly enable the firewall exception for port 3389. Please check whether the appropriate rule is enabled. If it is, try disabling and immediately enabling the firewall. This worked for me on several occasions.
NicholasNicholas
You'll probably need a CAL (Client Access License) in order to access the Windows Server 2012's resources.
slhck
167k4848 gold badges467467 silver badges483483 bronze badges
JustWonderingJustWondering
I was in a similar situation to you OP. I had a group policy to enable RDP. I checked that this was applying, and that I could ping the target server. In the 2012 server manager, it said 'Remote Desktop: Enabled'.
However, after following the steps posted by sushant (cmd > systempropertiesremote) (which can also be reached by other methods e.g. sysdm.cpl) I reached the 'Remote' tab of System Properties and saw that 'Don't allow remote connections to this computer' radio button was selected. This was clearly the cause of my issue and as expected, selecting 'Allow remote connections to this computer' enabled me to mstsc into the server.
I also had another instance where even though RDC was enabled, the firewall port wasn't opened. I now have as standard in any domain I manage two policies, one to enable RDP, and the other to allow it through the firewall.
GostegaGostega
Please check whether you have changed the default keyboards.
I had the same problem but as soon as I selected Keyboard - India, which I configured while installing 2012, the system allowed remote desktop connections again.
slhck
167k4848 gold badges467467 silver badges483483 bronze badges
ThrivikramaThrivikrama
so I came across a problem while setting a static IP on a windows 2012 VM. When the static IP was set my VM became unresponsive to RDP or RDC. how i fixed it?
in the above command prompt do not use the Collin and there IS a space after ipconfig
Jay Ess.
JaY EsSJaY EsS
I had the same problem with WINDOWS XP client wich could not connect to Windows 2012 R2 Remote Server.
I solved the problem by unchecking this box on the server: 'Allow connections only for computers running Remote Desktop with Network Level Authentication (recomended)'.
To find this settings on the Windows 2012 R2 : right click on 'My Computer', choose 'Properties' then 'Remote Settings'. In the screen wich will pop-up, you will find that checkbox.
Probably XP does not suport 'Network Level Authentication' and when the server requires this, the XP client cannot connect.
ToniToni
How to enable Remote Desktop on Windows Server 2012:
167k4848 gold badges467467 silver badges483483 bronze badges
sushantsushant
After reviewing all the answers and comments, also trawling the internet for similar problems, my conclusion is that it's a file corruption problem on the Windows 2012 Server computer.
Further indications Guy ThomasGuy Thomas
a) This test machine has given disk problems before. b) sfc /scannow reveals errors.
2,63099 gold badges2828 silver badges4747 bronze badges
The issue with the default keyboard certainly is one cause.
On one server, I had removed the US keyboard (that was by default configured during installation), then tried to enable RDP, and it did not work.
Once I re-installed the US keyboard, RDP started working!
user250997user250997
I had same problem with both XP and Windows 8 clients.. it seemed the server wasn't properly connected to the domain, I rebooted server, logged in as Domain Administrator, and then when I tried to connect using RDP the Win 8 machine worked fine, XP wouldn't due to NLA as above.
Kevin Panko
6,0791111 gold badges3636 silver badges4848 bronze badges
StefanStefan
I've just had this problem connecting to my Windows 2012 R2 domain controller. It turned out that the cause was that the Network Location Awareness service on the DC had set the network connection as Public instead of Domain. The solution that worked for me was to restart the NLA service as described here https://serverfault.com/questions/362374/domain-controller-thinks-its-on-a-public-network.
Randy OrrisonRandy Orrison
5,27922 gold badges2222 silver badges2424 bronze badges
protected by Der HochstaplerMar 14 '14 at 14:46
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead? Not the answer you're looking for? Browse other questions tagged remote-desktopwindows-server-2012 or ask your own question.
I've just installed Windows Server 2008 on a server and I'm able to connect through Remote Desktop but can't ping. Do I need to open an special port on the firewall to be able to ping a server?
splattne
25.9k1919 gold badges9292 silver badges144144 bronze badges
holiveiraholiveira
44922 gold badges1010 silver badges1313 bronze badges
7 Answers
By default Windows 2008 does not respond to pings. To enable:
Administrative Tools
How To Enable Ping In Windows Server 2016 Core
Windows Firewall with Advanced Security
Inbound Rules
File and Printer Sharing (Echo Request - ICMPv4-IN)
Enable Rule
You should now be able to ping your server from the LAN.
Glorfindel
57411 gold badge88 silver badges1818 bronze badges
sh-betash-beta
5,65355 gold badges3838 silver badges6565 bronze badges
Enable ping through the Windows Firewall at the command line like so:
Apparently this has changed in Windows Server 2008 R2 and newer, to:
That's. uh.. quite a mouthful.
Jeff AtwoodJeff Atwood
8,2391919 gold badges6969 silver badges9191 bronze badges
AlbanAlban
You will want to allow ICMP packets through. Ping doesn't use TCP, so there is no port to open.
Justin ScottJustin Scott
8,27311 gold badge2222 silver badges3737 bronze badges
Bart De Vos
16.2k55 gold badges5454 silver badges7777 bronze badges
whizkidwhizkid
16011 gold badge33 silver badges1616 bronze badges
Pay attention to use the correct quotation marks. Some web sites replace the quotation marks by similar symbols which cause syntax errors. C.f. enter link description here
bernd_kbernd_k
Run these 2 in admin powershell, it enables both ipv6 and ipv4 inbound pings on all networks (public/private/domain):
It is equivalent to this https://serverfault.com/a/6049/147813
Community♦
CMCDragonkaiCMCDragonkai
19011 gold badge22 silver badges1010 bronze badges
Not the answer you're looking for? Browse other questions tagged windows-server-2008firewallmonitoringpingwindows or ask your own question.Enabling Ping on Windows Server 2012 R2 Firewall (Guide)
Ping command is very useful for monitoring PCs and IPs residing on the local area network. Windows Server 2012 doesn’t support Ping command by default without manipulating the Firewall settings. The Ping command may also be disabled because someone else has disabled its rule in Control Panel. This article sheds some light on how to enable Ping on Windows Server 2012.
The following method discusses the procedure for turning On PING commands on Windows Server 2012 R2 that is equally valid for Windows Server 2012. Go to your Control Panel from Windows charm bar or from the search bar by typing “control”. Go to Windows Firewall. Now, click on “Advanced Settings”. The new rule should be established for allowing ICMP packets which would be helpful in using PING command. The rule is already present in Windows Server 2012, and you just need to enable it. For this purpose, select “Inbound Rules”. Search and right-click on “File and Printer Sharing” (Echo Request-ICMPV4-In). Choose the option of Enable Rule. Now, ping requests are allowed on Windows 2012 R2 Server. You need to respond to them without complexly disabling the firewall service. Your device has now become pingable. The following screenshot shows the response of Windows 2012 R2 Server after enabling the Ping command. It should be a very simple guide to follow. You must now be able to ping different IPs from your PC.
Learning has never been so easy!
If you can't ping your brand new Windows Server 2012 R2 Core machine from another machine.. Don't panic!
Ping reply is disabled by default. You just need a few easy step to enable it:
4 Steps totalStep 1: Open cmdStep 2: Run the following command
netsh firewall set icmpsetting 8
Step 3: Ping it!
Now your machine should respond to pings - If it doesn't you have to dig deeper to solve your problem.
Step 4: Deactivate ping reply if neccesary
To disable ping replies again just issue the following command:
netsh firewall set icmpsetting 8 disable
5 Comments
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |