PIX 515e. DMZ to inside static mapping

[Maggs29]

I spent the last few days trying to get this to work and am baffled as to what I am doing wrong.
I need to have packets forwarded from a DMZ interface back to the inside interface on MSSQL port, which is 1433. But I can't seem to get it to work.

I have done what was suggested in an earlier post:

static (DMZ1, inside) 192.168.130.2 192.168.130.2 netmask 255.255.255.255

access-list dmz1_in permit tcp host 192.168.130.2 host 192.168.128.110 eq 1433

access-group dmz1_in in interface dmz1

Does this look correct?
I have a syslog server running and when I try to telnet into port 1433 from the dmz1 it says "No translation group found for tcp src DMZ1:192.168.130.2/1120 dst inside:192.168.128.110/1433

Config (with some cleanup for security) below:

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
interface ethernet3 auto
interface ethernet4 auto
interface ethernet5 auto shutdown
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 DMZ2 security50
nameif ethernet3 DMZ1 security50
nameif ethernet4 DMZ security60
nameif ethernet5 intf5 security10
enable password XXXXXXXXXXX encrypted
passwd XXXXXXXXXX encrypted
hostname fw
domain-name domain.com.au
clock timezone EST 10
clock summer-time EDT recurring last Sun Oct 2:00 last Sun Mar 3:00
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list dmz1_in permit tcp host 192.168.130.2 host 192.168.128.110 eq 1433
pager lines 24
logging on
logging timestamp
logging console informational
logging trap informational
logging host inside hostname
mtu outside 1500
mtu inside 1500
mtu DMZ2 1500
mtu DMZ1 1500
mtu DMZ 1500
mtu intf5 1500
ip address outside 192.168.132.200 255.255.255.0
ip address inside 192.168.128.250 255.255.255.0
ip address DMZ2 10.0.0.2 255.255.255.0
ip address DMZ1 192.168.130.200 255.255.255.0
ip address DMZ 172.16.31.1 255.255.255.0
no ip address intf5
ip audit info action alarm
ip audit attack action alarm
no failover
failover timeout 0:00:00
failover poll 15
no failover ip address outside
no failover ip address inside
no failover ip address DMZ2
no failover ip address DMZ1
no failover ip address DMZ
no failover ip address intf5
arp timeout 14400
global (outside) 10 interface
global (inside) 10 interface
nat (inside) 10 0.0.0.0 0.0.0.0 0 0
static (DMZ1,inside) 192.168.130.2 192.168.130.2 netmask 255.255.255.255 0 0
access-group dmz1_in in interface DMZ1
route outside 0.0.0.0 0.0.0.0 192.168.132.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 192.168.128.52 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 192.168.1.2 255.255.255.255 inside
telnet 192.168.128.52 255.255.255.255 inside
telnet timeout 10
ssh timeout 5
console timeout 0
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
: end
[OK]

 

[Maggs29]

This can probably be ignored.
The problem was (I'm big enough to admit my mistake), the test machine had our production firewall as the default gateway, rather then the PIX that I'm currently testing. Changed this and it all worked.
It's always something so simple isn't it