The Spring BBSApps › Topic 356
Help!

WinGate

Topic 356 · 5 responses · archived october 2000
» This is an archived thread from 2000. Want to pick up where they left off? post in the live Apps conference →
~buzz seed
If you want to connect a LAN to the Internet, you basically have three options. The first is to set up each workstation as an independent connection point to the 'net. This can be done using analog modems, ISDN lines, cable modems, or even leased lines. The cost of this option quickly mounts as the number of workstations on the network increases due to the fact that each station needs its own modem (or similar connection equipment), phone line, and in some cases Internet account. Another option is to purchase an external router or similar network-to-Internet hardware (check out Dayna's NetCenter Internet Station for one of the better examples of Internet station hardware). This is another expensive route as the cost of such equipment begins at around $500 and can quickly reach the thousands depending on types of services offered and number of users supported. Neither of the first two options makes sense for many small networks because of the substantial costs involved. Thankfully, there's another alternative available. The final and most cost effective option is to purchase and install specialized network-to-Internet tools like WinGate, MidPoint, and Trumpet FireSock. These software applications allow you to share a host computer's modem and Internet connection with other users on the LAN. Modem sharing clients require only one modem and connection at minimum and can generally work over a variety of mediums including analog modems, ISDN lines, and leased lines. WinGate is one of the oldest and most popular modem sharing applications. While it does lack the modem teaming capabilities of some Internet hardware packages or clients like MidPoint, WinGate does support a wide variety of Internet protocols to ensure that your networked users can fully utilize the 'net. Support for HTTP (web), HTTPS/SSL (secure web), SMTP and POP3 (e-mail), NNTP (UseNET news), Telnet, FTP, and IRC services are just the beginning of WinGate's extensive set of features. WinGate can also be setup with RealAudio/VDOLive proxy capabilities or as a AutoSOCKS/SOCKS5 server (allows SOCKS compatible clients to access the Internet as if the client was directly connected to the 'net). All of the major applications including Netscape, Internet Explorer, and Eudora can be automatically configured to utilize WinGate's sharing capabilities (with or without the use of AutoSOCKS). And when necessary, switching back to a guest computer's local non-shared modem is a simple process that involves automatically restoring the normal proxy settings of your applications. Like MidPoint, WinGate also utilizes a shared cache that allows users to quickly access web pages that have already been downloaded by others without having to reconnect to the 'net. WinGate sports an attractive and user-friendly interface, but the help documentation included with the program could use a little work. Getting up and running with the client is relatively straightforward, although it's not as easy as doing so with a client like MidPoint. If you do have any problems getting WinGate to work, the WinGate Help Desk on the web is usually the best place to begin looking for answers. Additional WinGate features include acting as a general proxy server (eliminates the need for each workstation to have its own IP address), acting as a powerful firewall (authorizes and controls the information that passes between the network and the Internet), logging and auditing capabilities, remote control and user authentication services via the integrated GateKeeper client, mapped links (for applications like IRC clients and newsreaders that generally lack support for traversing firewalls or working through proxy servers). WinGate is available as a Lite version that begins at $110 for 2+ users and a Pro version that begins at $250 for 2+ users. Both versions of the client are free for two user networks (the host machine and one guest computer). If you're looking for an inexpensive way to share your modem and Internet connection with the entire network, WinGate offers a great selection of features in an attractively priced package that is sure to please even the stingiest of penny pushers. Pros: Inexpensive way to share modems and 'net connections over a small network, excellent set of features Cons: Lacks modem aggregation capabilities, could be easier to set up, help documentation needs work Version Reviewed: 2.0e Date of Review: 9/22/97 For the latest information on WinGate, check out: http://cws.internet.com/32lannet.html#wingate
~sixx #1
Purchasing wingate 3.0 to replace MS Proxy on NT server 4.0 running IIS is a big problem. First off, if you have problems getting any of the clients to connect, you're basically out of luck. Wingate FAQs on the web aren't helpfull. I wanted to be able to get Macintosh clients to be able to surf WWW, telnet, ftp, POP3. All my mac clients can do is surf the web. There is no help at all provided by Wingate in this area, although Wingate boasts that it can be done- they just don't want to tell you how. Next off, I've noticed on the two machines I've installed Wingate on, that they both crash at random. This requires me to physically stop and then restart the Wingate engine. As my reseller couldn't help me, I emailed Wingate. If you have a registered version, Wingate says they'll provide email support. I received back information telling me to contact the reseller. When I replied, asking Wingate to please help me because my reseller couldn't help me, I was informed on how I could apply to get a refund. Some customer service!
~terry #2
They've put you in an endless loop! I believe Symantec has a similar product, have you heard of it?
~terry #3
Bob Braach's comments: we run Wingate as a proxy server. It runs on the machine that's connected to the DSL line. A second NIC in that machine connects to the hub (or you can connect two machines directly using the right kind of cable). The machine with two NICs has two IP addresses, one to the DSL port and the other is an internal address for your house (by convention, you use 192.168.0.x, where x=1 at the machine with 2 NICs and x=2-n for the others). We run about 8 pcs off the dsl line and it works fine. You can license a 2 pc home version of Wingate for not a lot of money and it is pretty easy to set up. The only problem I ran into (which I fixed with advice from somewhere north of here in this topic) was a conflict in windows networking. Don't put any windows client networking on the DSL link or it will cause a conflict). I'll be putting wingate in at home so my kids don't have to fight over the dsl connection as soon as I have time.
~sges #4
It is not strictly correct to sa Wingate lacks modem aggregation capabilities ( I am ignoring MultiPPP). Wingate Pro can rotate request between any number of connections, for example three modems with ordinary PPP accounts, even from different ISPs. If the connections are identical (two 56K modems) this give you double the throughput. Wingate cannot do Dynamic load balancing or split downloaded files accross connections however. However I found it to be very stable unlike Midpoint where Dynamic load Balan ing can misfire and force you to hang up one modem to get any throughput.
~terry #5
Will it work with ISDN routers?
Help!
The Spring · spring.net · Apps / Topic 356 · AustinSpring.com