@michiganbb So you thought that necro-posting and whining about a 3yo post would be useful? Give it a try and see if that fixes your issue. You would have to do this anyway. Even if something works for one, doesn't mean there's a guarantee it works for you,. Backup the PC and try the changes. If they don't work...move on to something else.
There was NO resolution here. Client was one of those who was difficult getting payment from so we terminated the relationship before we did anything else.
In the Network Adapter options, disable anything that says power managment.
There's a couple of power management options on the NIC, but IIRC there's some bus-related power management options in the power-profiles. I've seen the NIC-related options take an interface off-line, but where you're saying that it's disappearing completely, I'd be more inclined to look at PCI or chipset drivers and settings.
However, all the concerns about licensing should raise red flags about your system. Yes, there are times that having something require licensing is okay or even desired. But you should always see it as a truly huge risk and one that you have to consider carefully. Licensing makes the most sense higher up the stack. For example, the application itself is the most likely object to justify licensing. The cabling is the least. Imagine how ridiculous it would be if your rack, desks, and cables required that you have a special license for each use!! It would be insane and you'd never stand for it (you might have to stand if your chair was licensed only to someone else's butt.)
Your hypervisor and operating system are closer to the cables, rack and desk than they are to the application in this way. These aren't components that you want to have at risk due to a need for licensing. Sometimes you have to, but it is rare and a "have to" would only be caused by an application and if an application puts you in that position for many companies that alone is a reason to question the viability of the developers behind said application.
At a minimum, something like ESXi introduces totally unwarranted complexity and risk and is something that can be quietly, transparently, removed and fixed during this process.
We now have 6 people who work out of state. 4 in Texas, 1 in California and 1 in Maryland. They all have domain connected laptops that I pre-configure with our applications before they get them and they connect to our VPN via the build in VPN connector in Windows 10/11. Our VPN is provided by our Windows Server with port forwarding on our ISP provided Vigor firewall.
I understand issues like internet pipes and the "hops" it takes to get back to our office on VPN but we see some significant drops in speed. Some apps that require a lot of file transfers, are almost unusable.
Is there anything I can do on our end to aid in some speed increases? I'm also willing to spend money if we have to on software or a network appliance.
You should do some basic investigation so you know what you should expect.
What is the speed in/out of your internet link to your VPN server?
What traffic comes in/goes out over this link besides VPN traffic?
Do you have any traffic shaping in the firewall?
It's very possible that low priority internet traffic, from clients in the office, is starving your VPN link of bandwidth.
@scottalanmiller - Just curious are you still using Tactical or just Mesh these days? I've been playing around with Tactical internally and definitely a great solution. I know you mentioned a while back you were using that and Mesh separate from each other.
We use both. Tactical has been pretty good. Definitely use Mesh 90% of the time and Tactical just 10%. But it has been a good tool and we like it.
Of course though - this thread is about Windows Server, not desktop - where this should be MUCH less of an issue with properly designed code.
Same code, they don't make it twice. Less hardware hotplugging, but probably just as many lines of code in use.
Less desktop apps on the platform, but you're right - the base code is the same.
Fewer desktop apps, maybe. But in the Windows world, server often is treated as a desktop (like 90% of the time) so the reduction is rarely what you'd hope. And there tends to be lots of server-only code too, often running as desktop apps.