Windows Forum

Ask something
Discussion Locked

Accessing company intranet web page

0 helpful
12 replies

by luv2bike2

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am new to Proxy and DMZ but I have been given a problem: internal users on a NT domain using either Windows 98 or NT or 2000 workstation need to access the company intranet web site.
The company has a Proxy server with a DMZ. On the DMZ there is a Mail server and a web server (for this sake the web server is called XYZ).
Users on the internet can type in XYZ.ABC.com and get to the intranet web site.
Users on the LAN can access the intranet web site by just typing in XYZ in the addressbox on IE. For some reason, when the users on the LAN type in XYZ.ABC.org they get a timeout error message.

The local users are going through the proxy server because the web server is on the dmz that is off of the proxy. the ip address for the web server is correct, so the is FQDN in the host file.

Does anyone have a clue as to why the local users can not access the web page by putting in XYZ.ABC.org but can access it by just typing in XYZ. What can be done so that the user can access it typing xyz.abc.org. If you need a little bit more information please ask.

Thank you

12 replies

by timwalsh

One question: if users are using xyc.abc.COM to access the website from the Internet, why would they use xyz.abc.ORG to access it from the LAN?
(xyz.abc.com and xyz.abc.org are 2 completely independant domains as far as the Internet is concerned.".ORG" is a top-level Internet domain name, therefore if you don't also have your domain registered with the organization that controls the .ORG registry, you can't use it. I would surmise that what is happening is IE is searching for xyz.abc.org and either isn't finding it or is finding multiple sites with the same name and can't resolve the conflict.

by ian mclaws

You say you are using a host file. Why not DNS?
Host files are prone to two common errors, typo's and duplicate entries. The host file is only read until a match is found. If your correct entry is below an incorrect one for the same server, the right one is never used.
When the users just type XYZ, they aren't using the host file for resolution. XYZ is a NetBIOS name which will first be resolved with netbios cache, WINS, LMHOSTS, or broadcast. This certainly points to a problem with your hostname resolution. If just a host file, take a good look at it. If possible, implement DNS.

Good luck,

Ian

This discussion is closed to new replies.