From: "Geo" 

Depending on the setup you may be entering the IP address of the sql server
or of the router. If it is the IP of the router they have probably mapped
some ports like 1433 and 1434 to the sql server and are running NAT on the
router.

Geo.

"Ellen K."  wrote in message
news:qpa5l153qnguhl2mvkl5qge822gtn0se22{at}4ax.com...
> This is all inside our firewall (and on our physical premises).  The eOn
> router and the stuff behind it are just not in our (only) domain.  To
> get to the eOn SQL Server box I have to use the IP address of the eOn
> router.  As mentioned in my other posts, this works fine from my
> desktop, from "my" servers, and to set up a DSN on the fat client to
> talk to the eOn database via ODBC.  But I am curious how the eOn router
> knows which of the devices behind it incoming messages are for.
>
> On Sun, 16 Oct 2005 11:40:50 -0400, "Geo"
 wrote in
> message :
>
> >You don't use the routers IP address except in the case of NAT where
there
> >are ports mapped to the sql box. On an internal network you would use the
IP
> >address of the sql box.
> >
> >Geo.
> >
> >"Ellen K."  wrote in message
> >news:oet3l1dn7vem1fv56q6djr2n5mugt7k4jq{at}4ax.com...
> >> How does the router know which of the devices behind it the message is
> >> trying to reach?
> >>
> >> On Fri, 14 Oct 2005 18:08:21 -0400, "Geo"
 wrote in
> >> message :
> >>
> >> >"Tony Williams"  wrote in message
> >> >news:43501322{at}w3.nls.net...
> >> >
> >> >> The business of using the router's IP address seems
like it could
cause
> >> >> problems, but I don't know enough about the setup to
offer any more
> >> >> suggestions other than to get a packet trace to see
exactly what's
> >going
> >> >> where.
> >> >
> >> >I do it all the time, it's usually more reliable if anything.
> >> >
> >> >Geo.
> >> >
> >>
> >
>

--- BBBS/NT v4.01 Flag-5