Post SP1 Connection issues

I'm having an issue that I feel can be resolved by scripting as a "workaround".

After installing Windows Server 2003 SP1 on our web server, intermittently
the sites are not accessible. This appears to be caused by the fact that
there is 2 NICs in this server…one with an internal, the other with an
external address. Each NIC has its own default gateway and with the current
network design both gateways are needed for all features to work. This worked
flawlessly before SP1.

As for the script--the issue is resolved if a "Repair" is done on the
external NIC, websites are instantly accessible again. I know nothing about
scripting but wonder if I can get some assistance in obtaining a script that
mimics the repair,…flushes ARP, NETBIOS, and DNS resolver cache….and
registers with DNS.

You should not be using different default gateways on the two NICs. The
default route for a webserver must be out to the Internet via the public
NIC. It should never have worked before SP1.

Why do you feel you need a different default gateway setting on the LAN
NIC? What do you think this achieves?

Eric M. wrote:
> I'm having an issue that I feel can be resolved by scripting as a
> "workaround".
>
> After installing Windows Server 2003 SP1 on our web server,
> intermittently
> the sites are not accessible. This appears to be caused by the fact
> that
> there is 2 NICs in this server.one with an internal, the other with an
> external address. Each NIC has its own default gateway and with the
> current network design both gateways are needed for all features to
> work. This worked flawlessly before SP1.
>
> As for the script--the issue is resolved if a "Repair" is done on the
> external NIC, websites are instantly accessible again. I know nothing
> about scripting but wonder if I can get some assistance in obtaining
> a script that mimics the repair,.flushes ARP, NETBIOS, and DNS
> resolver cache..and
> registers with DNS.

My batch file does the following:
::Flushes the ARP cache.
arp -d *

::Flushes the NETBios cache.
nbtstat -R

::Flushes the DNS client resolver cache.
ipconfig /flushdns

::Reregisters with WINS.
nbtstat -RR

::Reregisters with DNS.
ipconfig /registerdns
***Just make sure your Domain Group Policy or Local Policy gives the user
right "logon as a batch job" for the account issuing the scheduled job or
use an account that has that right.***

"Eric M." <(E-Mail Removed)> wrote in message
news:CFD9E036-89BB-4009-8C90-(E-Mail Removed)...
> I'm having an issue that I feel can be resolved by scripting as a
> "workaround".
>
> After installing Windows Server 2003 SP1 on our web server, intermittently
> the sites are not accessible. This appears to be caused by the fact that
> there is 2 NICs in this server.one with an internal, the other with an
> external address. Each NIC has its own default gateway and with the
> current
> network design both gateways are needed for all features to work. This
> worked
> flawlessly before SP1.
>
> As for the script--the issue is resolved if a "Repair" is done on the
> external NIC, websites are instantly accessible again. I know nothing
> about
> scripting but wonder if I can get some assistance in obtaining a script
> that
> mimics the repair,.flushes ARP, NETBIOS, and DNS resolver cache..and
> registers with DNS.