Constantly having to perfomr IPCONFIG /REGISTERDNS

After doing all the latest Windows Updates as of 3/9/2006, I am constantly
having to to a IPCONFIG /REGISTERDNS on my webserver multiple times a day. I
have checked everything I can think of to correct the issue. What would
cause this to happen. Nothing has changed for ISPs DNS record, checked that.
The machine will not even respond to http://IP ADDRESS when tried via a web
browser. Once I do the command above it work fine from anywhere between 15 -
60 minutes. Any help would be apprecitated. Windows 2003 Server

Thank
Ronald

"Ronald_L" <(E-Mail Removed)> wrote in message
news:EC8A191F-00F7-4567-9EDB-(E-Mail Removed)...
> cause this to happen. Nothing has changed for ISPs DNS record, checked
that.
> The machine will not even respond to http://IP ADDRESS when tried via a
web
> browser. Once I do the command above it work fine from anywhere between

If you are using http://IP ADDRESS then you aren't using DNS to begin with.

If your IE is using a proxy server then the IP# will fail because IE
wouldn't know an IP# if it tripped over one,...all it sees is the "dots" in
the URL and assumes it is a FQDN and sends it to the Proxy which ends up
choking on it. The moral of that story is that IP# are *not* more
dependable than Names and you should never use IP#s in a URL.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------

I'm not using a proxy for anytype of web access for IE. My issue is that
even using the ip address to bypass dns the website will not respond until I
perform a IPConfig /REGISTERDNS from the command line or do a repair on the
network interface. As soon as either one of those commands are carrried out,
the site works for a while without issues. What would cause that command to
be issued to get it back working. I have replaced the NIC, just in case,
checked all the settings on the card, checked the event viewer all to no
avail.

"Phillip Windell" wrote:

> "Ronald_L" <(E-Mail Removed)> wrote in message
> news:EC8A191F-00F7-4567-9EDB-(E-Mail Removed)...
> > cause this to happen. Nothing has changed for ISPs DNS record, checked
> that.
> > The machine will not even respond to http://IP ADDRESS when tried via a
> web
> > browser. Once I do the command above it work fine from anywhere between
>
> If you are using http://IP ADDRESS then you aren't using DNS to begin with.
>
> If your IE is using a proxy server then the IP# will fail because IE
> wouldn't know an IP# if it tripped over one,...all it sees is the "dots" in
> the URL and assumes it is a FQDN and sends it to the Proxy which ends up
> choking on it. The moral of that story is that IP# are *not* more
> dependable than Names and you should never use IP#s in a URL.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Troubleshooting Client Authentication on Access Rules in ISA Server 2004
> http://download.microsoft.com/downlo...7/ts_rules.doc
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
>
> Deployment Guidelines for ISA Server 2004 Enterprise Edition
> http://www.microsoft.com/technet/pro...isaserver.mspx
> -----------------------------------------------------
>
>
>
>

Try this;
Open the properties of the NIC.
Open the TCP/IP Properties.
Open the DNS Tab under Advanced...
Ensure that "Register this connection's addresses in DNS" is checked.

I've said this before...
Make sure QOS is turnned off unless you require it for special
applications.

Ensure your WEB Server has a STATIC IP Address.

Instead of using the IP to connect to the website, Register your WEB
SERVER in DNS.