0x80072EE2 - An error occurred while resolving dependencies for the selected task sequence - Intel(R) Ethernet Connection (16) I219-LM - sccm

Dear brothers and sisters from the IT World,
I trust this finds you very well.
We have received a new DELL Model: DELL Latitude 5530.
The model has the following Network Interface: Intel Ethernet I219 Network
The required drivers have been properly imported and added to the task sequence (driver package).
We have two vlan/subnet where we can stage the laptops:
Vlan A - Same Subnet as the SCCM Server
Vlan B - A diferent Subnet (Sccm Server), we use ip helpers to root the trafic.
Staging Vlan A
Test1 - Port RJ45 - Network Interface: Intel Ethernet I219 NetworK
I tried with a diferent dell model and everything worked properly, really fast and stable.
I tried with the model DELL Latitude 5530 (2 diferent laptops) and the Task Sequence return an error right at the begining, the DISK is not even formated and we get the following:
An error occurred while resolving dependencies for the selected task sequence (0x80072EE2). For more information, contact your system administrator or helpdesk operator.
As we can see on the SMSTS.LOG located in (X:\windows\temp), an IP is properly assigned:
enter image description here
And as you can see in this screenshot, i have an ip address:
enter image description here
Please find more details about the error below:
enter image description here
Test2 - USB-C - Docking Station
I tried with the model DELL Latitude 5530 (2 diferent laptops). The WINPE Img takes a lot of time to download but after that, the TS works properly (even if it is slow) and i dont get the error.
Staging Vlan B
Test1 - Port RJ45 - Network Interface: Intel Ethernet I219 NetworK
I tried with a diferent dell model and everything worked properly, however, the network is slower but it is stable.
I tried with the model DELL Latitude 5530 (2 diferent laptops) and everything worked properly, the network is slow but it is stable.
Test2 - I didnt do it because the objectif if to reimage on the SCCM Subjet.
This is driving me nuts.... Can you please guys have the kindness of helping me?
As always, your help and support is very much appreciated.
Thank you all and best regards,
Peace

Related

ping machine in VM gives the wrong adapter ip

I am studying Active directory. I created a virtual lab to experiment for the couse I am studying.
I am using Oracle VM 6.1 and I created 2 virtual machine. One where I installed Windows server 2019 and one wher eI installed Windows7 (my laptop cannot run anything bigger than that).
In each VM I created 2 network adapters, the first is attached to "internal network" on and the second to a "bridged adapter"
I then set the ip of the win2019 VM to 192.168.100.10 and the one for the Win7 machine to 192.168.100.50, both from the network configuration of the OSs.
I then activated the DNS service on the Win2019 and used 192.168.100.10 as DNS in the Win7 network configuration.
When I ping -4 server1 ( the anme I gave o the Win2019VM) from cmd in Windows7 I get as ip 192.168.100.31.
If I deactivate the bridged network adapters in both machines, I get the expected one, 192.168.100.10
If I reactivate the adapters, I get 192.168.100.31 again.
Seems WIN2019 gets the internal network adapter as second ethernet adapter.
From what I see on the course I am studing it is expected to have 192.168.100.10 as result of ping -4 server1 with both networks adapters active.
How can I get the DNS have server1 give 192.168.100.10 Ipv4 address when I ping it? Happy to provide more details if needed.
I am almost new to networking so please be patient if it is a stupid question. I checked the forum, but seems none posted this question here
Thnaks in advance
Edit this is the ipconfig /all for the Windows 2019 machine aka server1
This the win7 one
IPCONFIG /ALL from both servers.

IoT management page with P2P connection

I'm really looking for advice and a starting point more than anything. So I'll try my best to explain my end goals and the challenge. I want to set up a local WiFi connection (P2P) between a Rpi3 (or any embedded system really, running linux) and a laptop. The Pi should be the server and laptop the client. The raspberry PI is going to be reading samples over USB from an SDR. I want the laptop to be able to connect to the network the pi throws up, and be able open a browser and view the results. I'm guessing what i need to read up on is ports/sockets and web programming in general. The cheepy IoT sensors and light bulbs seem to be able to do this (opening network and forwarding data) relatively easily but i cannot find any information online to aid in my quest. All the Best and thanks in advance.
Since the embedded system will be running Linux, you can do something along the following lines:
setup the wifi as an Access Point (example). Also setup DHCP Server (example), so the wifi will assign an IP address to connecting laptop.
Install a webserver (e.g. Apache).
Create the webpage/ web application you need to "serve" the data. Install this into Apache.
Ask follow-up questions if you like.

NETGEAR Router: DNS Server Not Responding

