New pfsense setup (RDP)
-
I insist, look elsewhere.
To begin with, having a server being assigned ip address via dhcp is usually a bad idea, unless there are reasons for that.
Pf is at the network edge
Your pc and server are on the same lan
Your pc locates the ip of the server via arp and lan switch does the rest
Pf has no idea on that whatsoever.
Put a static ip on the server
make sure firewall is off and reboot
This is windows, Rebooting is needed by design
-
@netblues Okay, Will do that and check.
One thing that concerns me is that I have also an AP with a static IP address.. i can't even access that nor ping thru my pc. -
Recheck ip addreses, subnets
Use static for your pc and server and see if it works.
And post dhcp configuration from pf -
-
Well I don't see the gateway option, but still even if it was wrong/missing you would have no internet But rdp would work.
In any case, dhcp is ok for what you are experiencing.
The curlpit is elsewhere. -
I did not assign a gateway to the lan as it said there, maybe I was wrong, should I add it?
-
Not that gateway. The dhcp assigned gw to the clients
You must NOT assign a gateway on your lan interface whatsoever.
But solve the rdp issue. It is not pf related -
Have you rebooted the switch? That would be the only other thing besides your client machines that could be causing your issue.
-
Do you have port forwarding set up. I had to forward port 80 and 443 to my windows server to use Remote Desktop and Anywhere access.
-
You do NOT want RDP from public internet forwarded to your server.
https://forum.netgate.com/topic/143948/more-details-about-bluekeep-the-microsoft-rdp-vulnerabilityMicrosoft has finally acknowledged flaws in the RDP implementation and NSA is begging admins to at least install all current patches.
The question is not if your server gets owned but when (hours or days).Only way to play RDP safely is by a VPN to your pfSense.
-
@benman said in New pfsense setup (RDP):
Do you have port forwarding set up. I had to forward port 80 and 443 to my windows server to use Remote Desktop and Anywhere access.
Gentlemen.. WHAT are you TALKING about?
This is a same subnet connectivity issue.
Why on earth would anyone need to port forward, and more specifically 80 and 443 for rdp in any scenario? -
@netblues said in New pfsense setup (RDP):
@benman said in New pfsense setup (RDP):
Do you have port forwarding set up. I had to forward port 80 and 443 to my windows server to use Remote Desktop and Anywhere access.
Gentlemen.. WHAT are you TALKING about?
This is a same subnet connectivity issue.
Why on earth would anyone need to port forward, and more specifically 80 and 443 for rdp in any scenario?I was asking that myself. Also I'm worried about
@iAsk said in New pfsense setup (RDP):
One thing that concerns me is that I have also an AP with a static IP address.. i can't even access that nor ping thru my pc.
as that sounds pretty much like a LAN side issue to me. Switch+AP+Server+Client - IF are in the same network 192.168.100.x like above - should have no problem seeing each other. Otherwise that's a switch/IP problem on that network. Nothing to do with pfSense so far but with networking/cabling problems AFAIR.
-
I was referring to the fact that it worked before dropping in a router. Connecting host to host on the same broadcast domain must work, that traffic never reaches the router.
Two possible scenarios:
- access through the router
- layer8 problem and setup is messed up.
Maybe I interpreted too much in user's abilities.
@iAsk: can you post a schematic of your network layout, please. That would take the guesswork out.
-
@JeGr Apologies, I was half asleep when I was replying to this, I was thinking about anywhere access and getting all the Remote Desktop settings from the Server Website.
-
@benman No offense taken - just curious :)
