<div>
This will likely only work if both {companyname}.local + www.{companyname}.local both resolve to the company's IP address, per each machine's local /etc/hosts file or equivalent.<br />
<br />
And, this is generally a bad idea... because...<br />
<br />
Simple things like HTTPS will never work with this type of setup, because foo.local will never match the SSL cert.<br />
<br />
Simple fix, only reference Websites by their public name.
</div>


<div>
in your local DNS server, is there a zone for {company-name}.co.uk and an accompanying A record?
</div>


<div>
There is a subtle difference between the internal and external. One is Comanyname.local and the website is <a href="http://www.company-name.co.uk" rel="ugc">www.company-name.co.uk</a>&nbsp;(there's a hyphen in the website).<br />
<br />
There is an entry in DNS called company-name.co.uk which has an A record pointing to the external web address.
</div>


<div>
So in *theory* it should resolve. &nbsp;Can the DNS server ping it properly and resolve the website? &nbsp;Is the terminal server using the correct DNS server?
</div>


<div>
From what you're describing, everything should work properly (repeat of comment from CES). From any of the machines where you're having issues, could you please show the result of a tracert?
</div>


<div>
The DNS server and all of the PC's with issues can ping the website and resolve it without issues. I've pinged the website from an external source to confirm IP address is correct.<br />
<br />
I have completed a tracert on a couple of the machines with issues and it goes all the way to the IP address of the webhost without issues.<br />
<br />
I may be wrong, but I can't see it being a DNS issue however I am open to any suggestions
</div>


<div>
Is there a difference between how your terminal services service accesses the internet versus other systems? Like in web filtering and so on?
</div>


<div>
I've just logged onto both servers and the TS is actually on a different public IP address to the DC and users. Could it be the ISP is blocking access to the website?
</div>


<div>
You likely hit the problem.<br />
<br />
Many ISPs provide both an internal + public IP for all their machines, so routing optimization can be done when machines inside the ISPs infrastructure are communicating with each other. This ensures fastest communications, as packets stay inside local, high speed network fabric.<br />
<br />
Simple solution is still as I suggest above, just use a single, public IP for all site access, so no DNS or routing games are required to setup + maintain + debug.<br />
<br />
As you've seen, this can create significant time to debug.
</div>


<div>
No one else has been able to give a solution to the issue and a workaround has been found for it
</div>


<div>
<div class="content wysiwyg-content">
I have a client that cannot view their own externally hosted website on most of their PC's and servers when they are internal on the network. The only devices that works are their domain joined Terminal Server and local VM host server. You can ping the web address without any issues from all of the devices and it resolves to the IP address that is in the A record in DNS on the DC.<br />
<br />
Their internal domain is {companyname}.local and their website is {company-name}.co.uk. I have completed an NSlookup for www.{company-name}.co.uk and the non-authoritive answer comes back as the IP address of the A record.<br />
<br />
They also use CyberDuck to upload documents to the webpage and this cannot connect either. The company recently undertook an email migration from on-site exchange to Office 365 but we cannot confirm whether this may have had any affect..
</div>
</div>


I have a client that cannot view their own externally hosted website on most of their PC's and servers when they are internal on the network. The only devices that works are their domain joined Terminal Server and local VM host server. You can ping the web address without any issues from all of the devices and it resolves to the IP address that is in the A record in DNS on the DC.

Their internal domain is {companyname}.local and their website is {company-name}.co.uk. I have completed an NSlookup for www.{company-name}.co.uk and the non-authoritive answer comes back as the IP address of the A record.

They also use CyberDuck to upload documents to the webpage and this cannot connect either. The company recently undertook an email migration from on-site exchange to Office 365 but we cannot confirm whether this may have had any affect..

Cannot access own website internally

Web development includes all aspects of presenting content on intranets and the Internet, including delivery development, protocols, languages and standards, server software, browser clients, databases and multimedia generation.

Web Development

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.