Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

PIX 501 connecting two internal networks

I am using a PIX 501 to protect our internal network 10.0.0.0 (inside interface) from a seperate internal network 192.168.1.0 (outside interface) consultants have access to this 192 network, but I need to connect to machines on the 192.168.1.0 network using remote desktop and other similar apps.

My config looks like this

PIX Version 6.3(5)

interface ethernet0 auto

interface ethernet1 100full

nameif ethernet0 outside security0

nameif ethernet1 inside security100

hostname res6scadapix

domain-name themdc.net

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

access-list acl_in permit ip any host 10.15.10.11

pager lines 24

logging on

logging trap informational

logging host inside 10.1.57.1

mtu outside 1500

mtu inside 1500

ip address outside 192.168.1.25 255.255.255.0

ip address inside 10.15.10.25 255.255.0.0

ip audit info action alarm

ip audit attack action alarm

pdm location 10.0.0.0 255.0.0.0 inside

pdm history enable

arp timeout 14400

global (outside) 1 interface

nat (inside) 1 10.0.0.0 255.0.0.0 0 0

static (inside,outside) 192.168.1.11 10.15.10.11 netmask 255.255.255.255 0 0

access-group acl_in in interface inside

route inside 0.0.0.0 0.0.0.0 10.15.0.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 sip-disconnect 0:02:00 sip-invite 0:03: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 10.0.0.0 255.0.0.0 inside

no snmp-server location

no snmp-server contact

snmp-server community public

no snmp-server enable traps

floodguard enable

telnet 10.0.0.0 255.0.0.0 inside

telnet timeout 5

ssh timeout 5

console timeout 0

terminal width 80

From the inside network I try a remote desktop connection to 10.15.10.11, but it fails and I can't seem to get any syslog messages that would give me any help. Am I setting this up correctly? What would be the correct way to set this up?

I am on the 10.15.0.0 255.255.0.0 network, and I want to connect to the 192.168.1.0 255.255.255.0 network. I can not connect directly to the 192.168.1.0 machines because I am using that IP range somewhere else on our network. Therefore, I am trying to add a translation so that from the 10.15.0.0 network I can connect to a machine on the 192.168.1.0 network by connecting to an ip address on the 10.15.0.0 network. 10.5.x.x is inside, and 192.168.1.x is outside.

3 REPLIES
Silver

Re: PIX 501 connecting two internal networks

I'm a little confused. When you say:

>From the inside network I try a remote >desktop connection to 10.15.10.11, but it >fails

What are you calling the "inside" network?

Community Member

Re: PIX 501 connecting two internal networks

the inside network was the 10 network. the outside network is the 192 network. I resolved the issue by changing my static map from

static (inside,outside) 192.168.1.11 10.15.10.11 netmask 255.255.255.255

to

static (outside,inside) 10.15.10.11 192.168.1.11 netmask 255.255.255.255

Now it works.

Silver

Re: PIX 501 connecting two internal networks

If you mean that you are coming from the 192.168.x.x side, then you have applied your access-list incorrectly.

>access-group acl_in in interface inside

should be:

access-group acl_in in interface outside

and the access list should be changed to:

access-list acl_in permit ip any host 192.168.1.11

167
Views
0
Helpful
3
Replies
CreatePlease to create content