Dual router to wan problem

Here is my setup:

Router 1:
LAN IP 192.168.0.1
external domain name: a.mydomain.net
port 80 forwarded to 192.168.0.13

Router 2:
LAN IP 192.168.0.2
external domain name: b.mydomain.net
port 80 forwarded to 192.168.0.13

Webserver (WS2003)
IP 192.168.0.13
Default Gateway: 192.168.0.1, 192.168.0.2

I would like to be able to access the webserver from both a.mydomain.net and
b.mydomain.net. I can access the site via a.mydomain.net but not
b.mydomain.net
Is this because the server is using 192.168.0.1 as it's default gateway? Is
there anything that I can do (keeping both routers on the same subnet) that
make this work?

Your input is much appreciated

not sure the settings. Assuming all of the computers are in the same subnet,
they should be able to see each other and default gateway is not issue here.

--
For more and other information, go to http://www.ChicagoTech.net


Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.


Robert Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Marshall Lai" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Here is my setup:
>
> Router 1:
> LAN IP 192.168.0.1
> external domain name: a.mydomain.net
> port 80 forwarded to 192.168.0.13
>
> Router 2:
> LAN IP 192.168.0.2
> external domain name: b.mydomain.net
> port 80 forwarded to 192.168.0.13
>
> Webserver (WS2003)
> IP 192.168.0.13
> Default Gateway: 192.168.0.1, 192.168.0.2
>
> I would like to be able to access the webserver from both a.mydomain.net
> and
> b.mydomain.net. I can access the site via a.mydomain.net but not
> b.mydomain.net
> Is this because the server is using 192.168.0.1 as it's default gateway?
> Is
> there anything that I can do (keeping both routers on the same subnet)
> that
> make this work?
>
> Your input is much appreciated
>
>
>

"Marshall Lai" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Is this because the server is using 192.168.0.1 as it's default gateway?
Is
> there anything that I can do (keeping both routers on the same subnet)
that
> make this work?

No.
It doesn't matter if they are in the same subnet or not and it doesn't
matter what the Default Gateway is because you can only have one anyway.

One possibility would be with a *single* router that has two public
interfaces with each representing one of the domains. The device would then
have to forward port 80 traffic to the web server from "either/or" of the
two external links. The Device may also be required to have load balancing
features where it can balance between the two exteranl links.

The second possibility with two routers would be to have one of the two
routers forward port 80 to the *extenal* interface of the other router (if
they are capable of doing so).

The *right* way to do this would have been to used a *single* Internet link
that has enough bandwith to serve the purpose, then have *both* domains
registered to the same IP# of the single router on the single link.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Yes the computers and devices can see each other in the network with no
problem.
The problem lies in external connections coming into the server. The server
will only send the response to the default router no matter which router the
external request comes thru from.

For example, the server is configured with 192.168.0.1 as it's default
router. And an external connection thru the second router 192.168.0.2 is
forwarded to the server. The server will only respond to this request thru
the default router which is 192.168.0.1 so as a result, the client
connecting thru from 192.168.0.2 will not see the website......


"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> not sure the settings. Assuming all of the computers are in the same
> subnet, they should be able to see each other and default gateway is not
> issue here.
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
> help.
>
>
> Robert Lin, MS-MVP, MCSE & CNE
>
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
>
> "Marshall Lai" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Here is my setup:
>>
>> Router 1:
>> LAN IP 192.168.0.1
>> external domain name: a.mydomain.net
>> port 80 forwarded to 192.168.0.13
>>
>> Router 2:
>> LAN IP 192.168.0.2
>> external domain name: b.mydomain.net
>> port 80 forwarded to 192.168.0.13
>>
>> Webserver (WS2003)
>> IP 192.168.0.13
>> Default Gateway: 192.168.0.1, 192.168.0.2
>>
>> I would like to be able to access the webserver from both a.mydomain.net
>> and
>> b.mydomain.net. I can access the site via a.mydomain.net but not
>> b.mydomain.net
>> Is this because the server is using 192.168.0.1 as it's default gateway?
>> Is
>> there anything that I can do (keeping both routers on the same subnet)
>> that
>> make this work?
>>
>> Your input is much appreciated
>>
>>
>>
>
>

"Marshall Lai" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The problem lies in external connections coming into the server. The
server
> will only send the response to the default router no matter which router
the
> external request comes thru from.

Yes, and that is all it will ever do. That is the way it is supposed to
work. It looks at the IP# of the destination and compares it to the Routing
Table and follows the path that applies,...which will always be the Default
Gateway. Only "established" or "known" routes/destinations will follow
other routes if other routes are specified for those particular
destinations.

See my other post.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

In this case, if the single link fails, then there will be no
redundancy........
The forwarding to port 80 to the external interface of router 1 solution
seems interesting and let me try this out.....

