Cannot access company web page internally

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Our company web page is hosted inside our lan. In the past few weeks we
noticed that internal users are cannot access the page internally using the
public address (www.mycompany.com). But if I do ipconfig release then renew
then the web page appears normally.

All of the workstations are configured the same through dhcp with the
primary and secondary dns servers pointing to our internal dns servers. The
third and fourth dns servers in the dhcp scope are the ISP's.

What could be the cause of this problem and how do I troubleshoot it? The
servers are running Win2k.
 
In
bernardl said:
Our company web page is hosted inside our lan. In the
past few weeks we noticed that internal users are cannot
access the page internally using the public address
(www.mycompany.com). But if I do ipconfig release then
renew then the web page appears normally.

All of the workstations are configured the same through
dhcp with the primary and secondary dns servers pointing
to our internal dns servers. The third and fourth dns
servers in the dhcp scope are the ISP's.

What could be the cause of this problem and how do I
troubleshoot it? The servers are running Win2k.
Click to expand...

Remove your ISP DNS from the DHCP scope and ipconfig. If the web site is
located on a web server that is behind NAT, then you cannot access it by the
public IP address. Apparently you have the proper www host in your local DNS
with the appropriate private IP address, that is why resetting TCP/IP works.
It places the DNS servers in the original order, removing the ISP's DNS from
the ipconfig is all you need to do.
On a side note, if you have an Active Directory domain, it is not
recommended to use your ISP's DNS in any position on any member of your
local AD domain.
 
Our company web page is hosted inside our lan. [...] internal users are cannot access the page internally using the public address (www.mycompany.com). [...]



You've forgotten to populate your database, no doubt.



All of the workstations are configured the same through dhcp with the primary and secondary dns servers pointing to our internal dns servers. The third and fourth dns servers in the dhcp scope are the ISP's.



Don't do that.



What could be the cause of this problem [...] ?




The erroneous way that you have configured your systems.
 
Back
Top