Well when I telnet to www.geewhizbang.com on port 80 I get something
listening there.
I got a connection refused error message when I then typed:
GET http://www.geewhizbang.com/index.htm
I think you have some incorrect configuration on your IIS server. I assume
you are doing a port forward on your router for port 80 to your web server.
The DNS event in your event log is a furphy. Just go into the andanved
TCP/IP properties of the NIC on the DNS tab and untick the "Register this
connection in DNS" This will make the errors go away.
Unfortunately I don't know too much about IIS. I assume you can browse to
the website locally just using the internal IP address of your web server?
"Geoff Swenson" <Geoff Swenson[ at ]discussions.microsoft.com> wrote in message
news:770DE95F-3A79-4CDA-839F-39E8376ED0E3[ at ]microsoft.com...
[Quoted Text] >I have windows 2003 server, on a new computer. I formally ran a very
>lightly
> used website on Windows 2000 server, but since upgrading I have had a lot
> of
> issues getting this working consistently on 2003 server.
>
> I have the Qwest-provided 2wire modem, a static IP, dns service from
> dyndns.com and my geewhizbang.com domain is still valid and attached to
> the
> correct dyndns nameservers, and they in turn are pointing to my static iP.
> (71.39.137.64)
>
> But when I test this using WC3 validation service, it give me port 80
> failures. I also have messages in my event viewer:
>
> Host Name : geewhizzer
> Primary Domain Suffix : geewhizbang.com
> DNS server list :
> 192.168.0.1 (this is the 2wire modem btw)
> Sent update to server : 63.208.196.92
> IP Address(es) : 192.168.0.64
>
> (still quoting: The reason the system could not register these RRs was
> because of a security related problem. The cause of this could be (a) your
> computer does not have permissions to register and update the specific DNS
> domain name set for this adapter, or (b) there might have been a problem
> negotiating valid credentials with the DNS server during the processing of
> the update request.
>
> You can manually retry DNS registration of the network adapter and its
> settings by typing "ipconfig /registerdns" at the command prompt. If
> problems
> still persist, contact your DNS server or network systems administrator.
> For
> specific error code, see the record data displayed below.
>
> (end of quote).
>
> I ran the ipconfig /registerdns and it returned the same message a couple
> minutes later.
> I can supply more information about my setup of the modem and IIS on
> request
> to anyone who wants to help me with this.
|