foobs

Think we've sorted - there was a HTTP redirect setup on the /rpc site in IIS for some reason - got rid of that and instantly started working... Thanks all for your input - good to know I guess!

Somewhat of a discovery; it works using the new style "Remote Desktop" app with the orange icon instead of the old one with the blue icon... I added a rule to allow the old one through firewalls and no difference, really lost now..

We are using a proxy, adding it as a bypass didn't seem to help (or just turning proxy off on client and server - still worked externally!)

Just local user, I'll give that a go tomorrow as I'll be there, will try on a hotspot We've got an authentication policy for the RDS users group (as it should be) but nothing else, I was debating adding a group that allowed all domain PCs or something but can't see that making a difference either

Yeah we can and that works fine - the strange part is that when they take their laptops home it still doesn't work - even on their home networks....

This is the error, no logs or anything we can find - really not helpful: We do have it routed and the A record is all there on DNS, it's the internal address which I believe is correct (always used to be) Thanks

Hi All Hoping for some wisdom here or anyone with previous experience of this issue please! Basically, we run a remote server using RD gateway and up until recently it was fine, all of a sudden it's not accessible from any domain joined PC but still works perfectly fine from any non domain joined PC We've tried everything we can think of but it's driving me nuts.. Any ideas? The only thing we've changed recently is the website provider, and it's SSL certificate but can't see how that would be related.. The server is on a subdomain but has a separate certificate Many thanks in advance