I've banged my head for a few hours on this. I'm beginning to move several computers to a new subnet, all Windows 7, all domain joined. On the original subnet (192.168.145.X) everything works as expected. Once put on the VLAN for the new network (10.1.0.X) I can no longer RDP, ping, etc. even between the two on a local switch (e.g. no firewall rules applied).

Turning on logging of dropped packets for the windows firewall shows explicitly that ping and RDP are being dropped by the Windows firewall. I've turned the firewall off, but still cannot connect. I figure that, even as a local administrator, disabling the firewall may still have some GPO firewall settings applied from the domain that it is running, but RDP is enabled via GPO for all connections, all subnets. I've even created local rules on the windows clients to allow RDP.

What drives me up a wall is that if I change the switch to put the computers back on the default VLAN (192.168.145.X) it work with no issues.

If I throw 2 ubuntu VM's on the VLAN (10.1.0.X) I can ping or SSH all day long. I'm thinking it is a Windows Firewall issue, but all the settings seem correct and it works on the original subnet.

What hidden setting am I missing here?

  • What's routing the traffic between the two VLAN's? In order to get from 192.168.145.x to 10.1.10.x you need a router. – joeqwerty Mar 12 '15 at 20:20
  • pfSense is, but I'm not attempting to connect through a firewall from one subnet to the other. Simply being on the same subnet and attempting to RDP does not work. – Ryan Mar 12 '15 at 20:22
  • so one machine on 10.1.10.x can't RDP to another machine on 10.1.10.x? – joeqwerty Mar 12 '15 at 20:24
  • Correct, and there is an entry in the firewall that says the connection was dropped, despite the firewall allowing any protocol on port 3389. If I turn the firewall off completely, it fails silently – Ryan Mar 12 '15 at 20:27
  • OK, is the firewall rule configured for the correct network profile? What network profile is currently active and what network location is the network connection using (domain, public, private). The firewall rule profile needs to match the network profile. My guess is that the network profile changed and the firewall rule doesn't match it. – joeqwerty Mar 12 '15 at 20:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.