Re: Multi NIC Windows 2003 routing problem
From: Phillip Windell (_at_.)
Date: 11/01/04
- Next message: cjobes: "Logon documentation"
- Previous message: Sandeep KT [MSFT]: "RE: Workgroup can not be accessed"
- In reply to: Chuck: "Multi NIC Windows 2003 routing problem"
- Next in thread: Chuck: "Re: Multi NIC Windows 2003 routing problem"
- Reply: Chuck: "Re: Multi NIC Windows 2003 routing problem"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 1 Nov 2004 16:53:34 -0600
You cannot have two Default Gateways. By the very definition of the
term,..there can only be one.
157025 - Default Gateway Configuration for Multihomed Computers
http://support.microsoft.com/default.aspx?scid=kb;en-us;157025&Product=win2000
Since you appear to have three subnets floating around and I have no idea
about the relationship between them,...I cannot tell you how to deal with
the problem the right way.
The best way is to never multi-home a Server under any circumstances except
for Proxys and NAT Servers. Place real LAN routers between the subnets, not
computers.
Here are other multi-homing "horrors" to keep in mind. This is why computers
should only "live" on networks and let the Routers "route" the networks.
175767 - Expected Behavior of Multiple Adapters on Same Network
http://support.microsoft.com/default.aspx?scid=kb;EN-US;175767
272294 - Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default.aspx?scid=kb;en-us;272294
191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611
Microsoft Windows XP - Multihoming Considerations
http://www.microsoft.com/resources/documentation/windows/xp/all/reskit/en-us/prcc_tcp_qpzj.asp?
128978 - Dead Gateway Detection in TCP/IP for Windows NT
http://support.microsoft.com/default.aspx?scid=kb;EN-US;128978
171564 - TCP/IP Dead Gateway Detection Algorithm Updated for Windows NT
http://support.microsoft.com/default.aspx?scid=kb;EN-US;171564
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com "Chuck" <balt3@inside.net.remove.from.here.no> wrote in message news:4186a368$0$327$4d4ef98e@read.news.ch.uu.net... > Hi all, > > I have a Windows 2003 Enterprise Server which talks to machines in one > private network, hosted on one network card, and another private network as > well as the internet which should be routed over the other network card. > This exact layout on a Windows NT 4 Server works just fine, but not on the > Windows 2003 Server which I'm setting up to replace the NT4 Server. The > setup: > > NIC1: > IP: 192.168.90.1 > Def GW: 192.168.90.67 > Subnet mask: 255.255.255.0 > > NIC2: > IP: 10.10.10.2 > Def GW: 10.10.10.1 > Subnet mask: 255.255.255.0 > > NIC1 is connected to a Cisco PIX leading to a VPN. The PIX is the default > gateway, the network behind the PIX is 192.168.20.x > NIC2 is connected to a Sonicwall, which is connected to the internet. The > Sonicwall is the default gateway. > > When I set the TCP/IP properties on the server, I always get a warning > message saying that having different default gateways would not work as > expected. The server then communicates just fine on the 192.168.90.x > network, and it can also ping machines on the 10.10.10.x network. But any > requests that would go out to the internet are failing, can't even an > outside server with a public IP (which works on the NT4 system). > > Does anyone see how this can be solved? With the NT4 system I had to add > this route to get it to work: > route add 192.168.20.0 mask 255.255.255.0 192.168.90.67 -p > > but that doesn't seem to make a difference on the Windows 2003 Server. > > Any hints greatly appreciated. Thanks! > > >
- Next message: cjobes: "Logon documentation"
- Previous message: Sandeep KT [MSFT]: "RE: Workgroup can not be accessed"
- In reply to: Chuck: "Multi NIC Windows 2003 routing problem"
- Next in thread: Chuck: "Re: Multi NIC Windows 2003 routing problem"
- Reply: Chuck: "Re: Multi NIC Windows 2003 routing problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
