SOLVED! Winbox on Windows-7 using MAC Address doesn't work

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.

Can anyone confirm this?

Works perfectly fine on my Win7 box.

Thanks! It must have something to do with my windows configuration or lan port, although everything is standard.

My windows 7 RC1 does not like Winbox connecting to MAC addresses but my colleagues Win 7 (proper) behaves just fine.

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 am running Windows 7 x64 and MAC access works fine for me to.

Winbox on Win7 x64 fine here also.

you could try to right-click it and choose ‘run as administrator’, although on my Win7 it works fine

This works partially on my Win7 RC1

It shows the MAC address but not the IP.

I’m sure when I eventually conjure up the strength to reformat it will work on normal Windows 7.

I just tested it on my Win7 64bit, works fine.

I tested and it is work on my Win7 64bit, works fine. I think you have firewall on you system :wink:

“Firewall completely disabled”

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.

This issue has been resolved, thanks to this older thread that had a similar problem:
http://forum.mikrotik.com/t/mac-winbox-no-longer-works-on-new-laptops-toshiba-vista/19366/1

The issue is the virtual Sun Java’s VirtualBox Network Interface (similiar to VMWare).

Disable that network interface, and it works perfectly!

Thanks very much, it certainly does indeed.

yup, I worked for me after I disabled the virtual Sun Java’s VirtualBox Network Interface!
I have win7 x64 with latest updates.

Normis, it may be a good idea to put this in wiki or some kind of stickie titled: “Winbox MAC connect issue and solutions…”

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..:slight_smile:

:smiley: Yes, my Winbox started working after disabling Virtual machine Ethernet interface, im running Win7 64 bit. Thanks lads

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…