I'm running Windows 7 64-bit Professional edition and I've been using NETGEAR Router WNR612v3 for a while now. I'm not a professional in networking, but apparently the DNS server all of my computers in this house use is not responding. All the computers network card settings are set to automatic, both in resolving an IP address and resolving a DNS server.
I've had this issue all morning and fixed it by making my main computers DNS server static listening to one of GOOGLEs public DNS server (208.67.222.222) and that works perfectly. I then put my computer back to automatically resolve a DNS server and went to NETGEARs control panel by accessing my default gateway address (192.168.x.x) and configured the DNS address settings. I set it to automatically get one from my ISP (Bahnhof SE). That didn't work, so I've set it to static and tested three addresses at a time using all of these:
213.80.98.2
213.80.101.3
208.67.222.222
8.8.8.8
8.8.4.4
with no avail. It seems that my computers just won't resolve the DNS server given by NETGEAR, or I'm just understanding this wrong. But the end result is that my computer is obviously not receiving the Public GOOGLE DNS server that I've set on the NETGEAR DNS Addresses configuration. Here are a few screen shots:
Screenshot #1
Screenshot #2
Screenshot #3
Screenshot #4
Any suggestions are greatly appreciated! Thank you in advance.
with the limited information you provided all I can do is speculate that the firmware on your router is outdated or faulty, try updating the firmware or connect to an open Wi-fi network to ensure that the router is the problem. You will have to find where the problem is to fix it. My bet is on the router based on the fact that several computers within your house are having the same issue, and when adding the dns server address statically on the computers it works. So update the firmware, if that doesn't work go buy another router.

getaddrinfo() returns 127.0.0.1 for remote host

I have an application which uses getaddrinfo() to translate from the hostname of a PC in a Windows Workgroup to the IPV4 address for that PC on the LAN. (Note, I don't mean getting the address of the PC the code is running on, I mean the address of another PC on the LAN!) This has been working in the field as well as in the lab for quite some time but now I have a Windows 7 (32 bit) PC that behaves anomalously. The hostname for this PC is "elbow".
I compiled the sample code provided by Microsoft for getaddrinfo() at http://msdn.microsoft.com/en-us/library/windows/desktop/ms738520%28v=vs.85%29.aspx
When I run this sample code on any PC on my LAN and specify "elbow" as the hostname, getaddrinfo() returns the loopback address 127.0.0.1 instead of the correct one (192.168.1.110). However, if I specify any other hostname getaddrinfo() returns the correct address!
At some point in the past "elbow" did NOT exhibit this behavior, so clearly something about that PC has changed to cause this behavior. I have tried restoring the PC disk image to a point where I think it did not cause this behavior, but that made no change.
It also makes no difference whether the PC is hardwired or wirelessly connected to the LAN. DHCP is enabled for all PCs on the LAN. The behavior is persistent even with a complete power-down of all PCs, routers and switches.
Hit a similar problem and wanted to post just in case someone else found this thread.
The same thing happened on our side with a customer installed computer. We found that the customer changed their hosts file to associate 127.0.0.1 with the pc's name... a separate program using getaddrinfo to find a certain subnetwork kept failing...they ended up renaming the computer temporarily to use this function but they also could have fixed their host file.
The hosts file on that Win 7 computer was found in /windows/system32/drivers/etc.
I wanted to update this with the answer. The elephant in the room was the ISP's DNS. I was under the mistaken impression that my subnet was isolated from the ISPs DNS but that was not the case. For whatever reason, their DNS is returning 127.0.0.1 for the hostname "elbow" but as soon as I renamed it to something else my problem went poof! I also uncovered another PC that had the same problem, and renaming it fixed it too. The thing both PCs have in common is that both had undergone OS reloads, but the problem did not become apparent until some time after those OS reloads.

How to quickly connect 2 PC together using Ethernet without router / DNS

In the field I often need to perform remote debugging on a target PC using my Delphi development IDE running on my (host) laptop. Because I cannot use any pre-existing network address infrastructure I use a cross-over network cable directly linking the two PC's. I then setup manual IP address of (say) 100.100.100.1 and 100.100.100.2 for the two and after much rebooting and fiddling I get the shared folders that I need. Finally after working in this way I have to carefully put things back to how they were.
This is pain though. There is a lot of typing and room for error. Further, sharing can take a while before things become visible. Is there some way that I can run something (or write a script) that would ease this process in any way?
Use the designated intranet IP ranges: 10.x.x.x or 192.168.x.x, not 100.x.x.x.
Run a DHCP server on your box. The other box will most probably be already configured to use DHCP to obtain an IP address, this is the default. Windows comes with a bundled DHCP server (at least some versions, install it as a Windows component), or you can use a third-party one.
You need zero rebooting on either box: all modern OSes allow to change IP addresses and routing on the fly, Windows is capable of this for at least a decade. Note that you don't need to change the IP address of your box. Often the secret of fast folder access is using the IP address, like \\192.168.1.1\share_name because name resolution services may take long time to kick in.
If you want both the link via the cross cable and a wired Internet/LAN link, just add another network card to your box (slightly more expensive with notebooks) and have the DHCP server only work with that dedicated card, so you don't need to touch the Internet-connected interface at all.

Resources