Client VPN Radius and AD issues

[SlesGeek]

I have succesfully setup authentication via a Radius server. I have also been able to use Active Directory authentication... The issue i am running into is that when I connect with either solutions, I am unable to access all but two of our servers (which I have no clue as to why these two servers are the only ones accessible). 

However, if I switch the Client VPN authentication to the Meraki Cloud Authentication method, I am able to access all servers on the private LAN...

Are there additional settings I am not aware of on the radius server that would block the VPN client from accessing certain servers? I setup the radius server according to documentation I gleened from Cisco.

Thanks.

[alemabrahao]

Is it the L2TP client or Anyconnect?

Any chance the user in question is in a group that has limited access to the network?

[SlesGeek]

So here is a strange one…

I decided to test the VPN client using the Meraki Cloud Authenticator… which worked. I pinged all the servers and it worked great….

Then, I switched it back to the Radius server authentication and…. Now I am able to connect to the private LAN and it’s servers! WTH? Why would I need to establish a connection to the servers via the Meraki Cloud Authentication method before I can connect to them via the Radius method?

[alemabrahao]

I have no idea, in this case I suggest you to open a support case.

[PhilipDAth]

Does the RADIUS server have the Filter-Id attribute configured?  This can be used to push a group policy to restrict what the user can access.

[PhilipDAth]

https://documentation.meraki.com/MR/Group_Policies_and_Block_Lists/Using_RADIUS_Attributes_to_Apply_...