This eliminates the need for NetBalancer/NetLimiter so that rather than a flat, hard limit, you could throttle based on protocol, time of day, MAC address, etc.Normally there are two types of restrictions for shareware. You might even want to consider WinGate Pro (although probably cost prohibitive for small needs).
Of course, I suppose you could eliminate the hardware router on LAN2 completely in favor of WinGate if you can live w/ the three concurrent user limit.
And unlike WinGate, ICS doesn’t have any such throttling capabilities itself. IOW, it doesn’t run as a wholly independent app/service. NOTE: I had considered throttling ICS, but that might prove difficult since the ICS process appears integrated into the Windows firewall service. The only reason you’re using WinGate is to bridge those two network connections and still be able to throttle that process w/ the free versions of NetBalancer or NetLimiter. Frankly, even licensing is not really an issue since the only client is the hardware router on LAN2. But perhaps it’s not an issue in your case. Unfortunately, those users are now double NAT’d behind two firewalls, and so it complicates remote access. The free version supports up to three (3) concurrent users (not just three seats). One solution might be to employ a software router, say WinGate. And while they do make apps for throttling network bandwidth, they typically do so based on a "per process" basis (e.g. Problem is, that creates a single, logical network that's hard to control without affecting your own network limits. I assume you're supporting this configuration using a simple Windows bridge in Network Connections.
0 kommentar(er)
