server loses connectivity - weird route showing up

Hello,

I have a Windows 2003 Server that is acting up every few days. It seems to
lose network connectivity and I have to reboot it. When this happens, I
cannot ping the default gateway when I log on with the console. I run a
ROUTE PRINT and I see some additional routes showing up that I do not
believe should be there. Their interface is a number (10003) instead of an
IP address, and that interface is not listed in the table of interfaces.
The server has 2 gigabit network ports and only one of them is plugged in.
When I reboot, the routes are all normal. I have installed the latest
drivers. I am using a DHCP address for the NIC; my next step is to set it
to a static address. There are no events in the event log that lead up to
the failure (only events that are a consequence of the failure). Any other
ideas?

IPv4 Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10004 ...00 e0 81 30 40 89 ...... Broadcom NetXtreme Gigabit Ethernet #2
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.3.1 192.168.3.69 20
0.0.0.0 0.0.0.0 192.168.3.1 10003 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.3.0 255.255.255.0 192.168.3.0 10003 10
192.168.3.0 255.255.255.0 192.168.3.69 192.168.3.69 20
192.168.3.69 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.3.92 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.3.255 255.255.255.255 192.168.3.69 192.168.3.69 20
192.168.3.255 255.255.255.255 192.168.3.255 10003 10
224.0.0.0 240.0.0.0 192.168.3.69 192.168.3.69 20
224.0.0.0 240.0.0.0 224.0.0.0 10003 10
255.255.255.255 255.255.255.255 192.168.3.69 192.168.3.69 1
255.255.255.255 255.255.255.255 192.168.3.69 10003 1
Default Gateway: 192.168.3.1
================================================== =========================
Persistent Routes:
None

Thanks,
Shan McArthur

Shan,

I have a similar issue. But the interface number does not appear in the
route table, although it looks like it may be an interface id numbre for a
driver that has been replaced. the #2 in the name of the valid interface
gives me a clue there. You may find in the registry that there is an
interface defined that does have the 0x10003 number, but it is currently not
active. Have you perhaps changed the network card slot recently?

I am alos using the Broadcom NetXtreme. My symptopms are that the clients
cannot connect to the server after about 12 hours but only over the wan. In
my oppinion, I think the TCPIP stack and routing modules of W2k3 are busted
on my machine. As for figuring out why? Well I am just about to give up and
convert to Linux.

"Shan McArthur" wrote:

> Hello,
>
> I have a Windows 2003 Server that is acting up every few days. It seems to
> lose network connectivity and I have to reboot it. When this happens, I
> cannot ping the default gateway when I log on with the console. I run a
> ROUTE PRINT and I see some additional routes showing up that I do not
> believe should be there. Their interface is a number (10003) instead of an
> IP address, and that interface is not listed in the table of interfaces.
> The server has 2 gigabit network ports and only one of them is plugged in.
> When I reboot, the routes are all normal. I have installed the latest
> drivers. I am using a DHCP address for the NIC; my next step is to set it
> to a static address. There are no events in the event log that lead up to
> the failure (only events that are a consequence of the failure). Any other
> ideas?
>
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10004 ...00 e0 81 30 40 89 ...... Broadcom NetXtreme Gigabit Ethernet #2
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.3.1 192.168.3.69 20
> 0.0.0.0 0.0.0.0 192.168.3.1 10003 10
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.3.0 255.255.255.0 192.168.3.0 10003 10
> 192.168.3.0 255.255.255.0 192.168.3.69 192.168.3.69 20
> 192.168.3.69 255.255.255.255 127.0.0.1 127.0.0.1 20
> 192.168.3.92 255.255.255.255 127.0.0.1 127.0.0.1 10
> 192.168.3.255 255.255.255.255 192.168.3.69 192.168.3.69 20
> 192.168.3.255 255.255.255.255 192.168.3.255 10003 10
> 224.0.0.0 240.0.0.0 192.168.3.69 192.168.3.69 20
> 224.0.0.0 240.0.0.0 224.0.0.0 10003 10
> 255.255.255.255 255.255.255.255 192.168.3.69 192.168.3.69 1
> 255.255.255.255 255.255.255.255 192.168.3.69 10003 1
> Default Gateway: 192.168.3.1
> ================================================== =========================
> Persistent Routes:
> None
>
> Thanks,
> Shan McArthur
>
>
>

Hey Shan,

http://support.microsoft.com/kb/898060

