Can't access network drive through RDS

[LeeAU]

I have an issue with a network drive not mapping for users when logging in through Microsoft RDS. Our network drives are mapped through single a GPO that uses item level targeting and maps it to all users in a specific OU. I have run a gpresult /r and can see that the GPO is successfully applying, and the other mapped drives specified in the same policy map successfully. It’s just one drive that isn’t mapping (G) – and this only happens when the user is logged in using remote desktop, when they’re logged into a workstation (either Windows 7 or Windows 10) all of the drives including G: map successfully.

 

Upon further investigation I've found that our Microsoft Remote Desktop Server(s) can no longer access one of our file servers - FILESERVER01 / 192.200.1.20The hostnames/IPs of our RDS servers are (They are set up with load balancing):

External - RDS.MYCOMPANY.COM.AU

Internal - RDSSERVER01 / 10.202.180.21 & RDSSERVER02 / 10.202.180.22

(They are set up with load balancing)

 

The RDS servers can access everything else fine such as FILESERVER02, EXCHANGE01 etc. It’s just FILESERVER01 that it can’t communicate with, and FILESERVER01 can’t ping any of the above RDS server addresses either.I've checked DNS, DHCP, AntiVirus, LMHOSTS file and our Firewall and everthing seems to be in order with those...

Edited December 11, 2018 by LeeAU

[bknaggs]

Subnet mask correct on the file server?

I had a similar problem with one server being inaccessible to certain machines and it was that.

[LeeAU]

Subnet mask correct on the file server?

I had a similar problem with one server being inaccessible to certain machines and it was that.

 

 

Yes, I've double check and the subnet mask and other NIC settings are all ok, it's really weird!