"Phillip Windell" <@.> wrote in message
news:%(E-Mail Removed)...
> "Marshall Lai" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Is this because the server is using 192.168.0.1 as it's default gateway?
> Is
>> there anything that I can do (keeping both routers on the same subnet)
> that
>> make this work?
>
> No.
> It doesn't matter if they are in the same subnet or not and it doesn't
> matter what the Default Gateway is because you can only have one anyway.
>
> One possibility would be with a *single* router that has two public
> interfaces with each representing one of the domains. The device would
> then
> have to forward port 80 traffic to the web server from "either/or" of the
> two external links. The Device may also be required to have load balancing
> features where it can balance between the two exteranl links.
>
> The second possibility with two routers would be to have one of the two
> routers forward port 80 to the *extenal* interface of the other router (if
> they are capable of doing so).
>
> The *right* way to do this would have been to used a *single* Internet
> link
> that has enough bandwith to serve the purpose, then have *both* domains
> registered to the same IP# of the single router on the single link.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>

The proper way to have redundant lines is to work that out with the Internet
Provider so that each redundant line comes from the same provider and uses
IP#s from that same provider. The ISP's equipment on their end plays just
as big a role in the "redundancy" as does equipment on your end,....so the
two of you have to work together the make it happen. An ISP's that
specializes only in "Home user" situations will probably not be able to do
this.

There are also Cable/DSL Routers that have duel WAN ports and can
load-balance/fail-over between them. You'll have to investigate the features
of diffeent models yourself,..I have no dealings with any of those.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Marshall Lai" <(E-Mail Removed)> wrote in message
news:O%(E-Mail Removed)...
> In this case, if the single link fails, then there will be no
> redundancy........
> The forwarding to port 80 to the external interface of router 1 solution
> seems interesting and let me try this out.....
>
> "Phillip Windell" <@.> wrote in message
> news:%(E-Mail Removed)...
> > "Marshall Lai" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> Is this because the server is using 192.168.0.1 as it's default
gateway?
> > Is
> >> there anything that I can do (keeping both routers on the same subnet)
> > that
> >> make this work?
> >
> > No.
> > It doesn't matter if they are in the same subnet or not and it doesn't
> > matter what the Default Gateway is because you can only have one
anyway.
> >
> > One possibility would be with a *single* router that has two public
> > interfaces with each representing one of the domains. The device would
> > then
> > have to forward port 80 traffic to the web server from "either/or" of
the
> > two external links. The Device may also be required to have load
balancing
> > features where it can balance between the two exteranl links.
> >
> > The second possibility with two routers would be to have one of the two
> > routers forward port 80 to the *extenal* interface of the other router
(if
> > they are capable of doing so).
> >
> > The *right* way to do this would have been to used a *single* Internet
> > link
> > that has enough bandwith to serve the purpose, then have *both* domains
> > registered to the same IP# of the single router on the single link.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
>
>

Thanks. That's what I ended up doing. I bought the Linksys RV042 PN router
with can do 2 WAN(Load balance and/or failsafe), DDNS on both WANs and VPN
IPSEC. I just pass-thru pptp to my WS2003. And now everything is
perfect.....


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> The proper way to have redundant lines is to work that out with the
> Internet
> Provider so that each redundant line comes from the same provider and uses
> IP#s from that same provider. The ISP's equipment on their end plays just
> as big a role in the "redundancy" as does equipment on your end,....so the
> two of you have to work together the make it happen. An ISP's that
> specializes only in "Home user" situations will probably not be able to do
> this.
>
> There are also Cable/DSL Routers that have duel WAN ports and can
> load-balance/fail-over between them. You'll have to investigate the
> features
> of diffeent models yourself,..I have no dealings with any of those.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Marshall Lai" <(E-Mail Removed)> wrote in message
> news:O%(E-Mail Removed)...
>> In this case, if the single link fails, then there will be no
>> redundancy........
>> The forwarding to port 80 to the external interface of router 1 solution
>> seems interesting and let me try this out.....
>>
>> "Phillip Windell" <@.> wrote in message
>> news:%(E-Mail Removed)...
>> > "Marshall Lai" <(E-Mail Removed)> wrote in message
>> > news:%(E-Mail Removed)...
>> >> Is this because the server is using 192.168.0.1 as it's default
> gateway?
>> > Is
>> >> there anything that I can do (keeping both routers on the same subnet)
>> > that
>> >> make this work?
>> >
>> > No.
>> > It doesn't matter if they are in the same subnet or not and it doesn't
>> > matter what the Default Gateway is because you can only have one
> anyway.
>> >
>> > One possibility would be with a *single* router that has two public
>> > interfaces with each representing one of the domains. The device would
>> > then
>> > have to forward port 80 traffic to the web server from "either/or" of
> the
>> > two external links. The Device may also be required to have load
> balancing
>> > features where it can balance between the two exteranl links.
>> >
>> > The second possibility with two routers would be to have one of the two
>> > routers forward port 80 to the *extenal* interface of the other router
> (if
>> > they are capable of doing so).
>> >
>> > The *right* way to do this would have been to used a *single* Internet
>> > link
>> > that has enough bandwith to serve the purpose, then have *both* domains
>> > registered to the same IP# of the single router on the single link.
>> >
>> > --
>> >
>> > Phillip Windell [MCP, MVP, CCNA]
>> > www.wandtv.com
>> >
>> >
>>
>>
>
>