The above kb has provided some useful insight to me. I made use of packet
capture and identified the ICMP fragment directives were occuring due to MTU
size on the router path ways. I have used the suggested registry hack for
now to limit the size of MTU to 576 (0x270) I am no longer seeing the ICMP
messages and things seem to be working for our clients. Time will tell
though..... I now have a deminished belief in the reliability and
scalability of windows 2003. ;-(

"Shan McArthur" wrote:

> Hello,
>
> I have a Windows 2003 Server that is acting up every few days. It seems to
> lose network connectivity and I have to reboot it. When this happens, I
> cannot ping the default gateway when I log on with the console. I run a
> ROUTE PRINT and I see some additional routes showing up that I do not
> believe should be there. Their interface is a number (10003) instead of an
> IP address, and that interface is not listed in the table of interfaces.
> The server has 2 gigabit network ports and only one of them is plugged in.
> When I reboot, the routes are all normal. I have installed the latest
> drivers. I am using a DHCP address for the NIC; my next step is to set it
> to a static address. There are no events in the event log that lead up to
> the failure (only events that are a consequence of the failure). Any other
> ideas?
>
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10004 ...00 e0 81 30 40 89 ...... Broadcom NetXtreme Gigabit Ethernet #2
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.3.1 192.168.3.69 20
> 0.0.0.0 0.0.0.0 192.168.3.1 10003 10
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.3.0 255.255.255.0 192.168.3.0 10003 10
> 192.168.3.0 255.255.255.0 192.168.3.69 192.168.3.69 20
> 192.168.3.69 255.255.255.255 127.0.0.1 127.0.0.1 20
> 192.168.3.92 255.255.255.255 127.0.0.1 127.0.0.1 10
> 192.168.3.255 255.255.255.255 192.168.3.69 192.168.3.69 20
> 192.168.3.255 255.255.255.255 192.168.3.255 10003 10
> 224.0.0.0 240.0.0.0 192.168.3.69 192.168.3.69 20
> 224.0.0.0 240.0.0.0 224.0.0.0 10003 10
> 255.255.255.255 255.255.255.255 192.168.3.69 192.168.3.69 1
> 255.255.255.255 255.255.255.255 192.168.3.69 10003 1
> Default Gateway: 192.168.3.1
> ================================================== =========================
> Persistent Routes:
> None
>
> Thanks,
> Shan McArthur
>
>
>

We upgraded the machine BIOS and no longer experience the problem. The
machine has been rock-solid for a week now. It used to crash daily.

I don't think the problem was with Windows, so I would not rush to convert
to Linux. I am pretty sure that the problem was on the motherboard with the
embedded Broadcom NICs. Try updating your BIOS.

Shan

"BobbyO" <(E-Mail Removed)> wrote in message
news:61711DFC-ACB6-4424-A929-(E-Mail Removed)...
> Hey Shan,
>
> http://support.microsoft.com/kb/898060
>
> The above kb has provided some useful insight to me. I made use of packet
> capture and identified the ICMP fragment directives were occuring due to
> MTU
> size on the router path ways. I have used the suggested registry hack for
> now to limit the size of MTU to 576 (0x270) I am no longer seeing the ICMP
> messages and things seem to be working for our clients. Time will tell
> though..... I now have a deminished belief in the reliability and
> scalability of windows 2003. ;-(
>
> "Shan McArthur" wrote:
>
>> Hello,
>>
>> I have a Windows 2003 Server that is acting up every few days. It seems
>> to
>> lose network connectivity and I have to reboot it. When this happens, I
>> cannot ping the default gateway when I log on with the console. I run a
>> ROUTE PRINT and I see some additional routes showing up that I do not
>> believe should be there. Their interface is a number (10003) instead of
>> an
>> IP address, and that interface is not listed in the table of interfaces.
>> The server has 2 gigabit network ports and only one of them is plugged
>> in.
>> When I reboot, the routes are all normal. I have installed the latest
>> drivers. I am using a DHCP address for the NIC; my next step is to set
>> it
>> to a static address. There are no events in the event log that lead up
>> to
>> the failure (only events that are a consequence of the failure). Any
>> other
>> ideas?
>>
>> IPv4 Route Table
>> ================================================== =========================
>> Interface List
>> 0x1 ........................... MS TCP Loopback interface
>> 0x10004 ...00 e0 81 30 40 89 ...... Broadcom NetXtreme Gigabit Ethernet
>> #2
>> ================================================== =========================
>> ================================================== =========================
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 0.0.0.0 0.0.0.0 192.168.3.1 192.168.3.69
>> 20
>> 0.0.0.0 0.0.0.0 192.168.3.1 10003
>> 10
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> 1
>> 192.168.3.0 255.255.255.0 192.168.3.0 10003
>> 10
>> 192.168.3.0 255.255.255.0 192.168.3.69 192.168.3.69
>> 20
>> 192.168.3.69 255.255.255.255 127.0.0.1 127.0.0.1
>> 20
>> 192.168.3.92 255.255.255.255 127.0.0.1 127.0.0.1
>> 10
>> 192.168.3.255 255.255.255.255 192.168.3.69 192.168.3.69
>> 20
>> 192.168.3.255 255.255.255.255 192.168.3.255 10003
>> 10
>> 224.0.0.0 240.0.0.0 192.168.3.69 192.168.3.69
>> 20
>> 224.0.0.0 240.0.0.0 224.0.0.0 10003
>> 10
>> 255.255.255.255 255.255.255.255 192.168.3.69 192.168.3.69
>> 1
>> 255.255.255.255 255.255.255.255 192.168.3.69 10003
>> 1
>> Default Gateway: 192.168.3.1
>> ================================================== =========================
>> Persistent Routes:
>> None
>>
>> Thanks,
>> Shan McArthur
>>
>>
>>