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...
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
So, I'm looking at various ways to cleanup the nitty gritty IT stuff that users don't see and something that's been in place since before I came on-board is the STP / MSTP setup.
Looking at how things used to be setup, it made a certain degree of sense as there were 2 core switches (HP 3800 series) and each one was the root for an instance. We've since moved to one modular core (HP 5400 series), so it's the root for all instances.
My main concern at the moment is that we've since added several vlans into the mix that aren't part of either instance and if I'm going to have to update and propagate a new STP config would it be simpler / better to just put all VLANs into a single instance and be done with it?
Thoughts / pros / cons?
@scottalanmiller said in Recovering SQL Server 2005 Databases:
Let's assume no hardware failure. Is there a good path? We have the data, intact. It's just really old and needs to be updated.
FWIW I'd mount on 2005 then backup/restore on the current version of your choice.
https://dba.stackexchange.com/questions/222868/upgrading-sql-server-2005-to-2016
Forgetting the PCI stuff for a second, will the tablet even connect with / play nice with a wireless that doesn't have internet access? I can't speak to W10 but recent experience with Android and Apple has them refusing to use the wireless unless it can do a connectivity check out to 8.8.8.8 or another reliable resource.
Didn't they change the ability for local admin accounts to RDP like a year before EOL? My spidey(sp?) sense is tingling on this one but I'm not 100% sure what M$ changed along the way or exactly when.
I feel your pain. I had to move a bunch of stuff from SQL 2000 to 2012 R2 a while back and since it's going to be a multi-step process anyways I'd suggest mounting / restoring the 2005 stuff to another 2005 instance and then go through the process of upgrading.
** Might be easier than I recall, there was an extra step when coming from 2000 because of the way that 2000 handled paged space metadata or something along those lines, I thought it was between 2005 and 2008.
A lot of good things to consider here so far. Keep spanning tree in mind as soon as you're dealing with topology changes and intermittent issues. It can come up and bite you in the a$$ if you've got a static config somewhere or a new vlan that isn't part of the config.
Good to see that you were able to resolve this. From a security perspective I'd suggest disabling that SMBv1 access that we're seeing in your screenshot.
-- Cheers!
Is refusing the delivery an option? If you've got the cancellation request in writing then I'd simply refuse to pay any sort of restocking fee.
Dashlane is what we had as a major contender the last time we looked at this
@magicmarker said in File transfer drop:
Server 2019 enables by default some Hyper-v feature called RSC. I wonder if this is your issue. Someone had this same issue as me and turned it off and my Read speed went up to the 900Mbps limited by switch speed now.
https://serverfault.com/questions/976324/very-poor-network-performance-with-server-2019
@Jimmy9008 Looks like this might be your silver bullet
@Jimmy9008 said in File transfer drop:
@notverypunny said in File transfer drop:
So a couple of things I'd be looking at if it were me:
- RAID card config: write-through / write-back will have performance impacts (but should hit S2019 and W10 equally)
- Network vs storage:
-- iperf3 only runs in memory, so it completely removes storage from the troubleshooting equation, if you see the same type of drop-off testing with iperf3 you know that there's a networking gremlin somewhere that needs to be dealt with.
-- something like LANSpeedTest actually writes and reads a file on the far-end storage, so it should provide the same results as your typical file transfer, you can also arbitrarily set the transfer size, just in case you want to test something bigger than what you've got as a static file.- What's actually running in the OS at the same time
-- use something like processhacker to see what else might be using the network or other IO when your file transfer slows to a crawl.
--Maybe there's security configs being applied to your servers and not the W10 guests that aren't being taken into consideration.I'm not sure if these will help...
The physical servers over the network work fine. Full speed ahead! So, cant be RAID settings, network issue or storage. Physical <-> Physical is perfect. What is the point of testing with iperf, im saying already physical <-> physical is perfect...
The issue is with the VMs. From a VM on host A to a VM on Host B, im seeing much slower speeds. From physical A to physical B, its fine.
Granted, your physical network and storage may be up to par from host to host. You still need to identify where the VMs are having issues, so it's from within your VMs that you need to do this testing, to see if the problem is with your virtualized storage / network / other. Virtualization passthrough sounds like a miracle but it doesn't always work as expected.