Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

routing table issues (tcpClient app)

Status
Not open for further replies.

nicholasbach

Programmer
Apr 15, 2003
2
US
Hi,
Our company internal network is on the 192.168.16.0 subnet. We are in the process building a tcpClient application which will connect to a 3rd party vendor via a private point-to-point frame relay connection. The private network is on the 192.168.64.0 subnet. We will access this tcpClient application via a web based application.

The webserver will recieve requests, contact the private server, get a response and send it back to the client. The webserver has IPs on the internal and private network (it essentially is straddling both networks). I have added a static route on the webserver which should send 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
(192.168.64.1 is the private gateway)

From the webserver, I can successfully ping the private 3rd party server.(tracert goes through the private gateway). But, when I run the tcpClient app,it tries to connect via the internal gateway (with the static route, I would think all connections to that particular IP would go through the private gateway). Why would pinging route properly but the client not? Is there anyway I can tell the server to go to the private gateway when trying to access a certain IP?

I have been running a packet sniffer and the tcpClient always contacts the default gateway (internal network), I want it to contact the private gateway.

Hopefully this make sense.....
 
It looks like you used the wrong gateway address ...

The gateway is Between two subnets

192.168.16.0 and 192.168.64.0

You are on the 192.168.16.0 subnet so your gateway should have two interfaces like ...

192.168.16.4 and 192.168.64.5

You should establish a route to 192.168.16.4 in order to reach 192.168.64.0
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top