Analisis Penyebab dan Solusi DHCP error sering sekali terjadi ketika mati lampu, atau router mati tanpa di shutdown. Atau bisa juga bentrok antara dhcp mikrotik dengan dhcp perangkat penyebar wifi. Solusi mengatasinya sebenarnya cukup mudah. Pertama yang perlu kawan-kawan lakukan adalah cukup melakukan reboot pada routerboard. Saya sendiri pernah mengalami dan ketika saya reboot, dhcp tidak error dan kebali normal. Solusi lainnya ketika cara pertama tidak berhasil adalah, lakukan disable enable pada service dhcp di mikrotik. Kawan-kawan bisa temukan di menu IP – DHCP Server.

1. Dhcp Offering Lease For Without Success

Just got a new SRW224G4 and I am trying to make it work with my Mikrotik RB450G. After setup the vlan, when I plug my notebook to the switch, in the router I see that my notebook is trying to get the IP, but after 30secs it fails, on the log of the router I get the messages 'Offering lease withou succes'. After some messagens in some forums of mikrotik, I see that the router is fine, the problem is on the switch. Where can I see the full log of the switch to see what is going on? (this negociation, drop packages, etc.) My setup is very simple, from eth3 on the router I connect it ot the g3 port, on the switch, I made this port as TRUNK, created the vLans and tagged them on the correct ports and on the port of the trunk.

As I see the notebook trying to get the IP, I guess the vLans are correct once I made it only accept tagged traffic. I see that the switch is very slow, even its onw IP it takes a while to get it.

Am I missing some config on it to fix this? The docummentation is very poor, and when o google about this switch, I don´t get too much material. I think I´ve made a bad decision on buying it. Sorry Cisco, but this Lynksys switch is @¨#%$#%¨!

When wireless clients increase I get a lot of: wifi offering lease for without success (on mikrotik). I have already tried in DHCP server 'always broadcast' and 'authoritative=Yes'. DHCP Offering Lease Without Success sering sekali terjadi pada jaringan hotspot mikrotik. Akibatnya perangkat pelanggan yang terkoneksi dengan akses point tidak akan mendapat IP alias selalu mental sampai pada tahap offering. DHCP servers hear the workstation and respond by offering IP addresses; this message is a 'DHCP Offer.' The workstation looks through its offers and selects one (I'm not clear about how it selects. I've seen workstations turn down more-attractive leases in favor of less-attractive leases).

Dhcp Offering Lease For Without Success

I made a update of the firmware, but the latest update is from years ago, v. 1.2.3, did I get the latest one or there is another one that fixes this slowness cheers. Tom, Thanks for the help. Yes the Router understands vLans, it's a Mikrotik RB450G. After a lot of reset configurations, I've made it to work, on the switch I was setting the ports wrong, I don't know why, but only works when you specify the vLan id and 'Accept All', I was putting 'Only Tagged'.

In my mind, should be only tagged, but the accept all worked fine, each vLans is receiving its own range of IP's correctly, or this 'only tagged' is about another IEE rfc, or I dont know what is going on, because without, it only gets the correct vLan Id, so I gess the vLans are getting only tagged packages. After few other tests, I came up with another 2 problems, Mac OS X don't get ip from dhcp server, PC goes fast as 1sec and gets the IP, mac doesnt. Looks like this switch has something that Mac doesnt understant, taking 30sec to try to get an ip and fails after that. I read about, its something with spanning tree, but in my case, I've turned off spanning tree, even doing that, macs dont get an IP. Do you know something about it?

Some work around? Other problem is the inter vLan comunication, in the router the routes are fine, on each vlan I can ping the gateway of each other vLans, but I am not able to ping the hosts in the subnet, even with the route set correctly. Do you know if there is something on the switch that causes this problem? Do I have to setup something in other of the inter vLans work? Is it not working because the package is tagged with one vLan ID and the destination is another, so the switch drops those packages?