 |  |
At 1:44 PM -0500 10/1/01, <listaccount@starionline.com> wrote:
Re: Load balance not working...
From: Men & Mice Support
Date: Monday, October 1, 2001
Time: 12:20:12 pm
> > Very interesting. I'm currently seeing about 50% of traffic going to
> > each web server, from each DNS server.
> >
> > The reason I asked about the NAT setup was, most NAT servers have a
> > problem that would affect this. It seems like yours doesn't, or at
> > least it doesn't currently.
> >
> > Normally, QuickDNS Load Balancer opens a connection to each web
> > server on port 80. However, if both QuickDNS and the web server are
> > behind the same NAT server, with most NAT servers, Load Balancer
> > won't be able to connect to the web server. This is because Load
> > Balancer, in the setup you describe below, would be trying to connect
> > to 64.19.34.128, not 192.168.1.101.
>
>Now I'm really confused. I don't see how NAT translation affects this. I
>can access the web server from inside or outside the network. Outside using
>the 64 number, and inside using the 64 or the 192 number. It's making a
>connection any way I enter it.
OK, then you have a good NAT server that doesn't have that problem
(as evidenced by the fact that you can connect from the inside to the
64.x.x.x address).
>I guess I don't understand why I can't get the Load Balancer Tester to show
>that's it's indeed load balancing. Maybe because I'm running it from inside
>one of the networks that the DNS server is on? And why would this normally
>be a problem? I mean if I can connect with either the 64 or 192 address
>from within the network, shouldn't the LB Tester be able to also?
Yes, well, the LB Tester utility doesn't connect to the web servers.
It connects to QuickDNS.
Is it still showing a "non-LB response"? Or does it have a different
error message? Or what?
> > However, it seems to be working now. Either your NAT server doesn't
> > have this problem or you've worked around it.
>
>Whatever I did to avoid whatever issue your talking about was purely
>accidental and not by design. :) I think we pretty much just have a one
>address NAT table. One outside IP to one inside IP.
The issue is called one-way NAT. Most NAT servers only support
one-way NAT, not two-way NAT (aka local NAT).
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com Making DNS Easy
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696