1. Windows Server 2012 R2 Unable To Ping

By default Windows Server 2012 firewall blocks ping requests. To enable please. How To Activate Windows Server 2008/2012 R2 Trial License Hi Thank you. The installation of the AD DS role also adds the File Server role, and File Server role enables its Windows Firewall rules to allow ping. This is illustrated below. Windows 2012 R2 Domain Controller. Windows 2012 R2 Member Server. Note that the File Server role is not installed. Enabling IMCP v4 Using PowerShell. To enable the File and Printer Sharing (Echo Request - ICMPv4-In) rule in PowerShell we can use the below commands. Firstly we enable the rule, it applies to all profiles, and then.

I have 2 Hyper-V 2012 servers, which are joined to a domain (2 DCs) which are VMs on these servers. There are appropriate DNS records for each Hyper-V server.I have noticed that both servers have identical ipconfig settings (with of course different IPs etc), but when I run tracert and the hostname of one Hyper-V server, the first hop returns the destination Hyper-V server.If I do this on the other Hyper-V server, it will return hostnames which are of my webhost. It seems to be trying to use the public DNS to find the internal server (the server I am pinging FROM has 2 nics the private network and public internet).,As a result, I can't ping this Hyper-V server. The firewall is off and nor can I ping the VMs internally by the private IPs.

It looks like on a 2 NIC'd VM, the public NIC is trying to resolve the private IP, and one a server with just the private NIC, I get destination host unreachable from a ping.Any suggestion what may cause this? I can however ping outwards from this server. The problematic server can ping itself. There's also no AV in the environment. What's strange is that this issue happened when I got a chance to RDP onto the environment but it was fine before I left work.Thanks.

Man, have i got a good one for you guys. I have been going round and round with this one for several hours today.We have a couple servers we are configuring for some customers (mind you i did not pick out this hardware or purchase it, i was just called onto the team to help fix the problem.)Both servers are running windows server 2008 R2. And are fully patched. The gateway is a watchgaurd (don't have the specific model number off hand)server A can ping server B and the gateway perfectly fine. Server B cannot ping Server A or the gateway. When it tries to ping out (in wireshark) you can see the arp requests. And running the arp -a command on server b shows the IP and mac of the device it is trying to reach.To me, this seems like layers 1 and 2 are working but layer 3 is not.I have disabled windows firewall for all profiles (domain, public, private), upgraded network drivers, and looked everywhere I can think of for any other 3rd party software that would block outbound traffic from server B.

I have also tried both network cards on server B with the same results. I have them currently plugged into a dumb 5 port switch. I have also tried a cross over cable and directly connected both servers. Same results, A can ping B but B cant ping A.

(Again both firewalls disabled)Any ideas? These routes should workLAN1route add 172.18.8.0 Mask 255.255.252.0 172.18.9.64LAN2route add 172.18.132.0 Mask 255.255.252.0 172.18.135.21Your LAN2 has a straight-up class B mask (not subnetted). It 'believes' it should be able to see your 172.18.8 network through it's local physical connection, so it's probably sending that traffic out your 172.18.135.21 interface (which of course is not the correct path). This is where the routes (and mask) come in.Your LanA, LanB, and LanC all have a Class B mask - meaning they can talk to anybody that has a 172.18.x.x address - especially since they are all connected to the same switch.Change your mask on LAN2 to be 255.255.252.0 and try the routes above - I'm pretty sure it will work. Just some random ideas.Watchguard has nice traffic monitor, you can see everything going on, filtered by MAC or IP, if they have the software loaded.Sounds like you think B is the problem, so remove the watchguard from the equation, ping to/from A and B with a third computer just to ensure A is not problematic.Boot into safe mode with networking and see what you get. If good, do the old click off start up and service items in msconfig with reboots.If you want to eliminate hardware you could boot into a linux thumbdrive and test.Try other network tools, tracert etcThat's all I've got, sorry.

I'm assuming you must have checked the windows firewall settings on both servers (A &B)?Regardless the firewalls are disabled on both servers- enable on both servers check the settings on Windows Firewall with Advanced Security (Inbound and Out Bound) and Windows Firewall within Network and Sharing Center.I don't know why but have seen just disabling windows firewall many times have not resolved the issue. Unless I enable the firewall, allow a program/feature then disable the firewall service.

Windows Server 2012 R2 Unable To Ping

This is the way Windows works!Hope this helps!IT. Jamesa555 wrote:Ah, I thought it was an old build 'looked everywhere I can think of for any other 3rd party software' Let us know what you find, I am curious as to what the problem is.I say that because I was brought into this project late, just to troubleshoot what the problem with connectivity is. I was brought in after the OS, 3rd party software, and windows updates were applied. So I don't know for sure if networking worked right after the clean OS install, before the 3rd party software.

However their software should not be blocking anything like this. But I can't tell for certain if it is (stranger things have happened in our IT careers right?).