Question Locked

Cisco IOS problem

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,
im pretty a noob concerning Cisco IOS but perhaps someone here can help me with my problem.
We got an Cisco 851 ADSL Router which has the IP 192.168.168.1 in the internal network. There was supposed to be a server with the IP 192.168.168.104 also in the internal network. Yesterday i tried to forward a port to this server so that i would be able to connect to it via remote desktop. Somehow i got it all wrong and now the IP is reserved and i had to give the server a new ip what created new problems. Can somebody tell me how to figure out what network device is reserving the IP (192.168.168.104) and make it release it?

greets,
Adel

15 replies

by larryd4

The only thing that can reserve an IP address is a BootP/DHCP server.

If the ip address was given to another PC on your network, because of lease expiration, then that list should be in the active lease list in your DHCP server.

by aelray

the router is also working as DHCP server. and i have no clue which machine is now reserving the IP, especially since after shutting down every machine, except of the router and the server, the IP still seems to be in use. so for some reason the IP must be locked by the router. After seeing this i made a show run on the router and it says the only ip locked is 192.168.168.1 because it is the router's.

by cg it

if this is a Windows AD network, you should use Windows server DHCP services instead of a router DHCP.

note: Cisco has a really good technical KB on IOS. I would recommend going there and getting familiar with their KB. you'll be glad you did.

by cg it

try using SDM or SDM Express to configure your router.

Another would be to turn off the DHCP services.

by aelray

i don't know if this would solve the problem, because the IP seems to be reserved router internally (the router is also the DHCP server). i tried to forward the port with commands like this (tried it in various forms because it didn't seem to work):
ip nat inside source static tcp 192.168.168.104 3389 212.113.150.114 3389 extendable

by cg it

is simply the DHCP server won't give it out to any clients requesting an address.

If you assigned a server a static address, and you use DHCP, then you reserve that address in DHCP so that DHCP won't give it out. DHCP doesn't "lock" the address per se so that it's not part of the entire scope, rather the address gets dumped into the scope pool called reservations. Same as having a DHCP relay agent the relay agent has a pool of addresses from the scope reserved for clients on another subnet.

by aelray

i don't know, i am somewhat used of the idea, that a router can also work as DHCP, and there aren't only windows boxes in the network.

and the cisco KB is where i got the commands for configuring the forward, but all in all it just got me into a great mess.

by aelray

k, thanks for the definition, but for some reason i can't assign the address to the machine it had before. it always tells me it would be somewhere else in use, whereas there is nothing else running beside the router and the machine i'm talking about.

by cg it

DHCP believes that address is reserved and has been assigned to a machine therefore if you try to assign it again, DHCP will not accept it. you have to take that address out of the reservation pool to assign it to another machine then add it back in.

by cg it

I think DHCP is doing what it's supposed to do reserving that address from being used in the general pool for clients. Your server should have a static address.

If you have an ACL, always remember that the last line statement is deny any any but you won't see that last line. So if your configuration is wrong, what you want to have work won't because the last line is deny.

by aelray

i don't think i actively configured an ACL but if there is one automatically generated by the DHCP how do i access and alter it?
the IP of the server was static because i set it like this in the windows networking configuration.

by aelray

ok, problem solved, all that was needed, was a reboot ;)

This discussion is closed to new replies.