Jump to content

WannabeSysAdminx

Honorary Members
  • Posts

    47
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Not sure where to look. I'm only trying to learn. Also, isn't this subforum called 'general help'?
  2. I'll try to sum this up as well as I possibly can I'm in the process of setting up my homelab. I have Laptop 1, Laptop 2. On Laptop 1, I am connected to the Internet via WIFI. I have VirtualBox running on Laptop 1, network mode: Bridge Adapter [insert name of my WIFI card]. I have created a VM running Windows Server 2019. This VM is running DHCP, AD DS and DNS server roles. First I set up the DHCP, after that I set up AD DS and DNS. I created the DHCP scope without issues as well. I could join another - client - VM to my AD domain without issues but I can't join Laptop 2 (physical device) to my domain to save my life. When I plug the Ethernet cable into Laptop 2, it asks me if I wanna enable network discovery on it (including the AD domain name in the message): I said yes. Then I tried to join it - Ethernet still plugged in - to my AD domain, but it said: 'Cannot join device to domain; network path not found'. When I checked the IPv4 stats, the IPv4 DNS and DHCP address both pointed to the IP address of my Server VM. So it should be fine theoretically but it didn't work in reality Should I have disabled the DHCP server function on my physical router? Should I have connected Laptop1 to the Internet via Ethernet instead of WIFI before creating my Server VM? Please help me
  3. Update: Laptop crashed again today, 3 minutes ago. Crash followed by reboot automatically.
  4. Is it okay if I ran a Kaspersky Total Security full scan overnight and now it says there's no malware on my system?
  5. For the past 7 days, my laptop has crashed at least 1x a day, followed by immediate reboot. I redirected the minidump location to my external HDD, and when it crashed again, I checked out that folder, but there was no dump file in it. Windows hasn't registered the last 5 crashes in the form of a dump file for some obscure reason.
  6. So I ran sysprep on this image, then booted into the Macrium RE to capture this now sysprep'd image. Problem is, I can't figure out how to connect my physical external HDD to this VM so that in Macrium RE - on the VM - I could capture the image onto the physical external HDD. Alternatively, I tried to just grab the VHDX image file and deploy it on a physical machine to no avail too. Am I not supposed to be able to deploy a VHDX image on a physical machine? Regarding this second second part, I tried to boot into Windows.ISO then select the Troubleshooting option, then Restore System Image, but it couldn't detect the VHDX file I had on the external physical HDD connected to this physical laptop
  7. So I did what you had advised and now the wireless blue light just keeps on flashing, it won't be detected by my laptop (windows 10). The SSID and IP Address were in fact cleared completely.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.