cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
761
Views
0
Helpful
4
Replies

Cisco 2621 Router config

sonic
Level 1
Level 1

Is it possible to bind more than 1 ip address to the built in ethernet interfaces on a 2621 router?

2 Accepted Solutions

Accepted Solutions

donewald
Level 6
Level 6

Yes, you can use secondary addresses for this.

ip address

then for the secondary do this in the interface configuration mode

ip address secondary

Ensure you put secondary after the ip or it will overwrite the primary address.

Hope this helps,

Don

View solution in original post

Add this statement to your access-list 1

Router(config)#access-list 1 permit 192.168.1.0 0.0.0.255

Since you are not able to resolve DNS names for the workstations in the 192.168.1.0 network, you will need to configure DNS server setting for the workstations. (you can use the same DNS server as you use for the 10.0.0.0 network)

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

View solution in original post

4 Replies 4

donewald
Level 6
Level 6

Yes, you can use secondary addresses for this.

ip address

then for the secondary do this in the interface configuration mode

ip address secondary

Ensure you put secondary after the ip or it will overwrite the primary address.

Hope this helps,

Don

Thank you that works!

sonic
Level 1
Level 1

I got the second IP address (192.168.1.2) bound to the interface of my router, but nothing on that subnet can get out to the outside world. I tried to ping out from a pc with 192.168.1.3, but all I get is unknown host when using names (cisco.com) and request timed out when using ip addresses. I can ping out to places just fine on machines that are on the 10.0.0.0 net work . What else do I need to do? My router config is as follows, but I did go thru and sanatize it change the names to protect the innocent:

Current configuration:

!

version 12.0

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname abcdefghijklmnopqrstuvwxyz

!

!

enable password 7 abcdefghijklmnopqrstuvwxyz

!

memory-size iomem 15

ip subnet-zero

ip name-server 10.0.0.2 **(small busines server 2000 PC main network)**

ip name-server my.isp.provided.dns1

ip name-server my.isp.provided.dns2

!

!

!

!

!

interface FastEthernet0/0

description connected to Internet

ip address my.static.ip.address 255.255.255.x

no ip directed-broadcast

ip nat outside

!

interface FastEthernet0/1

description Connected to SBS 2000 Proliant 7000 Nic #2

ip address 192.168.1.2 255.255.255.0 secondary **(test network)**

ip address 10.0.0.1 255.255.255.0 **(small busines server 2000 PC main network)**

no ip directed-broadcast

ip nat inside

!

router rip

version 2

passive-interface FastEthernet0/0

network 10.0.0.0

no auto-summary

!

ip nat inside source list 1 interface FastEthernet0/0 overload

ip nat inside source static tcp 10.0.0.2 80 my.static.ip.address 80 extendable

ip nat inside source static tcp 10.0.0.2 1080 my.static.ip.address 1080 extendable

ip nat inside source static tcp 10.0.0.2 3389 my.static.ip.address 3389 extendable

ip nat inside source static tcp 10.0.0.2 20 my.static.ip.address 20 extendable

ip nat inside source static tcp 10.0.0.2 21 my.static.ip.address 21 extendable

ip nat inside source static tcp 10.0.0.2 23 my.static.ip.address 23 extendable

ip nat inside source static tcp 10.0.0.2 25 my.static.ip.address 25 extendable

ip nat inside source static tcp 10.0.0.2 110 my.static.ip.address 110 extendable

ip classless

ip route 0.0.0.0 0.0.0.0 FastEthernet0/0

no ip http server

!

access-list 1 permit 10.0.0.0 0.255.255.255

banner motd ^CTread lighty on unfamiliar ground^C

!

line con 0

exec-timeout 0 0

password 7 abcdefghijklmnopqrstuvwxyz

!

login

transport input none

line aux 0

line vty 0 4

password 7 abcdefghijklmnopqrstuvwxyz

!

login

!

end

Any suggestions would be accepted.

Add this statement to your access-list 1

Router(config)#access-list 1 permit 192.168.1.0 0.0.0.255

Since you are not able to resolve DNS names for the workstations in the 192.168.1.0 network, you will need to configure DNS server setting for the workstations. (you can use the same DNS server as you use for the 10.0.0.0 network)

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus