Network problems after upgrading to Server 2003 SP1

I have just updated our "Windows Server 2003" with SP1 via Windows Update.
The servers are running within a virtual server environment.

The servers are set up with two NICs - one connected to our intranet, and
one connected to the internet. The NIC connected to the intranet is on a
10.2.16.0 network, while the other NIC is connected with a public ip.

When I save the network configuration I am warned about problems with
multiple gateways (as I have been before). Before upgrading to SP1 there were
no problems running with two gateways, but after the upgrade the system drops
the gateway on the public network with variable intervals. When I try to run
"ipconfig" the system reports no gateway on the public NIC. If I then enter
the TCP/IP configuration on the NIC and saves it - or chooses "Repair" on the
NICs context menu the problem is fixed - but only for a while.

Does anyone know how to fix this problem permanently?


Regards
Jesper

posting the result of ipconfig /all here may help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
"Jesper Soederberg" <(E-Mail Removed)> wrote in message news:7F53CA8C-2634-475B-A0A5-(E-Mail Removed)...
I have just updated our "Windows Server 2003" with SP1 via Windows Update.
The servers are running within a virtual server environment.

The servers are set up with two NICs - one connected to our intranet, and
one connected to the internet. The NIC connected to the intranet is on a
10.2.16.0 network, while the other NIC is connected with a public ip.

When I save the network configuration I am warned about problems with
multiple gateways (as I have been before). Before upgrading to SP1 there were
no problems running with two gateways, but after the upgrade the system drops
the gateway on the public network with variable intervals. When I try to run
"ipconfig" the system reports no gateway on the public NIC. If I then enter
the TCP/IP configuration on the NIC and saves it - or chooses "Repair" on the
NICs context menu the problem is fixed - but only for a while.

Does anyone know how to fix this problem permanently?


Regards
Jesper

The only gateway setting should be on the public NIC. The gateway
setting on the private NIC should be blank.

If you need extra routing on the LAN, use static routes, not default
gateways.

Jesper Soederberg wrote:
> I have just updated our "Windows Server 2003" with SP1 via Windows
> Update. The servers are running within a virtual server environment.
>
> The servers are set up with two NICs - one connected to our intranet,
> and one connected to the internet. The NIC connected to the intranet
> is on a
> 10.2.16.0 network, while the other NIC is connected with a public ip.
>
> When I save the network configuration I am warned about problems with
> multiple gateways (as I have been before). Before upgrading to SP1
> there were no problems running with two gateways, but after the
> upgrade the system drops the gateway on the public network with
> variable intervals. When I try to run "ipconfig" the system reports
> no gateway on the public NIC. If I then enter the TCP/IP
> configuration on the NIC and saves it - or chooses "Repair" on the
> NICs context menu the problem is fixed - but only for a while.
>
> Does anyone know how to fix this problem permanently?
>
>
> Regards
> Jesper