We've experienced problem with windows vista not receiving the DHCP and sometimes I think it is related to the DHCP server that will be filled BUSY task of assigning IP addresses to ZERO (00:00:00:00:00:00) Mac address which will never go away until it expires and may stays there if there is a client keep requesting.

we had to over come this by an script that had to be running as schedule every 1 minute to check dhcp leases and remove them. I hope in next version of Mikrotik it will be solved although we haven't ugpraded 3.0RCx yet.

here is the wiki link

good luck

we use Vista here (I do too) and there are no DHCP problems with v3 RouterOS. If this issue is reproducable, tell me exact steps and we will test.

we use Vista here (I do too) and there are no DHCP problems with v3 RouterOS. If this issue is reproducable, tell me exact steps and we will test.

this ia 2.9 related issue. and I'm not sure about 3.0
v3 is just released and I'm sure a lot of people are on 2.9, including myself.

we used 2.9 for more than a year no problems with vista too. as usual, if anyone experiences any issues - contact support with supout.rif files

I have seen this probelm v 2.9.50 I cannot tell you though if it is 100% Vista related but certainly do see this on our DHCP server as well. As above we too had to set a script

Hello,

We have a Vista problem on one of our parks. (so the mac adress becomes 00 (and so on) and vista machines don't get an IP adress.) We tried this: http://support.microsoft.com/?scid=kb%3 ... 3&x=5&y=13, and vista DID get an IP adress, but still it had limited connections. I was just wondering, Is this problem fixed in V3?
The problem is really weird though, because we have several parks using V2.9.43. But only one park has problems with vista.
The script isn't really an option because we still have the problem.
by the way, I couldn't find if routerOS v3 still has the problem or not, what I did see is that there were some updates for DHCP.

I have noticed that Vista has a strange requirement to disable/enable the interface in case a lease is lost and needs to be refreshed

It's like vista is trying to get a new IP every xxx time. But is the problem fixed in V3, or is there a more simple solution for the problem? We really like to fix the problem, we have been working on it a couple of weeks now, and guests are complaining..

btw, the script only removes the Mac adresses that are 00 and so on? or does it somthing else too? The script doesn't run every minute, do you have to enter that somewhere?

It's supposed to be some sort of security feature of Vista

... go figure

I use MacOS

security feature in vista? I can find some difference between Vista and XP, but nothing that has something to do with DHCP. But my idea was that if V3 doesn't have the problem, we upgrade the RouterOS and problem solved. But we have to make sure it WILL solve the problem. Because it takes some time to upgrade the os..

I don't think this will work in v3 either, because it's not really a router issue. look here:
http://support.microsoft.com/kb/928233

jij kan nederlands??

I already tried that, didn't work. Vista DID get an IP adress but still only limited connection... if we can fix that, that problem is solved

btw, how can I get the name of the network adapter {guide}???

1. 2.9.5 fixed our Vista problem [2.9.46 had problems, along with other previous version with Vista].
2. 3.x also fixed our Vista problem.
3. Switch wireless card from Public to Private also fixes it most of the time.
4. Turn firewall off on Vista has also fixed it.


2.9.5 was the most obvious fix though.

Actually, I would be a little careful going to 3.x. There are some issues with it.

Go to 2.9.50, that has worked the best for me.

Also, under the wireless card settings in Vista, you can switch from Public to Private. That fixes it sometimes.

It's not clear to me from Normis' post what the behavior of ROS 3.x is with respect to the broadcast bit in DHCP discovery packets.

The Microsoft support post mentions that some routers don't alter their response based on the broadcast bit. What does ROS 3.x do when it sees a discovery packet with the broadcast bit set to request a broadcast response?

Any news on this issue? It appears to me that the problem occurs because Microsoft changed the broadcast bit settings from previous versions of Windoze. Some have come up with resolutions that include changing the registry key for the broadcast bit.

What does ROS 3.x do when it sees a discovery packet with the broadcast bit set to request a broadcast response?

I have a few hotspots installed where this is still an issue.

Thank you