chrisjako Posted June 20, 2014 Posted June 20, 2014 Morning all, I've recently setup RDWEB which works great for some and not for others, just remoted into a staff members PC at home and this is what she gets: However it works fine when i try from my PC and another member of staffs PC Any ideas as to what might be blocking her?
chrisjako Posted June 20, 2014 Author Posted June 20, 2014 o.k I've got so far as to finding out its a DNS issue, remote access works when i resolve the internal DNS name of the server to the hosts file of the external client machine however I cant find out for the life of me how to change what FQDN the apps look to in RDWEB
jdoldridge Posted June 20, 2014 Posted June 20, 2014 It is somewhere in IIS I had to add the TSDefault Gateway in there and it started working like a dream
chrisjako Posted June 23, 2014 Author Posted June 23, 2014 I found a powershell script which changes the internal DNS to the External, which was also the cause to the problem as the apps where resolving to the internal DNS due to our double NAT setup we have with our local LEA
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now