Hi, Guest
Daniel - you have an altrusitic streak the size of Alaska. Kudos for not only finding the problem but resolving it for your officemates as well.
My opinions on paid vs. free software?
Pros:
Paid - generally better tech support and patch availability, better features (for the most part), easiest use for non technically-minded people. Day-to-day management is easier.
Open-source - more variety, lower initial cost per unit, lower security risks due to lack of worldwide acceptance and its feasibility as a target for hackers, etc.
Cons / Operating system anecdotes:
MS - W2K3 Server and ISA 2004 (newer version of MS Proxy), new server rollout as the "gateway" for our office to the Internet (eventually). Handles not only local-to-the-server traffic, but also WAN traffic from shops (8KMs away) and Sudbury office (125 KMs away). ISA 2004 hijacks the routing tables and MS's RRAS functionality, refusing to allow you to redirect the proper data flow back to the remote sites. Ordinarily this is a 5-second operation to configure. Solution: Install an older version of ISA that doesn't interefere with routing. Problem solved. Ease of solution - about all we were ready to do as MS says this wasn't the case, but nothing else was left to do EXCEPT switch proxy software.
Linux - Configuring a Linux box for wireless surveying and intrusion detection. All current "good" releases of Linux apparently lack native D-Link WLAN support (even with Broadcom chipsets on the card). Found the right driver on the Internet. Downloaded it. Followed standard procedure to add to the kernel and recompile. First 2 attempts fail, after realizing we were missing an obscure setting in a config file during one of the "make" operations. Finally get the driver added to the kernel. Compiled. Reboot. Won't load. Revert to previous kernel. Boot. Return network card and try again with a different card. Still a WIP. :rolleyes:
My opinions on paid vs. free software?
Pros:
Paid - generally better tech support and patch availability, better features (for the most part), easiest use for non technically-minded people. Day-to-day management is easier.
Open-source - more variety, lower initial cost per unit, lower security risks due to lack of worldwide acceptance and its feasibility as a target for hackers, etc.
Cons / Operating system anecdotes:
MS - W2K3 Server and ISA 2004 (newer version of MS Proxy), new server rollout as the "gateway" for our office to the Internet (eventually). Handles not only local-to-the-server traffic, but also WAN traffic from shops (8KMs away) and Sudbury office (125 KMs away). ISA 2004 hijacks the routing tables and MS's RRAS functionality, refusing to allow you to redirect the proper data flow back to the remote sites. Ordinarily this is a 5-second operation to configure. Solution: Install an older version of ISA that doesn't interefere with routing. Problem solved. Ease of solution - about all we were ready to do as MS says this wasn't the case, but nothing else was left to do EXCEPT switch proxy software.
Linux - Configuring a Linux box for wireless surveying and intrusion detection. All current "good" releases of Linux apparently lack native D-Link WLAN support (even with Broadcom chipsets on the card). Found the right driver on the Internet. Downloaded it. Followed standard procedure to add to the kernel and recompile. First 2 attempts fail, after realizing we were missing an obscure setting in a config file during one of the "make" operations. Finally get the driver added to the kernel. Compiled. Reboot. Won't load. Revert to previous kernel. Boot. Return network card and try again with a different card. Still a WIP. :rolleyes:
Daily driver 1: 2007 Jeep Wrangler Unlimited Sport "S"
33" BFG Mud-Terrain KM2s, lots of Rough Country gear - bumper, 2.5" lift, swaybar disconnects, Superwinch 10,000lb winch, Detroit Locker in rear D44 axle, custom exhaust, K+N filtercharger, Superchips-tuned.
Daily driver 2: 2006 Subaru Legacy GT
COBB Stage 1+ package - AccessPort tuner, COBB intake and airbox. Stage 2 coming shortly - COBB 3" AT stainless DP and race cat, custom 3" Magnaflow-based exhaust and Stage 2 COBB tune.
33" BFG Mud-Terrain KM2s, lots of Rough Country gear - bumper, 2.5" lift, swaybar disconnects, Superwinch 10,000lb winch, Detroit Locker in rear D44 axle, custom exhaust, K+N filtercharger, Superchips-tuned.
Daily driver 2: 2006 Subaru Legacy GT
COBB Stage 1+ package - AccessPort tuner, COBB intake and airbox. Stage 2 coming shortly - COBB 3" AT stainless DP and race cat, custom 3" Magnaflow-based exhaust and Stage 2 COBB tune.