Accessing server behind PIX 501

[itnat]

I'm having problems accessing one of my servers behind a PIX 501. The server is in our lab. I am able to get from the lab to the production network and to the Internet just fine. I need to be able to control the server via Remote Desktop from my laptop, some times plugged into the network and some times via wireless.

I have tried several suggestions found online, Cisco's documention and from Cisco PIX Firewalls book. But still getting nowhere. After several config changes we started having a problem accessing 2 of our production servers so I defaulted the PIX and set it to a basic config. We were then able to reach the 2 production servers again.

Thanks in advance for any help.

Lab network is 192.168.3.x
Production network is 192.168.1.x

Here is my PIX config.

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
hostname labpix
domain-name lab.xxxxx.com
clock timezone EST -5
clock summer-time EDT recurring
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
pager lines 24
logging on
logging trap informational
logging host outside 192.168.1.31
logging host outside 192.168.1.4
logging host outside 192.168.1.183
logging host inside 192.168.3.3
mtu outside 1500
mtu inside 1500
ip address outside 192.168.1.27 255.255.255.0
ip address inside 192.168.3.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.1.31 255.255.255.255 outside
pdm location 192.168.1.4 255.255.255.255 outside
pdm location 192.168.1.183 255.255.255.255 outside
pdm location 192.168.3.3 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 192.168.1.1 1
timeout xlate 0:05: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.1.0 255.255.255.0 outside
http 192.168.3.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.3.40-192.168.3.129 inside
dhcpd dns 192.168.1.3
dhcpd wins 192.168.1.3
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain lab.xxxxxxx.com
dhcpd auto_config outside
dhcpd enable inside

 

[Decryptk33p3r]

Best way to do this is a client VPN connection through the PIX into the trusted network then w/remote desktop you can access it. Or do a static one for one translation & open yourself up to the world. VPN is the way to go.
Mike