Log file - only recording internal access

I have a strange issue, I have a number of Sites on my webserver.  The
webserver exposes http traffic to the internet.  On my default site, my IIS
logs show all traffic.  On an additional site on the same server, logs are
generated when I access the site from a local ip address, but although the
site is available to public ip addresses the log does not record these
address nor is there record of the visit.  (I used an outside service to
looks good, but when I go to my IIS logs, there is no visit recorded.  I then
browsed the site locally and a new log file is created (first visit of the
day) and all the pages and image files where listed in the log.

How would pages be served up and the log not record them?
--
Fredrick A. Zilz
Director IT
InterHealth N.I.

There is no feature in IIS to restrict logging action to internal/external.

There is no feature in IIS to restrict logging action to internal/
external. Let's first check all our configuration and supporting
evidence.

I want to verify that the external traffic actually got forwarded to
the specific webserver/website that you are examining -- because the
log file indicates that your external requests are not coming to this
web server at all. Hence, nothing was logged.

Maybe your external traffic does not actually get forwarded to this
webserver/website but another server in the cluster/farm (is this the
only machine where the report can be generated?)

Also, if you put a proxy in front of the web server, it is possible
that all "external" IPs got translated to internal IP of the proxy to
access the web server, so it *appears* that no one external is
accessing the web server.

Furthermore, on IIS6, the log file does not flush to disk immediately,
so you will not see its results until 1min later.

You don't see this with an internal machine because you either do not
go through the proxy, or you are going to the specific machine and not
forwarded.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//



On Mar 19, 10:50 am, Fred Zilz <FredZ...@>

Thank you David, it appears that the problem was an external DNS issue and our

Thank you David, it appears that the problem was an external DNS issue and
our website was not accessible.   I have corrected the dns issue.  What I
don't understand is how the outside website
when the external dns was not pointing to our site.  I guess I need to figure
out another way to check that our site is online outside of our local network
(to the public).

I am embarrassed.
--
Fredrick A. Zilz
Director IT
InterHealth N.I.

No worries - I tend to think that modern-day networking can be assimple yet

No worries - I tend to think that modern-day networking can be as
simple yet non-trivial to diagnose as electrical, water, or
ventilation systems. The question is simple - does something get from
point A to point B - but the number of interconnects, splices,
aggregations, throttling as well as accurate tools to probe the system
are many and non-obvious. And no one gets a map of all this.

Usually, when I go through troubleshooting sequence and I conclude
something strange/contradicting, I backtrack and check all my tools
and assumptions to make sure their inputs are 100% correct. More often
than not, the strange conclusion comes from inaccurate input. If that
still doesn't make sense, then I backtrack through my troubleshooting
sequence and make sure it makes logical sense.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//







On Mar 19, 1:25 pm, Fred Zilz <FredZ...@>