• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Nasty Problem - Fixed, Don't get caught out

Scheduled Pinned Locked Moved Solved
Windows Problems
3
11
3.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    Julianh
    last edited by Apr 4, 2016, 4:20 PM

    I had a real pig of a problem today, and wanted to let you all know about it, so you don’t spend as many hours as I do finding it.

    The symptoms of a duplicate IP are, one box works, reboot the duplicate IP and the other box works, then the first stops.

    I imaged one server then sent the image down to 5 other machines. none of the other machines were accessible across the network, checked all the obvious IPs etc, no joy.

    It turned out to be the MAC address. The image had taken the mac address up, and all the imaged servers had the mac address from the source image.

    Easy enough to fix by defining a new mac in the adapter’s properties, but a pig to spot.

    I hope this helps someone else out there.

    Julian

    1 Reply Last reply Reply Quote 0
    • J
      Junkhacker Developer
      last edited by Apr 4, 2016, 4:30 PM

      was it a virtual network device? like the virtualbox host-only network adapter?

      signature:
      Junkhacker
      We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

      J 1 Reply Last reply Apr 10, 2016, 4:11 PM Reply Quote 0
      • J
        Julianh
        last edited by Apr 4, 2016, 5:50 PM

        Hi,

        It is all physical, which is why it’s supposed to be impossible.

        W 1 Reply Last reply Apr 4, 2016, 6:21 PM Reply Quote 0
        • J
          Junkhacker Developer
          last edited by Apr 4, 2016, 5:52 PM

          @Julianh said in [Nasty Problem - Fixed:
          …

          Easy enough to fix by defining a new mac in the adapter’s properties, but a pig to spot.

          what kind of network adapter was it then? can you give us the make/model?

          signature:
          Junkhacker
          We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

          1 Reply Last reply Reply Quote 0
          • W
            Wayne Workman @Julianh
            last edited by Wayne Workman Apr 4, 2016, 12:22 PM Apr 4, 2016, 6:21 PM

            @Julianh said in [Nasty Problem - Fixed:

            Hi,

            It is all physical, which is why it’s supposed to be impossible.

            Well now you have all of our interest. Please do spill the beans about all involved hardware AND the fog version you’re using.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 0
            • J
              Julianh
              last edited by Apr 4, 2016, 8:12 PM

              The machines were built for me, but they use the realtek Lan card on the ASUS A88XM-Plus mother boards, Fog v 1.20 on unbuntu 14.04, 6 core AMDs with 32 GB ram and SSDs.

              I was imaging up Server 2012, which normally works fine, one image per Physical server normally. But it’s eating my storage, so I thought I’d try 1 image to multiple servers, looks like I’m buying some more disks.

              W 1 Reply Last reply Apr 4, 2016, 8:23 PM Reply Quote 0
              • W
                Wayne Workman @Julianh
                last edited by Apr 4, 2016, 8:23 PM

                @Julianh Would you be willing to build a test server with FOG Trunk on it and see if the problem exists in our developmental version of FOG? It’d be greatly appreciated and you’d be doing the fogproject a solid.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

                1 Reply Last reply Reply Quote 0
                • J
                  Julianh
                  last edited by Apr 4, 2016, 9:26 PM

                  Hi Wayne,

                  I have a VMware troubleshooting course to finish off updating, but afterwards I should have some time and more importantly kit free in early May. I could have a go then if that’s ok.

                  Julian

                  W 1 Reply Last reply Apr 4, 2016, 9:28 PM Reply Quote 1
                  • W
                    Wayne Workman @Julianh
                    last edited by Apr 4, 2016, 9:28 PM

                    @Julianh Sounds good, ask for help if you need - don’t forget us!

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                    Daily Clean Installation Results:
                    https://fogtesting.fogproject.us/
                    FOG Reporting:
                    https://fog-external-reporting-results.fogproject.us/

                    1 Reply Last reply Reply Quote 0
                    • J
                      Julianh
                      last edited by Apr 10, 2016, 3:38 PM

                      I’ve been looking into this, and have spoken to one of our MCT instructors.
                      The machines I was imaging were Server 2012 R2, with Hyper-v. The Macs were duplicated on all the images. The instructor pointed out that Hyper-v moves the original Mac into software and uses the physical card as a glorified pass through device, so in effect the physical Mac becomes software, which explains how the situation arose.

                      I hope this helps anyone else imaging 2012 R2 Servers.

                      Could you mark this as solved and edit the title to “Nasty Problem - Fixed, Don’t get caught out when imaging Hyper-V Hosts”

                      1 Reply Last reply Reply Quote 0
                      • J
                        Julianh @Junkhacker
                        last edited by Apr 10, 2016, 4:11 PM

                        @Junkhacker
                        Well this was the interesting bit, it was all physical, the MACs imaged up were those of the physical adapters, but Hyper-v was “moving” the physical MACs to it’s internal network cards, and then of course imaging the software MACs up. Interesting, a pain but quite interesting.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        1 / 1
                        • First post
                          4/11
                          Last post

                        136

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project