Hi,
I we are running SBS2000. We are building an application
which will connect to a 3rd party vendor via a private
point-to-point frame relay connection.

Our internal SBS network is on the 192.168.16.0 subnet and
the private network is on the 192.168.64.0 subnet. We
have a webserver which will recieve requests, contact the
private server, get a response and send it back to the
client. The webserver has an IP on the internal and
private network (it essentially is straddling both
networks). I have added a static route on the webserver
sending all requests for a certain IP to the private
network.
>>route add xxx.xxx.xxx.0 MASK 255.255.255.0 192.168.64.1

From the webserver, I can successfully ping the private
3rd party server via our private network (tracert goes
through the private gateway). When I run the tcpClient
app (called from the webserver), it tries to connect via
the internal gateway (with the static route, it should be
using the private gateway). Why would pinging route
properly but the client not? Is there something I need to
do at the SBServer level to force all requests for the
private network to the private gateway? (I thought the
static route would handle it)

I'm kinda stumped...

Re: shot in the dark - routing issues by Mark

Mark
Fri May 21 21:31:09 CDT 2004

I've always found it best to configure p2p with Netopia routers instead of
using the server as a router.

--
Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com



"nic" <anonymous@discussions.microsoft.com> wrote in message
news:1057501c43f63$78e87930$a001280a@phx.gbl...
> Hi,
> I we are running SBS2000. We are building an application
> which will connect to a 3rd party vendor via a private
> point-to-point frame relay connection.
>
> Our internal SBS network is on the 192.168.16.0 subnet and
> the private network is on the 192.168.64.0 subnet. We
> have a webserver which will recieve requests, contact the
> private server, get a response and send it back to the
> client. The webserver has an IP on the internal and
> private network (it essentially is straddling both
> networks). I have added a static route on the webserver
> sending all requests for a certain IP to the private
> network.
> >>route add xxx.xxx.xxx.0 MASK 255.255.255.0 192.168.64.1
>
> From the webserver, I can successfully ping the private
> 3rd party server via our private network (tracert goes
> through the private gateway). When I run the tcpClient
> app (called from the webserver), it tries to connect via
> the internal gateway (with the static route, it should be
> using the private gateway). Why would pinging route
> properly but the client not? Is there something I need to
> do at the SBServer level to force all requests for the
> private network to the private gateway? (I thought the
> static route would handle it)
>
> I'm kinda stumped...
>



Re: shot in the dark - routing issues by Jim

Jim
Sat May 22 15:27:11 CDT 2004

I did this three years ago and forget the steps. I think basically I
had a router connected to the remote location. The internal network is
192.168.16.x. SBS is 192.168.16.2 The router had an internal static ip
of 192.168.16.3. I went to the command prompt of the server and did a
route add x.x.x.x mask 255.255.255.0 192.168.16.3 p or persistent. Now
the SBS knows that any request from a workstation to x.x.x.x goes
through that router. I think Mark M was suggesting the same but maybe
not. It may be possible that the router at the other end has to have a
routing table. I think I may have been in the router at both ends but
it has been a long time ago.

"nic" <anonymous@discussions.microsoft.com> wrote:

>Hi,
>I we are running SBS2000. We are building an application
>which will connect to a 3rd party vendor via a private
>point-to-point frame relay connection.
>
>Our internal SBS network is on the 192.168.16.0 subnet and
>the private network is on the 192.168.64.0 subnet. We
>have a webserver which will recieve requests, contact the
>private server, get a response and send it back to the
>client. The webserver has an IP on the internal and
>private network (it essentially is straddling both
>networks). I have added a static route on the webserver
>sending all requests for a certain IP to the private
>network.
>>>route add xxx.xxx.xxx.0 MASK 255.255.255.0 192.168.64.1
>
>From the webserver, I can successfully ping the private
>3rd party server via our private network (tracert goes
>through the private gateway). When I run the tcpClient
>app (called from the webserver), it tries to connect via
>the internal gateway (with the static route, it should be
>using the private gateway). Why would pinging route
>properly but the client not? Is there something I need to
>do at the SBServer level to force all requests for the
>private network to the private gateway? (I thought the
>static route would handle it)
>
>I'm kinda stumped...

Jim B. SBS MVP
remove the mvp to send email