Networks

Ask something
Question Locked

Allow SQL access thru a Cisco PIX 501 VPN

0 helpful
4 replies

by deputycruse

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I want to allow access to SQL through a PIX 501 VPN. I want to allow clients to dial in to the VPN and access the SQL database over the VPN connection. My configuration is below. The SQL server is 10.0.0.2; any assistance would be appreciated.

Building configuration...
: Saved
:
PIX Version 6.3(5)
interface ethernet0 10full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password XXXXXXXXXXX encrypted
passwd XXXXXXXXXX encrypted
hostname MDTVPN
domain-name XXXXX.XXX
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 ils 389
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 inside_outbound_nat0_acl permit ip any 10.0.9.0 255.255.255.0
access-list 101 permit ip 10.0.0.0 255.240.0.0 10.0.0.0 255.240.0.0
access-list 101 permit ip 10.0.0.0 255.240.0.0 192.168.10.0 255.255.255.0
access-list 101 permit ip any 10.0.9.0 255.255.255.0
no pager
mtu outside 1500
mtu inside 1500
ip address outside XX.XX.XX.XX 255.255.255.252
ip address inside 10.0.0.4 255.240.0.0
ip audit info action alarm
ip audit attack action alarm
ip local pool MDT 10.0.9.1-10.0.9.200 mask 255.240.0.0
ip local pool vpnpool 10.10.9.1-10.10.9.200 mask 255.240.0.0
pdm location 10.0.9.0 255.255.255.0 outside
pdm location 10.0.0.0 255.240.0.0 outside
pdm location 192.168.10.0 255.255.255.0 outside
pdm location 10.0.0.0 255.0.0.0 inside
pdm location XX.143.0.0 255.255.0.0 inside
pdm location XX.143.0.0 255.255.0.0 outside
pdm location XX.0.0.0 255.0.0.0 inside
pdm location XX.111.69.0 255.255.255.0 inside
pdm location XX.124.61.0 255.255.255.0 inside
pdm location XX.158.150.0 255.255.255.0 inside
pdm location XX.52.101.0 255.255.255.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 10.10.8.5-10.10.8.155 netmask 255.240.0.0
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 67.158.150.157 1
route inside XX.111.69.0 255.255.255.0 10.0.0.1 1
route inside XX.124.61.0 255.255.255.0 10.0.0.1 1
route inside XX.158.150.0 255.255.255.0 10.0.0.1 1
route inside XX.52.101.0 255.255.255.0 10.0.0.1 1
route inside XX.0.0.0 255.0.0.0 10.0.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.240.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
sysopt connection permit-l2tp
isakmp enable outside
isakmp keepalive 3550 55
isakmp nat-traversal 3550
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption aes
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup MDT address-pool vpnpool
vpngroup MDT dns-server 10.0.0.1 10.0.0.2
vpngroup MDT wins-server 10.0.0.1 10.0.0.2
vpngroup MDT default-domain leonet.local
vpngroup MDT idle-time 1800
vpngroup MDT password ********
telnet 10.0.0.0 255.240.0.0 inside
telnet timeout 15
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 10
console timeout 0
vpdn group 1 accept dialin pptp
vpdn group 1 ppp authentication pap
vpdn group 1 ppp authentication chap
vpdn group 1 ppp authentication mschap
vpdn group 1 ppp encryption mppe auto
vpdn group 1 client configuration address local MDT
vpdn group 1 client configuration dns 10.0.0.1 10.0.0.2
vpdn group 1 client configuration wins 10.0.0.1 10.0.0.2
vpdn group 1 pptp echo 60
vpdn group 1 client authentication local
vpdn username dtf password *********
vpdn enable outside
dhcpd address 10.0.0.5-10.0.1.4 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
: end
[OK]

4 replies

by dumphrey

you should not need to do any thing else to allow sql access. This is supposing you have not limited access through an acl.
The process can be enhanced by adding a radius server to authenticate users with AD, and to provide access to network resources through AD.

aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server RADIUS (inside) host (ip address)(pre-shared key) timeout 10

And adding the line:
vpngroup (group name) authentication-server RADIUS
to your vpngroup config.

the windows radius server in Routing and remote access works just fine with this and sets up in a minute or so after its added through add/remove programs. Setting up the policies takes a bit longer but worth it.

[EDIT]
What in particular is the problem with the set up? Can the clients connect to VPN or not? And if so what error on connecting to SQL?

by deputycruse

I have no problem authenticating, I can ping any computer as well as access resources on the internal network. I cannot access an MS SQL 2000 instance on a server that I can ping. I have tried to access it thru ODBC connections. What would the policies be under the Radius server in windows 2003 server? as far as a more difficult setup but well worth it? I also need some assistance with routing internet traffic through 10.0.0.1 if you have any suggestions.

Thanks,

Brian

by vicki.fox

Try removing the inspect sql statement out of your configuration. I just had a similar problem. Folks could only open databases smaller than 5ish records. Once I removed that, they could open files as large as 1.5 million records.

This discussion is closed to new replies.