remote VPN clients not showing correctly in terminal server

[MGregC]

We use MS 2019 terminal servers and have remote locations connecting via MX' to the data center where the TS live. Clients on the other end of the VPN show as coming from the WAN IP of the hub MX at the data center. We are tracking clients by their IP address given the non-Meraki parts of our infrastructure.

Is there something on the Meraki side that will present the correct IP of the remote client--192.168.x.x, etc?

[JustinBennett]

I had the same issue once I moved my RDP servers behind their own protected firewall subnet in my datacenter. Load balancing, RDP Gateway, or NAT on the RDP Hosts can cause the source client IP address to be obscured or dropped for numerous other reasons. I was very sad once I lost this insight as well to my RDP farm. 

[alemabrahao]

Are you using L2TP or Anyconnect? 

[MGregC]

Sorry for the confusion. 

When I say remote clients I mean they are connected to an MX on the other end of the Meraki AutoVPN. They are not using L2TP or AnyConnect.

[alemabrahao]

I suggest you to open a support case.