hgj1357
asked on
W2003 Server w/IIS trouble with hosting
I have installed W2003 Server on a newly formated computer. I want to host 3-4 websites that will generate <100 hits per month in total. I do not need file service or domain control. I have a single NIC. The server sits behind a Linksys router that forwards port 80 to this server. It forwards other ports to one of two NICS on my SBS2003 server which handles email, remote access etc. I have a second router behind which sit my workstations and the second NIC on the SBS2003. The SBS2003 and workstations all seem to work OK.
I installed sharepoint services , application server and remote access on the W2003 server. I put a basic site on this server and from the "Edit Web Site Identification" screen entered the public IP, the web address and the port (80). The W2003 is the sole member of a workgroup and NOT part of the SBS2003 domain.
I have tried accessing the site from a proxy but get a "cannot display web page" error.
My httperr.log shows entries with the IP of the proxy - which makes me think that something is getting through.
I need some help here, and I am very green with IIS.
Thanks
I installed sharepoint services , application server and remote access on the W2003 server. I put a basic site on this server and from the "Edit Web Site Identification" screen entered the public IP, the web address and the port (80). The W2003 is the sole member of a workgroup and NOT part of the SBS2003 domain.
I have tried accessing the site from a proxy but get a "cannot display web page" error.
My httperr.log shows entries with the IP of the proxy - which makes me think that something is getting through.
I need some help here, and I am very green with IIS.
Thanks
What IP addresses are assigned to the NIC on the server and what IP address is the site set to listen on?
My guess is that the IP address for the site doesn't exist on the NIC and that is why you are getting the errors.
Dave Dietz
My guess is that the IP address for the site doesn't exist on the NIC and that is why you are getting the errors.
Dave Dietz
ASKER
My Server NIC is:
192.168.2.10
My router is:
192.168.2.210 / 71.120.63.170
I told IIS to listen for www.got-help.com on 71.120.63.170 port 80
192.168.2.10
My router is:
192.168.2.210 / 71.120.63.170
I told IIS to listen for www.got-help.com on 71.120.63.170 port 80
ASKER
router forwards port 80 to 192.168.2.10
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Got it!
Thanks
I'll give you points for the first post if you can tell me a good way of getting tracking information like "extreme tracking"
H
Thanks
I'll give you points for the first post if you can tell me a good way of getting tracking information like "extreme tracking"
H
I might be able to help if you can define what you mean by "extreme tracking"....
Dave Dietz
Dave Dietz
ASKER
It is a freebie (slightly lame) product that you can use to track web traffic. It tracks unique visitors etc.
I'd like some kind of tracking capability.
I'd like some kind of tracking capability.
Check out AWStats: http://awstats.sourceforge.net
A lot of people seem to be happy with what it provides and it's free. :-)
Dave Dietz
A lot of people seem to be happy with what it provides and it's free. :-)
Dave Dietz
ASKER
This appears to be designed for a Linux web server.
Is anything available for the W2003/IIS platform?
Is anything available for the W2003/IIS platform?
AWStats can be used on IIS just fine - check the setup document:
http://awstats.sourceforge.net/docs/awstats_setup.html
And from the main page:
It can analyze log files from all major server tools like Apache log files (NCSA combined/XLF/ELF log format or common/CLF log format), WebStar, IIS (W3C log format) and a lot of other web, proxy, wap, streaming servers, mail servers and some ftp servers.
Also in the FAQ:
FAQ-ABO100 : WHICH SERVER LOG FILES OR OS ARE SUPPORTED ?
AWStats can works with :
All web server able to write log file with a combined log format (XLF/ELF) like Apache, a common log format (CLF) like Apache or Squid, a W3C log format like IIS 5.0 or higher, or any other log format that contains all information AWStats expect to find.
Most of all others Web/Wap/Proxy/Streaming servers.
Some FTP, Syslog or Mail log files.
Because AWStats is in Perl, it can works on all Operating Systems.
Examples of used platforms (bold means 'tested by author', others were reported by AWStats users to work correctly) :
OS:
Windows 2000, Windows NT 4.0, Windows Me, Linux (RedHat, Mandrake, Debian, Suse...), Macintosh, Solaris, Aix, BeOS, FreeBSD, ...
Web/Wap/Proxy/Streaming servers
Apache 1.3.x and 2.x, IIS 5.0 or higher, ISA, WebStar, WebLogic, WebSite, Windows Media Server, Tomcat, Squid, Sambar, Roxen, Resin, RealMedia server, Oracle9iAS, Lotus Notes/Domino, Darwin, IPlanet, IceCast, ZeroBrand, Zeus, Zope, Abyss...
FTP servers
ProFTPd, vsFTPd...
Mails servers
Postfix, Sendmail, QMail, Mdaemon, www4mail, ...
Perl interpreters (all Perl >= 5.005):
ActivePerl 5.6, ActivePerl 5.8, Perl 5.8, Perl 5.6, Perl 5.005, mod_perl and mod_perl2 for Apache, ...
You will need to install Perl for it to work but that is also free: http://www.activestate.com/ActivePerl/
Dave Dietz
http://awstats.sourceforge.net/docs/awstats_setup.html
And from the main page:
It can analyze log files from all major server tools like Apache log files (NCSA combined/XLF/ELF log format or common/CLF log format), WebStar, IIS (W3C log format) and a lot of other web, proxy, wap, streaming servers, mail servers and some ftp servers.
Also in the FAQ:
FAQ-ABO100 : WHICH SERVER LOG FILES OR OS ARE SUPPORTED ?
AWStats can works with :
All web server able to write log file with a combined log format (XLF/ELF) like Apache, a common log format (CLF) like Apache or Squid, a W3C log format like IIS 5.0 or higher, or any other log format that contains all information AWStats expect to find.
Most of all others Web/Wap/Proxy/Streaming servers.
Some FTP, Syslog or Mail log files.
Because AWStats is in Perl, it can works on all Operating Systems.
Examples of used platforms (bold means 'tested by author', others were reported by AWStats users to work correctly) :
OS:
Windows 2000, Windows NT 4.0, Windows Me, Linux (RedHat, Mandrake, Debian, Suse...), Macintosh, Solaris, Aix, BeOS, FreeBSD, ...
Web/Wap/Proxy/Streaming servers
Apache 1.3.x and 2.x, IIS 5.0 or higher, ISA, WebStar, WebLogic, WebSite, Windows Media Server, Tomcat, Squid, Sambar, Roxen, Resin, RealMedia server, Oracle9iAS, Lotus Notes/Domino, Darwin, IPlanet, IceCast, ZeroBrand, Zeus, Zope, Abyss...
FTP servers
ProFTPd, vsFTPd...
Mails servers
Postfix, Sendmail, QMail, Mdaemon, www4mail, ...
Perl interpreters (all Perl >= 5.005):
ActivePerl 5.6, ActivePerl 5.8, Perl 5.8, Perl 5.6, Perl 5.005, mod_perl and mod_perl2 for Apache, ...
You will need to install Perl for it to work but that is also free: http://www.activestate.com/ActivePerl/
Dave Dietz
ASKER
zoicks!
Have you made this work with IIS?
Have you made this work with IIS?
Once.
Don't really have much need for statistics beyond the basic log files in most of what I do though so I haven't played with it much.
If I remember correctly the install is pretty straight forward - pretty much copying a bunch of files and then editing the config file to point to the right locations.
Dave Dietz
Don't really have much need for statistics beyond the basic log files in most of what I do though so I haven't played with it much.
If I remember correctly the install is pretty straight forward - pretty much copying a bunch of files and then editing the config file to point to the right locations.
Dave Dietz
ASKER
==========================
#Software: Microsoft HTTP API 1.0
#Version: 1.0
#Date: 2007-04-07 15:24:43
#Fields: date time c-ip c-port s-ip s-port cs-version cs-method cs-uri sc-status s-siteid s-reason s-queuename
2007-04-07 15:24:43 208.110.73.34 41583 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:25:04 208.110.73.34 41632 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:25:25 208.110.73.34 41688 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:26:26 208.110.73.34 41967 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:34:03 208.110.73.34 43427 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:34:48 208.110.73.34 43693 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:37:01 208.110.73.34 44174 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:37:54 208.110.73.34 44402 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 15:41:51 208.110.73.34 45464 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 20:58:03 71.12.101.51 3441 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 23:17:48 208.110.73.34 47269 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-07 23:17:48 208.110.73.34 47270 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
2007-04-08 02:33:36 166.196.42.241 1212 192.168.2.10 80 HTTP/1.1 GET / 400 - Hostname -
2007-04-08 04:31:57 74.6.75.31 38856 192.168.2.10 80 HTTP/1.0 GET /robots.txt 400 - Hostname -
2007-04-08 04:31:57 74.6.67.206 40301 192.168.2.10 80 HTTP/1.0 GET / 400 - Hostname -
#Software: Microsoft HTTP API 1.0
#Version: 1.0
#Date: 2007-04-08 10:48:31
#Fields: date time c-ip c-port s-ip s-port cs-version cs-method cs-uri sc-status s-siteid s-reason s-queuename
2007-04-08 10:48:31 65.222.176.124 2986 192.168.2.10 80 HTTP/1.1 GET / 400 - Hostname -