Access to RDS Farm over DirectAccess
Hi,
We have just setup a new 2016 RDS farm, which works perfect when people are working on our network. But when they are at home and connected up by our multisite DirectAccess (also 2016), they cannot access the farm servers. All other servers are accessible.
I've have no problem connecting directly to servers inside the farm when being connected through DirectAccess.
Do you guys how fix this issue?
We have just setup a new 2016 RDS farm, which works perfect when people are working on our network. But when they are at home and connected up by our multisite DirectAccess (also 2016), they cannot access the farm servers. All other servers are accessible.
I've have no problem connecting directly to servers inside the farm when being connected through DirectAccess.
Do you guys how fix this issue?
I think your asking to broad of a question, and not providing enough information. We have no idea how your network is setup, what kind of security you have setup, troubleshooting you've done, things like that.
ASKER
I dont totally agree with you.
I've no problem connecting to the Connection broker or directly to the sessions host, when connected up by DirectAccess. But when connecting to the Farm adress (through the Connection broker), it wont connect. So I have access to the RDS farm servers, but not when going through the Farm DNS record. Which works when on the local network.
So i'm thinking it might be something IPv6-like that is causing this problem?
I've no problem connecting to the Connection broker or directly to the sessions host, when connected up by DirectAccess. But when connecting to the Farm adress (through the Connection broker), it wont connect. So I have access to the RDS farm servers, but not when going through the Farm DNS record. Which works when on the local network.
So i'm thinking it might be something IPv6-like that is causing this problem?
On a remote client do an IPConfig /all and verify connectivity.
Check on the DA server to make sure there are no bangs (warnings) for DNS.
On the remote client:
ping LocalServerName
ping LocalServerName.Domain.Com
Do they resolve correctly?
Also, another method to connect would be via RD Gateway.
Check on the DA server to make sure there are no bangs (warnings) for DNS.
On the remote client:
ping LocalServerName
ping LocalServerName.Domain.Com
Do they resolve correctly?
Also, another method to connect would be via RD Gateway.
make sure the broker sends the server-name and not the IP for the connection.
IP4 address4es are not reachable with DA.
check with netstat -n at the client if you see connections within "SYN" state while connection should be established.
IP4 address4es are not reachable with DA.
check with netstat -n at the client if you see connections within "SYN" state while connection should be established.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This was solved a couple of weeks ago.