Hmmm.. For me it looks like ssh configuration problem, not a firewalling issue...

The thing is every time I try to SSH back into my box I also try FTP and that will not work.

I dont know, Ive been playing with that gShield. Im going to try to make a configuration as close as I can to the script and see what differences it makes. That may help me to discover what the problem is with my script.

-Scott

In your ftp part of the firewall you only allow ESTABILISHED and RELATED, not NEW packets, so a connection cannot be made (or I can't see the right fragment).

Several large problems in both versions of rules,
but a couple of questions first...

You are Masquerading everything outward on eth1, which means it is your "Internet" interface, YES?
You are directing traffic to a couple of internal servers, 10.0.0.3 & 4 YES?
You have some servers on the firewall, at least http, ssh, ftp YES?

There are a lot of OUTPUT rules, which will block any traffic the firewall itself generates, including dns queries which ssh may want for verification.
I suggest you comment them ALL out and change the POLICY to ACCEPT. There should be no reason to mistrust what the firewall itself generates, not just yet...

Remove the INPUT -s *my.ip.add.ress* -j DROP rule. The rp_filter does this.

I suggest you add some -j LOG rules immediately before any -j DROP rules and last of all on any DROP POLICY chains, to catch the information until you get an idea what is happening. eg
iptables -A INPUT -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -m state --state NEW -j LOG --log-prefix "INPUT_NEW_!_SYN " --log-level 6
iptables -A INPUT -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -m state --state NEW -j DROP

These can be viewed with "tail -f /var/log/messages" in a default syslog install.

I suggest you add at least...
iptables -A FORWARD -i eth1 -o eth0 -p tcp ! --syn -m state NEW -j DROP
iptables -A FORWARD -i eth1 -o eth0 -m state --state INVALID -j DROP
iptables -A FORWARD -i eth1 -o eth0 -f -j DROP
for protection in the FORWARD chain. Fragments should be handled inside netfilter automatically, but in case...

Because there are similar port descriptions in the INPUT chain and the PREROUTING chains, I think you may be confusing the packet paths.
INPUT is only used for packets which will stop on the firewall, usu at a server on the firewall.
FORWARD is for the packets going to LAN based servers.
Forwarded packets go through PREROUTING, FORWARD & POSTROUTING chains

See how that goes..
Regards,
Peter