Odd routing problem Outside of Firewall In

[compuveg]

Ok, here's the network, 63.19.67.0/25

The router is 63.19.67.1
The firewall's external interface is 67.19.67.1
This firewall's external interface is 63.19.67.3

The firewall is in front of 2 webservers. One is 63.19.67.32.

There is a FTP server behind the router, and in front of he firewall. 63.19.67.50. I've configured this a number of ways, but generally with an IP of 63.19.67.40 and a subnet mask of 255.255.255.128 and a default gateway of 63.19.67.1. I've also tried the subnet mask all the way out to 255.255.255.254.

In either setting, the outside world has no trouble with the server, but it is inaccessible to internal users, and is also unable to reach the 2 internal webservers.

I've also tried to add routes pointing to the webservers or internal network. For example;

route add 63.19.67.32 mask 255.255.255.255 63.19.67.3

and that doesn't seem to work. Any ideas with what I'm doing wrong?

Thanks--

 

[compuveg]

Well, turns out the PIX firewall had a bad entry in the ARP table. I had to do a...

no arp 63.19.67.50

...command and everything took off the way it should. Sheesh. This problem came up Thursday and I thought the PIX would have rebuilt the ARP tables by now. Guess not.

 

[brianinms]

Um, why would you have hosts infront of your firewall.

 

[compuveg]

Well, it was that way when I got here, basically. It is just a junk box, used for only FTP, so people can leave us files or we can post them for people, without bothering the webmaster.