MikroTik

Hello,

I can't get netinstall to work on Windows 10. Net booting is not working. On that same computer while Win7 was installed, everything worked OK. It looks like somekind of Win10 security, but I can't figure it out. Anyone with same problem?

BR...

Have you tried like many of us, and another win versions with netinstall.
1. First disable windows firewall.
2. Run netinstall program as administrator.

Yes, firewall disabled, and netinstall started as admin. That was the first thing i did...

Why not try to set an statiic ip on the pc.
Like mikrotik default range:
192.168.88.10

And testing the correct port of your router.
For Netinstall, the PC needs to be connected to port 1 !

And for a another solution for bad arp ip connections, lets make a static arp to ip on your pc.

1. Look at the router to see what mac address (in my ex 00-0C-42-12-34-56) it has for the correct port.
2. Start cmd as admin. Right click Start button Command Prompt (Admin)
3. Set static arp into arp table----Type :arp -s 192.168.88.1 00-0C-42-12-34-56
4. Ping your device until stop with <CTRL><C>----Type: ping -t 192.168.88.1

I'll have to give up on Win10. To many problems. Winbox behaving strange, netinstall also. Few other specific software don't work. Bye, bye Win10...

I'll have to give up on Win10. To many problems. Winbox behaving strange,

Works perfectly for me.

False alarm. I have installed new Win10, and now everything working great. The question is what peace of software killed netinstall last time. I will do step by step app install...

False alarm. I have installed new Win10, and now everything working great. The question is what peace of software killed netinstall last time. I will do step by step app install...

This is going to sound stupid... but have you tried changing its name?

No joke!

After installing Windows 10, I had the same problem -- devices wouldn't show up in the netinstall window. I had a static IP set. I had it set to always run as administrator. I had all other networking turned off. I updated the drivers for my USB-to-ethernet adapter. I double-checked the presence of the firewall hole.I scanned the boot IP range from the attached MikroTik, and the boot server showed up. But it just would not work.

As a related problem, I was getting really tired of seeing the warning box saying, "Do you want to allow this app from an unknown publisher to modify your system?" before every failed test, so I did a web search to see if there were any way to turn that off. I came across this posting, where a fellow claimed that any app with the strings patch, install, update, or setup in the name will trigger this warning, while others won't.

It smacked of voodoo, but I renamed the package to netinsttall.exe. And not only did it turn off that message, but damned if netinstall didn't immediately start working (after one additional, "do you want to let this app through the firewall" message box).

Hey, I can't explain it, but it's working now, and I'm not going to screw with it.

I got this working by disabling all network cards except wired.

I wish that netinstall and winbox discovery let you select a connection profile to use. The program automatically selects one, and if it picks the wrong one, then you're kind of screwed.

Problems could be the same or related to this: http://forum.mikrotik.com/viewtopic.php ... 60#p490402

False alarm. I have installed new Win10, and now everything working great. The question is what peace of software killed netinstall last time. I will do step by step app install...

This is going to sound stupid... but have you tried changing its name?

No joke!

After installing Windows 10, I had the same problem -- devices wouldn't show up in the netinstall window. I had a static IP set. I had it set to always run as administrator. I had all other networking turned off. I updated the drivers for my USB-to-ethernet adapter. I double-checked the presence of the firewall hole.I scanned the boot IP range from the attached MikroTik, and the boot server showed up. But it just would not work.

As a related problem, I was getting really tired of seeing the warning box saying, "Do you want to allow this app from an unknown publisher to modify your system?" before every failed test, so I did a web search to see if there were any way to turn that off. I came across this posting, where a fellow claimed that any app with the strings patch, install, update, or setup in the name will trigger this warning, while others won't.

It smacked of voodoo, but I renamed the package to netinsttall.exe. And not only did it turn off that message, but damned if netinstall didn't immediately start working (after one additional, "do you want to let this app through the firewall" message box).

Hey, I can't explain it, but it's working now, and I'm not going to screw with it.

Worked for me too - I suspect it may be to do with UAE control - it asked if I was going to allow access from Public Networks first time I opened the newly renamed file - perhaps I fogot to tick this on the original Netinstall ?

In my case netinstall (both 5.26 and 6.37.1) when run under windows 10 pro (run as Administrator) will just send an error 10013 - bind() failed: An attempt was made to access a socket in a way forbidden by its access permissions.
This is followed by a msgbox no code!!!: The operation completed successfully.(0)
In any case, acknowledging will just close the window.

Any hints of what am I doing wrong?

Windows colic is so tedious.

Is it possible you have another BOOTP server already running?

Try creating a new administrator user on your machine and see if netinstall runs any better under that user.

Just a heads up, I found this because I was having problems.

Turns out Virtualbox messes it up, if you have it installed.

workaround
For me, disabling APIPA by creating a DWORD value called "IPAutoconfigurationEnabled" with a value of "0x00000000 (0)" below "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" in the windows registry (and rebooting) solved the problem.

diagnostics/troubleshooting process
My Wireshark trace suggests that the netinstall utility told the routerboard to connect back to the APIPA adress of the Windows PC, even though a static IP adress and default gateway had been specified. Looking at the interface details on windows showed two IP addresses, the static one and an APIPA adress (169.254.x.x). After completely disabling APIPA, only the static IP address was shown for the network interface and netinstall told the routerboard to connect to it.

netinstall feature request
When there are multiple IP addresses configured on the network interface used by netinstall, prefer the non-APIPA address or ask the user.

I found that I had to run it under Windows 7 compatibility mode.

Hi, I had the same issue wirh win10. Netinstall didn’t find the device, despite while making a traffic capture, the hex lite was requesting BOOTP.
Disabling all interfaces but wired, and renaming netinstall.exe to nettinstall.exe, running it as administrator wirh windows defender fw disabled for all networks, I finally could see the RB750 and install the OS again.
Thank you all for your tips!

I ran into this same issue. Ofcourse I have virtual box installed. Had the virtual box driver disabled from the ethernet card and it still didn't work which used to on win 7.

So I took a moment. Had the idea of running Win7 within virtual box just for this purpose. and it worked.


Turned the Vbox bridge driver back on in win10, and made sure the nic was bridged for the VM.

Made sure to install the vbox drivers in win7 so I could drag and drop the files. this way I can leave everything alone in the vm and it will be ready for me next time.

I found that I had to run it under Windows 7 compatibility mode.

Me too, same issue, had it work selecting "run as administrator" and " run compatibility mode win7"

Hello,

I can't get netinstall to work on Windows 10. Net booting is not working. On that same computer while Win7 was installed, everything worked OK. It looks like somekind of Win10 security, but I can't figure it out. Anyone with same problem?

BR...

It looks like netinstall is conflicting with virtualbox
on clean Windows 10 2004 everything works fine