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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Cannot connect to Internet..

Here is my config:

PfafflPix# sh config

: Saved

: Written by enable_15 at 10:30:50.250 UTC Wed Sep 3 2003

PIX Version 6.3(1)

interface ethernet0 100full

interface ethernet1 100full

nameif ethernet0 outside security0

nameif ethernet1 inside security100

enable password 8Ry2YjIyt7RRXU24 encrypted

passwd 2KFQnbNIdI.2KYOU encrypted

hostname PfafflPix

domain-name ciscopix.com

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

names

pager lines 24

mtu outside 1500

mtu inside 1500

ip address outside 216.184.176.194 255.255.255.224

ip address inside 192.168.1.1 255.255.255.0

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) 1 0.0.0.0 0.0.0.0 0 0

route outside 0.0.0.0 0.0.0.0 216.184.176.193 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 RADIUS protocol radius

aaa-server LOCAL protocol local

http server enable

http 192.168.1.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.1.2-192.168.1.254 inside

dhcpd lease 3600

dhcpd ping_timeout 750

terminal width 80

Cryptochecksum:78e357d50e88e5fc64c1d45f2373528b

I double and triple check the settings, but still

no luck.

I appreciate any help or suggestions.

Thank you.

-Paul Hong

  • Other Security Subjects
3 REPLIES
New Member

Re: Cannot connect to Internet..

global (outside) 1 interface

You have an ip address where it says "interface" which is different than the outside interface address?

route outside 0.0.0.0 0.0.0.0 216.184.176.193 1

.193 is your gateway?

Are other services working? (like ping)

You incidentally might consider changing your snmp community string to something other than "public."

You could also turn some logging on to see what is happening....

Gold

Re: Cannot connect to Internet..

Hi Paul,

Your config looks OK, What is the error message your seeing when trying to browse the internet? Do you have LAN router with the PIX in the middle and a internet router in front, i.e. LAN-ROUTER-PIX-ROUTER-INTERNET. Also, try command 'clear xlate' and try again.

Thanks - Jay

Silver

Re: Cannot connect to Internet..

Hi Paul,

Different things can be wrong, although your config looks okay. Some questions could help isolating your problem.

1) can you ping your router (.193) from the PIX itself?

2) can you ping cisco site (198.133.219.25) from the PIX

3) try opening http://198.133.219.25 with your browser

If all this works, there your config is okay.

Pinging from the inside will only work if you create an access-list on the outside interface for the response traffic! (have to remember that ICMP is not statefull inspected)

If all this works it could be the case that only name-resolving is not working, this is easy tyo determine by browsing to http://www.cisco.com (if this works not, but it works with the IP-address, you're having problems with name resolving

Hope this helps. Please keep us posted on how things are going.

Kind regards,

Leo

If all this works you most likely have a problem

218
Views
0
Helpful
3
Replies
This widget could not be displayed.