cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
719
Views
0
Helpful
5
Replies

IP NAT and HTTPS on 2514 Cisco router

dthomas
Level 1
Level 1

HTTPS Connections timeout thru a Cisco 2514 12.0 IOS

running IP NAT overload, connected to a Comast cable modem. Timeout occurs after login to the secure site. I have tried different computers and browsers behind the 2514, does not solve the problem. Any help will be greatly appreciated.

Thanks

5 Replies 5

ajd
Level 1
Level 1

Can you post the config (just X.X the ip's)?

It will help the multitude of 'theorys' that you will get in response and give you maybe more tips on your configuration.

-ne1secure

See config below.

Thanks

version 12.2

no service single-slot-reload-enable

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname CC-B

!

logging rate-limit console 10 except errors

enable password

!

ip subnet-zero

no ip finger

!

ip cef

no ip dhcp-client network-discovery

!

!

!

!

interface Ethernet0

ip address dhcp

ip nat outside

!

interface Ethernet1

ip address x.x.x.x 255.255.255.0

ip nat inside

!

interface Serial0

no ip address

shutdown

!

interface Serial1

no ip address

shutdown

!

ip kerberos source-interface any

ip nat inside source list 1 interface Ethernet0 overload

ip classless

!

access-list 1 permit x.x.x.x 0.0.0.255

!

!

line con 0

transport input none

line aux 0

line vty 0 4

password 7

login

!

end

It would be better if you had a pool of addresses, even it was one. One problem is that you are trying to create a 'secure' connection to an interface that is in use constantly.

Also, how long before it times out?

Its probably the cable modem not keeping the connection as opposed to the router.

Ill look into this though as I am curious.

I will get back to you tomorrow.

-ne1secure

The secure web home page is download/displayed on the client machine. The timeout occurs after the username/password are sent to the secure server. A syn packet is sent to the server from the client and the https server never ack. Connection times out. Also what is this command use for: IP NAT SKINNY TCP PORT?

Turns out the cable modem had the problem. According to Comcast Tech Support my brand of modem(Toshiba's PCX1100U, also known as the DAZ8813) has a bug which causes it to lockup during https connections.I replaced it with RCA moden which works great. Model number escapes me at the moment.

Thank You very much for your help Ne1secure!

Dave