Re: Why this default route doesn't work ?



The computer is multihomed.

*Internet*-NIC
IP:1.78.253.1
Subnet:255.0.0.0
Default Gateway:1.78.253.254


Intranet-NIC:
IP:1.1.1.1
Subnet:255.0.0.0
(No default gateway)

Note that are although the subnet masks are the same on both NICs, the
networks are different. As far as i know that should not cause any problem.
Then I set the default gateway thru the route add command, but obviously
that is not working...

"Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eplQkA8ZFHA.3840@xxxxxxxxxxxxxxxxxxxxxxx
> "on the second NIC" ?
>
> First I've heard of the second NIC. Is it possible that you have 2 NICs
on
> the same subnet? This can cause all kinds of problems.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Marlon" <marlon-nospam@xxxxxxxxxxx> wrote in message
> news:O933r77ZFHA.3132@xxxxxxxxxxxxxxxxxxxxxxx
> > I spoke too soon. That's correct, the article below confirms that I
> wouldn't
> > need a default gateway (and I shouldn't) set it up on the second NIC:
> > http://support.microsoft.com/d­efault.aspx?scid=kb%3ben-us%3b­157025
> >
> > In order to prove that 1.1.1.254 gateway knows the route to 2.2.2.2, I
go
> to
> > another server which does have the default gateway configured=1.1.1.254.
> > From such server I ping 2.2.2.2 successfully.
> > That means 1.1.1.254 knows the route to 2.2.2.2
> >
> >
> > Any ideas ?
> >
> > "Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:ecT8P27ZFHA.616@xxxxxxxxxxxxxxxxxxxxxxx
> > > They will all work fine provided 1.1.1.254 knows how to find 2.2.2.2.
A
> > > default gateway is not necessary. The following connects to google
just
> > > fine:
> > >
> > > Active Routes:
> > > Network Destination Netmask Gateway Interface
> > Metric
> > > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
> > > 192.168.1.0 255.255.255.0 192.168.1.189 192.168.1.189
1
> > > 192.168.1.189 255.255.255.255 127.0.0.1 127.0.0.1
1
> > > 192.168.1.255 255.255.255.255 192.168.1.189 192.168.1.189
1
> > > 216.239.39.99 255.255.255.255 192.168.1.2 192.168.1.189
1
> > > 224.0.0.0 224.0.0.0 192.168.1.189 192.168.1.189
1
> > > 255.255.255.255 255.255.255.255 192.168.1.189 192.168.1.189
1
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Neteng" <neteng.ccie@xxxxxxxxx> wrote in message
> > > news:OmWwbe7ZFHA.2288@xxxxxxxxxxxxxxxxxxxxxxx
> > > > These will not work because he has no DG. He would have to add the
> route
> > > > with the next hop being on the local subnet. A detailed explanation
> was
> > > > posted at groupstudy.
> > > >
> > > > "Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxx> wrote in
message
> > > > news:eOYMAL7ZFHA.3032@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > If the mask is correct, the command should be:
> > > > >
> > > > > route add 2.0.0.0 MASK 255.0.0.0 1.1.1.254
> > > > >
> > > > > If the network ID is correct but the mask is wrong, the command
> should
> > > be:
> > > > >
> > > > > route add 2.2.2.0 MASK 255.255.255.0 1.1.1.254
> > > > >
> > > > > Also, if you only need to reach one machine as opposed to an
entire
> > > > network,
> > > > > you can use a static route with the host IP and a full mask:
> > > > >
> > > > > route add 2.2.2.2 MASK 255.255.255.255 1.1.1.254
> > > > >
> > > > > Doug Sherman
> > > > > MCSE, MCSA, MCP+I, MVP
> > > > >
> > > > > "Magoo" <magoo-nospam@xxxxxxxxxxx> wrote in message
> > > > > news:%23mNmST6ZFHA.2900@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > > Pardon me, I sent you misinformation:
> > > > > > I have no default gateway set on the TCP/IP properties. That's
why
> I
> > > > > > configured the default route.
> > > > > > correct, assume the subnet mask is correct (I edited the IP
> address
> > > > before
> > > > > > posting this message and in the process I didn't reflect my
> correct
> > > > mask).
> > > > > >
> > > > > > Therefore all information is correct :
> > > > > > Assume I have the correct default route set with the right
subnect
> > > mask:
> > > > > > route 2.2.2.0 MASK 255.0.0.0 1.1.1.254.
> > > > > > It still returns destination host unreachable.
> > > > > > How can this be ?
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxx> wrote in
> > message
> > > > > > news:Oy2lUN6ZFHA.1368@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > > > Well first of all, if the router/computer at 1.1.1.254 knows
> where
> > > to
> > > > > send
> > > > > > > packets destined for 2.2.2.2, then there is no need for a
static
> > > > route.
> > > > > > > Second, if the router/computer at 1.1.1.254 does not know
where
> to
> > > > send
> > > > > > > packets destined for 2.2.2.2, then a static route pointing to
> that
> > > > > gateway
> > > > > > > will not help. Finally, if you want to configure a static
route
> > to
> > > > the
> > > > > > > network on which 2.2.2.2 resides, it would be 2.0.0.0 NOT
> 2.2.2.0.
> > > > > > >
> > > > > > > Doug Sherman
> > > > > > > MCSE, MCSA, MCP+I, MVP
> > > > > > >
> > > > > > > "Magoo" <magoo-nospam@xxxxxxxxxxx> wrote in message
> > > > > > > news:uyNLjF6ZFHA.1456@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > > > > I have a Win2003 server named ISA with the following
> > configuration
> > > > > under
> > > > > > > > TCP/IP Properties:
> > > > > > > >
> > > > > > > > IP address=1.1.1.1
> > > > > > > > Subnet mask=255.0.0.0
> > > > > > > > Defaut gateway=1.1.1.254
> > > > > > > >
> > > > > > > > That's it.
> > > > > > > >
> > > > > > > > Now I need to make sure this server will reach
> > > mypublisheserver.com.
> > > > > > > > On the host file of ISA Server, I put
> > > > > > > > mypublished server 2.2.2.2.
> > > > > > > >
> > > > > > > > Then I add a route:
> > > > > > > > Route add -p 2.2.2.0 MASK 255.0.0.0 1.1.1.254
> > > > > > > > I do a route print and I confirm the persistent, static
route
> > has
> > > > been
> > > > > > > > added.
> > > > > > > >
> > > > > > > > Then I ping mypublished server. It resolves to IP 2.2.2.2
> > > > > accordingly,
> > > > > > > but
> > > > > > > > it returns:
> > > > > > > > "Destination host unreachable"
> > > > > > > >
> > > > > > > > What's wrong ?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>


.



Relevant Pages

  • Re: LAN with WLAN . . .
    ... but leave the default gateway setting on the LAN NIC blank. ... When you specify a default gateway on a NIC it sets up a default route ... If you specify a default gateway on two NICs you get ...
    (microsoft.public.windows.server.networking)
  • Re: LAN with WLAN . . .
    ... but leave the default gateway setting on the LAN NIC blank. ... When you specify a default gateway on a NIC it sets up a default route ... If you specify a default gateway on two NICs you get ...
    (microsoft.public.windows.server.networking)
  • Re: Keep routing table
    ... I've just tryied with this configuration. ... i add this 2 route ... > You can only have *one* Default Gateway (other nics must remain blank). ...
    (microsoft.public.win2000.networking)
  • Re: "Routing and Remote Access" in Windows Server 2003
    ... Set the default gateway of NIC B to NIC A. ... > say that I have to make sure no filtering blocks internet address, ... > Server computer. ... > In "Routing and Remote Access" I have added both NICS. ...
    (microsoft.public.win2000.ras_routing)
  • SSL on multiple sites in a virtually hosted WinServer 2003
    ... my ISP and its address is the public gateway. ... I am hosting several websites on the server. ... This setup works fine for only one SSL enabled site. ... one of the nics but it gets confused as to which gateway to send the packets ...
    (microsoft.public.windows.server.networking)