OMV "blocks" Win10 Network

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • OMV "blocks" Win10 Network

      Hello,
      I have a strange problem.
      Since a few month my 2 PCs with Win10 are showing the yellow triangle (of death) LAN Network icon.
      First I thought it is an Windows problem but as soon as I disconnect OMV (on BananaPi) and restart the network switch everything works fine.
      I have no idea where to start, to get rid of this error. All Windows 10 apps are not working, when the yellow triangle is shown, Firefox and chrome etc. are working.
      So I am connected with my PCs to the internet but the must be some trouble in the network config.
    • It is definitely a wrong network setting you are using on the OMV system but without telling us what your settings are, no one can help.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • morph8000 wrote:

      what infos do you need?
      network settings. I don't care how you present them.

      morph8000 wrote:

      Or is it better to update to Version 4.x?
      Normally I would say it is better to upgrade to OMV 4.x, I don't know how that upgrade will work on a BPi.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • no Firewall and no proxy is used. rsync was on before, now I disabled it. IPv6 was disabled before, now I set it to dhcp.
      Still testing if the yellow triangle now is gone. Normally it comes back as soon as I reboot Windows and the BananaPI is the first device in network.
      Booting up windows and AFTER that OMV normally removes the yellow triangle. But that could not be the solution.
      Images
      • pi1.JPG

        22.21 kB, 533×220, viewed 48 times
      • pi2.JPG

        31.72 kB, 1,466×172, viewed 58 times
      • pi3.JPG

        41.36 kB, 1,447×333, viewed 54 times
    • I don't see anything wrong there. Rsync is definitely not the problem. I assume your router's IP address is 192.168.0.1? What do you mean the BPi is the "first" device on the network? Do you have the dnsmasq plugin installed on the BPi?
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Yes, 192.168.0.1 is router IP
      no, I think I discribed it wrong.
      I meant PC needs to be the first booted or started device in the network.
      If BananaPI is started first and after that the PC, I get the triangle.
      Only PC booted or PC after BananaPI I have no problem.
      But OMV is running always 24/7 and PC is restarted every morning. I dont want to disconnect BananaPI every day just to boot PC first in the network
    • morph8000 wrote:

      2 PCs with different Networkcards and cables both have the same problem. So I dont think, switch, cable or something is the problem.
      Ok, but it's not an OMV problem either, this is something related to your network, I have known switches appear to work, only to find out with some testing that the switch was failing on certain ports and therefore creating network problems. Running the network troubleshooter will usually give up some information.
      Raid is not a backup! Would you go skydiving without a parachute?
    • morph8000 wrote:

      DHCP range is 140 devices, so ...50 shouldn't be a problem. 2 PCs with different Networkcards and cables both have the same problem. So I dont think, switch, cable or something is the problem.
      I agree that it shouldn't be a problem. But that doesn't help if it is a problem. If the DHCP server is trying to give out IP numbers that are used already you get exactly the problems that you reported.
      OMV 4, 7 x ODROID HC2, 1 x ODROID HC1, 5 x 12TB, 1 x 8TB, 1 x 2TB SSHD, 1 x 500GB SSD, GbE, WiFi mesh
    • changed OMV IP from x.50 to x.15, and PC IP from DHCP to x.17, still not good and same problem.
      Internet works, see speedtest from fast.com, but Win10 gives error.
      Picture 1: 15 seconds waittime between deactivating and activating network adapter.
      Resetting network, the suggested solution from win10, doesnt change anything.
      Changing the PC IP adress (to x.18) removes the yellow triangle.
      Deactivating and activating network adapter = triangle, changing IP back to old number x.17 still triangle, changing IP to x.16 = triangle is gone.
      Images
      • Pi5.jpg

        149.02 kB, 603×907, viewed 43 times
      • Pi4.jpg

        225.16 kB, 1,667×1,009, viewed 37 times

      The post was edited 3 times, last by morph8000 ().

    • If the Windows boxes aren't looking at the OMV system for dns and none of the systems have duplicate IP addresses, I have no idea how this could happen without bad hardware and/or something weird with the router.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • morph8000 wrote:

      Resetting network, the suggested solution from win10
      I have been working with Windows machines for longer than I can remember and that it not necessary!

      All this is related to your network, as @Adoby has said it could have something to do with DHCP, so what is the DHCP range on your router it should have something like 192.168.0.xxx to 192.168.0.xxx (xxx being number/s).
      Raid is not a backup! Would you go skydiving without a parachute?
    • I suggest that you go over ALL your devices and figure out exactly what IP they use, where they got that from and how you can make sure it doesn't conflict with other devices. It might even be a good idea to write it all down on a piece of paper or in a file somewhere. And/or put the info on stickers on each device.

      Using fixed IP only on network equipment, printers, media players and servers is a good idea. Let the rest use DHCP.

      It seems you or somebody else have assigned the same IP to more than one device. It may be from having more than one DHCP server or from you not keeping track of the IPs in use and the range(s) of the IPs the DHCP server(s) give out.

      One very simple method is to use some network scanning software to figure out what IPs are in use. Also login to routers, access points, repeaters and other similar devices to see if the have a DHCP server active. It might be helpful to disable all DHCP servers except one.

      Your description that some IPs work but other doesn't seem to confirm (even prove?) that you use the same IP on multiple devices.
      OMV 4, 7 x ODROID HC2, 1 x ODROID HC1, 5 x 12TB, 1 x 8TB, 1 x 2TB SSHD, 1 x 500GB SSD, GbE, WiFi mesh

      The post was edited 1 time, last by Adoby ().