@JaredBusch Might take another look then... My FTTH comes in as a tagged VLAN and it wouldn't pick up a dhcp lease on v2, even after a few reboots but once I downgraded to v1 it picked up the lease from the ISP right away.

1. Download the current firmware to your laptop.
   https://dl.ui.com/firmwares/edgemax/v2.0.8-hotfix.1/ER-e50.v2.0.8-hotfix.1.5278088.tar

Just got one for home last week and I had to downgrade to the v1 firmware to get VLAN tagging to work, just a heads up. It might work on the v2 firmware but I didn't have the time, patience or inclination to arse around with it more than necessary. No more ISP gear in the home network except for the SFP that I had to move from their CPE to the ERX-SFP.

https://www.wilsonsignalbooster.com/

From what you're saying it'll probably take a custom solution. I'd hazard a guess at a high-gain directional antenna on the roof (to get connection with the cell network) with omni-directional repeaters to cover the yard

ZeroTier is a pretty cool solution, but the OP problem with AnyDesk could also be related to power-management settings having changed (a week ago... Windows update induced problems anyone?).

Knowing how users tend to be, if you can make their original solution work how it used to with some power management tweaks (don't forget the options directly on the NIC) you'll be a $DietyOfChoice. Just some food for thought.

Cheers

@Dashrender said in Windows Domain join issue:

@fuznutz04 said in Windows Domain join issue:

Nothing that stands out for this. I am getting replication errors that I need to solve. (having issues replicating to this DC to my COLO DC, but I wouldn't think that this would cause issues with me joining a PC to the domain at this location.)

Yeah, your PC had flipped DNS to the external one - so no surprise on the replication errors.

Target account name is incorrect - huh..
not sure what would be about...

Hate to be the bearer of bad news but you might have to fix AD first...

https://support.microsoft.com/en-ca/help/2183411/active-directory-replication-error-1396-logon-failure-the-target-accou

EDIT: just came across this:
https://atherbeg.com/2017/01/04/error-while-joining-machine-to-domain-logon-failure-the-target-account-name-is-incorrect/

@dbeato said in Windows Domain join issue:

@fuznutz04 said in Windows Domain join issue:

It's been forever since I have worked with Windows domains. But today, I have to join a Windows 10 PC to a domain. I keep getting the error:
"The specified network name is no longer available."

Primary DNS is set to the DC IP on the PC .
Pinging domain name gets a reply from the DC IP as expected.

I know this is something simple, but I am not finding it.

Any ideas?

What is the secondary DNS on the network card?

^^ This -- make sure that there isn't an external DNS as backup on the machine you're trying to add to the domain, even if the DC is the primary it'll bork on joining if there's anything external to the domain as secondary / tertiary etc

Has that admin account perhaps hit the threshold of allowed domain joins? There are a few ways to get around it if that's the case.

.... Googling really quickly leads me too believe that it should actually tell you if this is the case, but I'll leave this here just in case M$ is being difficult again...

@Dashrender said in MSTP with multiple instances - Yea or Nay:

@notverypunny said in MSTP with multiple instances - Yea or Nay:

@scottalanmiller said in MSTP with multiple instances - Yea or Nay:

Are the VLANs needed? What are they for?

Traffic isolation / functional separation / security. Servers / Management / endpoints / VDI / Wifi / telephony etc etc etc

One would ask if any of those are needed today?
Functional separation I could see if you have two desperate networks but need to use a single ethernet fabric. I have that, my Guest WiFi has it's own firewall and own internet connection, yet we share the APs. it's on it's on VLAN with no routes between prod and guest.

But on the prod side, in a LANLess world, is that really needed? Of course, few of us likely actually have LANLess set ups.

Skimming through the LANLess explanation @travisdh1 posted a while back, I think we're somewhat a mashup of it and segmentation. Some of the VLANs in question are end-point only and as such the security isn't as tight as the ones that are used in the server-room / data center functions. If I were designing something from scratch, LANLess would certainly be something to consider, but since this is far from a new build, I doubt I could start to justify the headaches that changing VLANs and IP addressing would entail.

To come back around to my initial question, can anyone point me to any pros / cons with regards to having multiple instances of spanning tree given that we no longer have 2 devices acting as root bridges?

@scottalanmiller said in Recovering SQL Server 2005 Databases:

We got a 2008 R2 that we tracked down. And they were able to get backup files rather than the original database files only, so looking like it will be much easier.

Good news, much less pain than having to deal with mounting on 2005 and then backup/restore to current.

@scottalanmiller said in MSTP with multiple instances - Yea or Nay:

Are the VLANs needed? What are they for?

Traffic isolation / functional separation / security. Servers / Management / endpoints / VDI / Wifi / telephony etc etc etc