On Windows XP and Windows Vista, the MAC Address login to winbox works fine.
On Windows 7, when I push the … button in winbox, the box that opens is empty, no addresses listed. If I type the address in manually, it does not connect.
If I use the IP address, winbox works perfectly. However, on new boards unconfigured, I need the MAC login to work.
Windows firewall is completely disabled, and no other programs installed are blocking it.
Interesting. I have Windows 7 that was upgraded from Windows 7 RC1. Upgrading from RC1 without a complete reinstall is discouraged by Microsoft. Perhaps this is caused by that.
I believe this may be the same reason that the other person in this thread that did not work. They were using Win7RC, and I am using Win7 that was upgraded from Win7RC.
hello,
virtualbox interfaces should be disabled when using mac connect from winbox, i have same problem on windows xp.. also vmware interfaces should be disables and any other virtual machines..
I’ve always found that I have to disable all interfaces, except for the interface connected to the mikrotik, for layer 2 winbox to discover the routerboard.
If interface is setup to get an IP by dhcp, Windows won’t pass any traffic until it gets the lease from a DHCP server… which is fast if there’s a server available, but takes more than a minute if no DHCP server replies to the ip request. Set a fixed ip and problem gone.
Personally, I haven’t had any issues with virtual interfaces of any kind (and I have used lots of them!) under WinXP/Win7. I haven’t used Win8 enough to comment about it.
The same problem, windows 8.1. First I noticed that disabling of some interfaces can help, but after reboot I has the problem again (even previously disabled interface was still disabled). Then I found the solution about vmware interfaces, disabled it (in fact, only one onterface is enabled, others disabled), and it was solution within a couple of days. Now the problem returns, all unused interfaces is disabled, tried to disable firewall, antivirus, nothing helps. I can’t remember, what was changed in the system. I think it could be now the “Checkpoint Smartconsole”, that I need to control the standalone server…
When I researched this problem a week before, I found, that in good condition (when mac-winbox works) a few broadcast packets (то 255.255.255.255) is sent in time of pressing “…”. In bad condition (mac-winbox does not work) there is no outgoing packets to 255.255.255.255. In any condition, on incoming broadcast (discovery) packet from router, its address was appear in winbox neighbor list.
Now I can see the incoming discovery packets (I see it by windump), but nothing appears in winbox.. Outgoing requests (broadcast packets by pressing “…”) is absent at all.
It’s hard to work without mac-winbox…
Still researching…