November-24th-2020, 06:42 PM
Hi Armin,
I apologize, I have been on holiday the last few days.
I used the wrong name, but yes, I did use Windows File Explorer's Network search.
I first tried setting up and detecting the good Net pi unit using its DHCP server and I was able to find it in the Network window of File Explorer with no problems. It had used the DHCP range I had changed the configuration to and provided addresses on both machines I used adapters.
With the exact same network adapter settings, I then disabled both machines Ethernet adapters, then disconnected the working unit from the internal network (which consists of just a un-managed switch, the PC's and the Net pi units connected at any one time) and I then I re-enabled both network adapters on the PC's. After comparing the adapter status's compared to the working unit, it does not appear that the Net pi unit is assigning correct IP settings to the PC adapters as shown in the two attached images.
I also tried this exact same connection method as above using an Industrial workstation running Ubuntu 20 OS and it also produced the same results. I was able to get an assigned IP address and locate the unit in the "Other Locations" tab of the Files window, and I was able to access the good unit. But on the bad unit the network adapter monitor was showing that it was not obtaining an IP address and after 3 tries, it would disable itself and of course I was not able to locate the unit in the Files window. I have also attached an image of that units settings and results.
Is there anything else you can think of to access this Net pi unit?
Thank you
Mark
Hello Armin,
Sorry, I forgot to post the startup screens for the bad unit I am calling B0E4D. I tried to capture the scrolling several times, but was only able to get 3 screen captures that were legible. Please see attached.
Thank you,
Mark
I apologize, I have been on holiday the last few days.
I used the wrong name, but yes, I did use Windows File Explorer's Network search.
I first tried setting up and detecting the good Net pi unit using its DHCP server and I was able to find it in the Network window of File Explorer with no problems. It had used the DHCP range I had changed the configuration to and provided addresses on both machines I used adapters.
With the exact same network adapter settings, I then disabled both machines Ethernet adapters, then disconnected the working unit from the internal network (which consists of just a un-managed switch, the PC's and the Net pi units connected at any one time) and I then I re-enabled both network adapters on the PC's. After comparing the adapter status's compared to the working unit, it does not appear that the Net pi unit is assigning correct IP settings to the PC adapters as shown in the two attached images.
I also tried this exact same connection method as above using an Industrial workstation running Ubuntu 20 OS and it also produced the same results. I was able to get an assigned IP address and locate the unit in the "Other Locations" tab of the Files window, and I was able to access the good unit. But on the bad unit the network adapter monitor was showing that it was not obtaining an IP address and after 3 tries, it would disable itself and of course I was not able to locate the unit in the Files window. I have also attached an image of that units settings and results.
Is there anything else you can think of to access this Net pi unit?
Thank you
Mark
Hello Armin,
Sorry, I forgot to post the startup screens for the bad unit I am calling B0E4D. I tried to capture the scrolling several times, but was only able to get 3 screen captures that were legible. Please see attached.
Thank you,
Mark
