RD Web Access

[Matty94]

Having a strange with getting RDWeb accessing externally. Internally it works fine, however when I try to access the webpage externally it just comes up as the site can't be reached. I've added the external IP address of the domain to the dns in the webhosting page and imported a signed SSL certifcate from godaddy.

 

It might be a simple thing that might need adding but I just can't think what else might be causing this issue. Has anyone else came across this issue before?

 

Thanks

 

Matt

[Liam]

Sounds like DNS to me. Which version of rd web?

[kmount]

Can't be reached, or can't be resolved?

 

If you put the IP in does it work?

 

Sounds like either firewall (or NAT) or DNS to me.

[Nausing]

Sounds like firewall to me. Check you've NATed.

[Matty94]

Sounds like DNS to me. Which version of rd web?

 

I'm using Server 2012R2 with IIS8.

 

Can't be reached, or can't be resolved?

 

If you put the IP in does it work?

 

Sounds like either firewall (or NAT) or DNS to me.

 

It can't be reached. Same thing happens when I try to use the IP address.

Firewall is managed by the LEA so it might be a possibility it could be the firewall.

 

These are the DNS i've added into the webhosting page:

 

[TABLE=width: 500]

[TR]

[TD]DNS Entry[/TD]

[TD]Type[/TD]

[TD]Destination[/TD]

[/TR]

[TR]

[TD]remote[/TD]

[TD]A[/TD]

[TD]School's public IP Address[/TD]

[/TR]

[/TABLE]

 

I don't know if this is correct. It's my first time setting up this type remote access.

 

 

 

Sounds like firewall to me. Check you've NATed.

 

The firewall is managed by the LEA, so I'll contact them tomorrow to get further information about this.

Edited October 9, 2016 by Matty94

[Nausing]

If you haven't modified any settings on the Firewall then im pretty sure 100% this is the issue.

 

What I done for my RDS remotely was get a static IP from my ISP. I then forwarded RD.domain.ac.uk to this IP address on DNS. I then made a NAT rule on my firewall to point all traffic from the internal RD server IP to the IP address the ISP gave me.

 

Essentially when you enter the DNS name externally, it forwards to the internal address.

[CAWJames]

Are you using an RD Gateway or pointing straight to your Web Access server? I found lots of problems when I went straight to the WA, then I installed a GW server and it all worked. But I think your problems are no NAT pointers in your firewall to tell the traffic where to go. You will also have problems if you have any other 443 web services on your public address.

[DavetheITguy]

What firewall are you using TMG, Sonicwall ? are the LA issuing a reverse proxy ? are the DNS records referencing correctly ?

[jcookhgs]

Was it the LEA in the end?

[Matty94]

Sorry, yes it was LEA in the end that needed to make a NAT rule on the firewall.