Routing fails from time to time

[semuhphor]

We have a Windows 2003 server with 2 nics. One is connected to an internal network (192.168.1.x), the other to a dmz (192.168.10.x).

Both networks are served by the same cisco router connected externally to a T1.

From time to time, the server cannot be accessed from the DMZ, and we have to restart that NIC (only the NIC) to reestablish contact with the outside world.

The weird thing is that when the DMZ connection fails, the NIC is still active on the 192.168.10.x net. I can get to it from another machine on that same net, so it is the router that is not passing the packets, not a NIC failure.

This happened with both our current CISCO router and our previous SONICWALL router.

Any thoughts on what may cause this would be greatly appreciated.

TIA,

-- Bob Flanders

[ahmednaas]

Did you do any diagnostics on the switch when this happens? What does the event log on the server say?

This is far-fetched but hopefully routing is not enabled on the 2k3 server (between the 2 NIC's)?

[semuhphor]

How would I tell if routing was enabled on win2k3?

Kinda new at this.

[ahmednaas]

check:

control panal -> admin tools -> services -> routing

if it is enabled then disable it.

[semuhphor]

I checked the service ... it is disabled.

Any other thoughts?

Thanks,

-- Bob

[Danilo Dy]

From the windows 2003 Server, what is configured as default gateway?

Since the Windows 2003 Server DMZ NIC will be access by the outside world, your Windows 2003 Server default gateway should be in the network 192.168.10.x - whatever is configured in your Cisco router as the gateway for network 192.168.10.x

This in the assumption that the Windows 2003 Server internal NIC is not to be access by the outside world but only internal clients in the same network 192.168.1.x.

[semuhphor]

Thanks for your message. I'm going to give that a try when I can mess with the server. Can't play with it during normal business hours.

I'll let you know what we see.

-- Bob