Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AD replication and DNS issues

Status
Not open for further replies.

cambo2k

MIS
Feb 7, 2001
111
0
0
CA
I recently changed one of my sites over to a cable modem and PIX 501 VPN connection (Cost savings to move it from a 3rd party managed WAN).
However the DHCP clients are not registering with DNS. They are showing the "Active lease, DNS dynamic update pending. This address is not available for lease by the DHCP server" icon.
There are no errors on the internal server related to DNS or DHCP.
Thoughts or ideas? More info required?

Thanks!
 
Can you post a config? Also, where are the DHCP and DNS servers (behind the 501 or the headend device?)


Brent
Systems Engineer / Consultant
CCNP, CCSP
 
I will try and post a config. In the meantime - the server is a member server inside the PIX, the pix connects to our VPN concentrator. Once inside the concentrator the PDC is right beside it.

 
So is the local member server is providing DNS and DHCP? Check to see if the DHCP server is running on the pix.

Are there any ACL restricing the traffic across the VPN?

I have a similar setups at some clients and they work, so we should be able to get yours up and running.



Brent
Systems Engineer / Consultant
CCNP, CCSP
 
local server is dhcp only.
Dhcp is NOT running on the PIX
I opened up the ACL as a temp measure.

Still have to get the config... sorry for the delay
 
Here is the config now running. I opened it up pretty well all the way as a test.


interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password encrypted
passwd encrypted
hostname HOST-pix
domain-name xxx.com
fixup protocol dns maximum-length 1500
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 137-139
fixup protocol ils 389
fixup protocol ils 445
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 101 permit ip 10.160.x.0 255.255.255.0 10.160.0.0 255.255.0.0
access-list 101 permit ip 10.160.x.0 255.255.255.0 x.y.200.0 255.255.255.0
access-list 101 permit ip 10.160.x.0 255.255.255.0 x.y.102.0 255.255.255.0
access-list 101 permit ip 10.160.x.0 255.255.255.0 x.y.104.0 255.255.255.0
access-list 101 permit ip 10.160.x.0 255.255.255.0 x.y.101.0 255.255.255.0
access-list 101 permit ip 10.160.x.0 255.255.255.0 x.y.103.0 255.255.255.0
access-list 101 permit ip 10.160.x.0 255.255.255.0 host 209.112.14.5
access-list 101 permit ip 10.160.x.0 255.255.255.0 1.2.3.0 255.255.255.0
access-list outside permit icmp any any
access-list outside permit tcp any any
access-list outside permit udp any any
access-list inside permit icmp any any
access-list inside permit tcp any 10.160.0.0 255.255.0.0
access-list inside permit tcp any x.y.200.0 255.255.255.0
access-list inside permit tcp any x.y.102.0 255.255.255.0
access-list inside permit tcp any x.y.101.0 255.255.255.0
access-list inside permit tcp any x.y.103.0 255.255.255.0
access-list inside permit tcp any x.y.104.0 255.255.255.0
access-list inside permit tcp any any
access-list inside permit tcp any 10.160.p.0 255.255.255.0
access-list inside permit tcp any 10.160.q.0 255.255.255.0
access-list inside permit tcp any 10.160.r.0 255.255.255.0
access-list inside permit tcp any 10.160.s.0 255.255.255.0
access-list inside permit tcp any 10.160.t.0 255.255.255.0
access-list inside permit tcp any 10.160.u.0 255.255.255.0
access-list inside permit tcp any 10.160.v.0 255.255.255.0
access-list inside permit tcp any 10.160.w.0 255.255.255.0
access-list inside permit tcp any 10.160.x.0 255.255.255.0
access-list inside permit udp any any
access-list vpn permit ip 10.160.x.0 255.255.255.0 any
access-list vpn permit ip 10.160.45.0 255.255.255.0 any
pager lines 24
logging on
mtu outside 1500
mtu inside 1500
ip address outside 1.2.3.2 255.255.255.0
ip address inside 10.160.x.1 255.255.255.0
ip verify reverse-path interface outside
ip verify reverse-path interface inside
ip audit info action alarm
ip audit attack action alarm
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group outside in interface outside
access-group inside in interface inside
route outside 0.0.0.0 0.0.0.0 1.2.3.1 255.255.255.0
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 RADIUS protocol radius
aaa-server LOCAL protocol local
url-server (outside) vendor websense host 10.160.1.54 timeout 5 protocol TCP version 1
http server enable

no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set aptset esp-aes-256 esp-sha-hmac
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto map aptmap 10 ipsec-isakmp
crypto map aptmap 10 match address vpn
crypto map aptmap 10 set peer 5.6.7.8
crypto map aptmap 10 set transform-set aptset
crypto map aptmap interface outside
isakmp enable outside
isakmp key key here address 5.6.7.8 netmask 255.255.255.255
isakmp identity address
isakmp keepalive 1800 60
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption aes-256
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400

telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 60
management-access inside
console timeout 0
terminal width 80

 
That looks ok. I would drop the inside ACL. By default all traffic is allowed from a higher security interface to a lower one. Can you query the DNS server from the remote site? (You can download M$ Portqry v2. It does a decent job.)
What are the ACLs on the main sites firewall for IPSEC traffic protection? Are they mirror images? You can add
sysopt connection permit ipsec
(as a temporary measure only) to both firewalls to test if an ACL applied to an outside interface is blocking access.



Brent
Systems Engineer / Consultant
CCNP, CCSP
 
I got this one figured out (i think). When the PIX was put in it was set to dhcpd to pick up the IP etc before the ISP made it static. This put in the DNS as well and i did not clear the translation tables on the PIX so it was remembering the DHCPD settings.

Thanks for you help!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top