12-05-2005 10:57 AM - edited 03-09-2019 01:15 PM
I cannot access my web server that is located on the DMZ from the inside. I can ping the servers nic and all the web site IPs from the PIX. I have the following in my config:
static (inside,dmz1) 10.10.0.0 10.10.0.0 netmask 255.255.0.0 0 0. 10.10.0.0 is the network on the inside. I am able to access the websites from the outside. I am using all static and acl's. I have a webfarm and the two servers ip's are 172.16.1.3 and 172.16.1.4. Thanks, Jay
12-05-2005 03:36 PM
Please provide your complete config. Hide the public addresses.
what is the private IPO of the server you cant access.
any log messages you can provide?
what version of PIX
12-06-2005 04:25 AM
Below is the config with ??? for the public ips and passwords. I am new at this and am not sure what you mean by private IPO. There are two servers, one nic's ip is 172.16.1.3 and the other is 172.16.1.4. They both have the same websites on them. The site I am testing with is 172.16.1.30. How do I provide the log messages you need?
pix1# sho logging
Syslog logging: disabled
Facility: 20
Timestamp logging: disabled
Standby logging: disabled
Console logging: disabled
Monitor logging: disabled
Buffer logging: level debugging, 13320 messages logged
Trap logging: disabled
History logging: disabled
Device ID: disabled
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 100full
interface ethernet2 auto
interface ethernet3 auto shutdown
interface ethernet4 auto shutdown
interface ethernet5 auto shutdown
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz1 security50
nameif ethernet3 intf3 security6
nameif ethernet4 intf4 security8
nameif ethernet5 intf5 security10
enable password ??????
passwd ????? encrypted
hostname pix1
domain-name ??????
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 out-to-in permit tcp any host ??.??.??.?? eq www
access-list out-to-in permit tcp any host ??.??.??.?? eq https
pager lines 24
logging buffered debugging
mtu outside 1500
mtu inside 1500
mtu dmz1 1500
mtu intf3 1500
mtu intf4 1500
mtu intf5 1500
ip address outside ??.??.??.?? 255.255.255.224
ip address inside 10.10.1.210 255.255.0.0
ip address dmz1 172.16.1.2 255.255.255.224
no ip address intf3
no ip address intf4
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 dmz1
no failover ip address intf3
no failover ip address intf4
no failover ip address intf5
pdm history enable
arp timeout 14400
static (inside,dmz1) 10.10.0.0 10.10.0.0 netmask 255.255.0.0 0 0
static (inside,outside) ??.??.??.?? 10.10.9.38 netmask 255.255.255.255 0 0
static (dmz1,outside) ??.??.??.?? 172.16.1.30 netmask 255.255.255.255 0 0
access-group out-to-in in interface outside
route outside 0.0.0.0 0.0.0.0 ??.??.??.?? 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 RADIUS protocol radius
aaa-server LOCAL protocol local
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 10.10.0.0 255.255.0.0 inside
telnet timeout 20
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:xxxx
: end
Thanks...Jay
12-06-2005 05:21 AM
i am guessing you can't access the webserver by name, as you mentioned you can ping the ip. "alias" needs to be configured.
e.g.
alias (inside) 172.16.1.30 ??.??.??.?? 255.255.255.255
12-06-2005 06:04 AM
I am trying to access the site my typing http://172.16.1.30 in the browser.
12-13-2005 11:55 AM
According to this config, only the host 10.10.9.38 can reach the Internet from the inside network via this static command:
static (inside,outside) ??.??.??.?? 10.10.9.38 netmask 255.255.255.255 0 0
This static is correct and will let the inside reach the DMZ:
static (inside,dmz1) 10.10.0.0 10.10.0.0 netmask 255.255.0.0 0 0
There is no ACL on the DMZ interface that would be preventing this connection. Problem might be server related - might be. All you need to access machines located in the DMZ from the inside is a static command which you have and it looks correct.
Try the capture to see what is actually (if anything) is coming back from the server>
Also, the log entry you posted shows the xlate being set up when you browse to that web server.
Here is a troubleshooting tip. At this point I would creat a capture on the DMZ interface like this:
access-list cap1 permit ip host 172.16.1.30 host
capture webcap access-list cap1 interface dmz1
Then try to browse to the server. After the session times out look at the capture to see if packets are comming back to you.
show capture webcap cap1 detail
The capture results will determine your next step.
12-08-2005 05:05 AM
nkhawaja, I was able to capture some logging on a telnet session to the PIX. I weeded thru the many lines and saved the lines that apply to my pc 10.10.1.207 on the inside and the dmz site 172.16.1.30.
Hope this helps...
Jay
12-13-2005 07:04 AM
Oops forgot the log:
710005: UDP request discarded from 10.10.1.207/138 to inside:10.10.255.255/netbi
os-dgm
302013: Built outbound TCP connection 1407 for dmz1:172.16.1.30/80 (172.16.1.30/
80) to inside:10.10.1.207/1540 (10.10.1.207/1540)
710005: UDP request discarded from 0.0.0.0/68 to dmz1:255.255.255.255/bootps
302014: Teardown TCP connection 1392 for dmz1:172.16.1.7/80 to inside:10.10.2.99
/2715 duration 0:02:02 bytes 0 SYN Timeout
305009: Built static translation from inside:10.10.2.166 to dmz1:10.10.2.166
302013: Built outbound TCP connection 1408 for dmz1:172.16.1.8/80 (172.16.1.8/80
) to inside:10.10.2.166/1152 (10.10.2.166/1152)
710005: UDP request discarded from 0.0.0.0/68 to dmz1:255.255.255.255/bootps
710005: UDP request discarded from 0.0.0.0/68 to dmz1:255.255.255.255/bootps
710005: UDP request discarded from 0.0.0.0/68 to dmz1:255.255.255.255/bootps
12-13-2005 12:39 PM
Looks like server maybe just not responding?
Do a 'route print' on the server. Make sure your 10.10.x.x addresses don't exist somewhere.
Issue a clear xlate and try again.
12-22-2005 06:56 PM
I think you just need to add an access-list on the inbound side of the DMZ. Try a permit all just test and modify it to close down unused ports.
access-list dmz-in perm ip any any
access-group dmz-in in interface DMZ
12-27-2005 06:07 AM
I was able to get some capture information after all the above suggestions. I have 2 issues. One, I cannot access the DMZ1 websites from the inside. Two, I cannot access the inside websites from the outside through the outside router. I can access the inside websites from a pc configured with a public IP connected to the outside switch. I can access websites on DMZ1 from the outside through the router. When I try to access the inside websites I see the xlate being done but no response. I was not able to get a capture on any port when trying to access the inside from the outside. Attached is the current config and captures. THANKS....
12-28-2005 01:29 PM
Well, the capture shows packets coming from the server on port 80 and being passed to the client on the inside interface. To be honest with you, it doesn't look like a firewall issue.
When you try to browse to the web server does the hitcnt increment on the dmz ACL? If so the problem is not at the firewall.
-Mark
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide