Internet Connection Sharing (ICS)

[dean_warez]

Hi guys,
im new to WinGate by the way.

I've set up a proxy (www) on the server pc; on this proxy it just basically uses two internet connections etc...

How can i set up a computer connected via a NIC to my server to use this proxy aposed to one of the internet connections.?

Do i need wingate on both pc's?

Dean

[erwin]

Hi Dean

For your client machine, you can use three different connection methods. NAT,Proxy, or the WinGate Internet Client, each with their own benefits etc.

NAT(Network Address Translation) method is probably the easiest to explain the setup to get you up and running quickly.

On the client machine just make sure that the DNS and Gateway entries in the network properties have the internal IP of the WinGate server listed.

This way all Internet requests will be sent to the WinGate. Just to make sure it doesnt try to use another connection,(such as a modem on the client machine) check in the connection settings in your clients browser and make sure the "never dial" option is selected.

The WinGate helpfile has more on the setup of the other connection methods, found under "Connection Methods" chapter.

Regards
Erwin

[dean_warez]

Im using wingate 5.2.3 can you please give me a short mini tutorial on how i would do this. I tried but i cant find the DNS and gateway enteries. Basically im just all confused.

Dean

[Pascal]

Hi Dean,

The easiest way is to find the TCP/IP properties of your client machine. Depending on the Operating System in use it will be in a different place. Usually however you can find it by getting properties for your network cards. There you will find the entries for Gateways and DNS Servers. What you want to do is add the WinGate Server's Internal IP as the default gateway and DNS Server on the client machine's internal network adapter's TCP IP properties.

Once you've done that check that you have access to the internet. If you do, all's good. What you might want to do then is go into GateKeeper and switch to the WWW Proxy Service and make sure that "Redirect connections from NAT or WGIC" is ticked. You will find that under the sessions tab.

That setup will give you the ease of configuration for NAT (Using the def.gateway + dns serer option) while allowing you to use a proxy like setup (The transparent redirection)

[dean_warez]

Whats the WinGates Server Internal IP? Where can i find that? Also when i set up the www proxy do i need to check the bind to any internal adapter?

[Pascal]

Open a command prompt and type "ipconfig /all". That should list the network adapters and ip addresses on your WinGate Server. You are looking for the ip-address of your internal network card (The one pointing to your LAN)

If you are using NAT you generally don't need to check bindings. If you follow the directions that Erwin gave you you will need to double check that the WWW Proxy Service is listening on the adapter who'se properties you found above. (It should normally be bound to that, anyway) Most of this is listed in the helpfile, though - which should give you a good overview of the three different methods and the advantages / disadvantages of them.

As a side thought, you can use a version 5.2.3 license with 6.0.3. 6.0.3 is significantly easier to work with and it's driver is much improved over the 5.x versions.

[dean_warez]

Ok... what do i put in the IP address and subnet of the client PC's NIC?

All what it does at the minute is display loads of blocked ports coming from the client NIC to the wingate server in the firewall tab. Its port 1024 its blocking to 53 i think. And i cant use the net on the client pc.

Is there an easier way? Can i just install the wingate client internet thingy?

Dean

[Pascal]

If you go to your WinGate server and run "ipconfig /all" from a command prompt you will see something like:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon Gigabit Ethernet 10/10
0/1000Base-T Adapter, Copper RJ-45
Physical Address. . . . . . . . . : 00-11-2F-0C-B4-A2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.13.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.13.1
DHCP Server . . . . . . . . . . . : 192.168.13.1
DNS Servers . . . . . . . . . . . : 192.168.13.1
Lease Obtained. . . . . . . . . . : Sunday, 24 October 2004 11:04:48 a.m.
Lease Expires . . . . . . . . . . : Tuesday, 19 January 2038 4:14:07 p.m.

If you have multiple adapters (Network cards, modems, etc.) in your machine you will see more than one. You want to pick the one that is connected to your local network. (The hub/switch that leads to your other computers).

The bit that in my configuration is highlighted in bold, italic and underlined is the IP address of my local area connection. Find yours. That is the number you have to put into the client configuration. If you post the results of your "ipconfig /all" here I can highlight the numbers for you.

Second thing. Go into "GateKeeper" - "Options" - "Advanced". (It should be the first, second or third menu from the top). There is a tab that allows you to set the properties of your adapters. From the sound of it, your adapters are set incorrectly (Otherwise it should not be blocking traffic from your local network). Are you using public ip ranges for your local network? Make sure that your local network connections are marked as "Private, Trusted" while your internet connection is marked as "Public, Untrusted".

Third thought. WGIC could potentially be easier. You need to setup the application, make sure it discovers the WinGate server and then you might need to configure it to make sure that all your applications can get out to the internet. (Might need to change some modes). Configuring NAT is the easiest possible option, followed by WGIC, followed by proxy. (IMO)

[dean_warez]

Ok, ive taken a few screen shots (10)

Go to www.freewebs.com/the-exodus/wingate/

then add the following to the end:

1.jpg
2.jpg
3.jpg
etc...
it goes to 10.jpg (which is the client few of the ipconfig /all)
where as 9.jpg is the server side of the ipconfig /all

Dean

Tell me if you require anymore screenshots[/img]

[Pascal]

Okay. Your internal IP address is 169.254.158.179. All of that is setup fine. However, two problems:

1. You've bound your WWW Proxy Service to 127.0.0.1 ONLY. Which means that it will be listening for connections from the WinGate Server only.

2. You've put the WWW Proxy Service on port 1111. Which means the Transparent Redirection for it won't work (In 5.2.3, in 6.0 it's possible to have that kind of setup working)

3. The options for 169..... should be "Public:No", "Trusted:Yes".

The first question is - why that range of IP addresses?
Secondly, why put the WWW Proxy Service on port 1111?

If you make the change for the interface (3) then all should be functional - although it won't be going through the WWW Proxy Service.

If ALL you want to use is the WWW Proxy Service (Web browsing, nothing else) then the easiest option might be to:

Client
Open Internet Explorer, go into "Options" menu and into the "Connections" tab and click "LAN Settings". In there, click "Use a proxy server for ...." and specify the IP address as 169.254.158.179 and the port as 1111. Then okay out of it.

Server
Bind the WWW Proxy Service to 169.254.158.179 (As per screenshot 3).

Your client should now be browsing through WinGate.

[dean_warez]

Thankyou very much!

I have done it without setting the proxy stuff in inter explorer on the client.

I have reconfigured the www proxy to port 80 instead of 1111, i only had it on 1111 cos i followed a tutorial on how to use multiple broadband connections with wingate etc... and thats the port they used.

So does it mean now that my client machine can now use my proxy server that i have set up on my pc, meaning it has a 3.5MB d/l speed :-)?

Cheers m8

If you have a paypal account or sommit for the company or for yourself tell me and ill donate some money. You've spent a while helping me m8.

Thanks again

[Pascal]

So does it mean now that my client machine can now use my proxy server that i have set up on my pc, meaning it has a 3.5MB d/l speed :-)?

Add the connection speeds? Two Cable modems? That would be too nice. In 5.2.3 the concept of multilinking those adapters are not quite as good as it could have been. With 6.0.3 it is better, but I think your best option would be to link them at OS level if you want them "added" together.

[dean_warez]

well they are used in rotation. So kinda linked together. Depends what programs support proxy stuff.

How you link them at OS level?

So is there a different between versions 5 and 6 of wingate on how well it uses these connections in rotation then?

[Pascal]

well they are used in rotation. So kinda linked together. Depends what programs support proxy stuff.How you link them at OS level?

http://support.microsoft.com/default.as ... -us;307849

That should give you an overview for XP.

So is there a different between versions 5 and 6 of wingate on how well it uses these connections in rotation then?

Definately. Between WinGate 5 and WinGate 6 we made major improvements in the WinGate network driver.

We also improved Bindings, so you can specify a policy rather than binding to a specific IP. This is fantastic for USB / cross-over cable'd machines, etc. because even if the Internal Interface is down temporarily, WinGate will still rebind when it becomes available.

The other place that saw major work was the concept of Gateways - so you can setup connection rotation, fall over (In case one goes down), etc.

You can use 6.0.3 with your 5.2.3 license key - all you need to do is activate it. It'll give you all the functionality you currently have. If you do decide to do that, I'd recommend that you backup your existing 5.x registry setup. The installer for 6.0.3 should prompt you to do that, but just so you can revert back easily if you decide you don't like 6.0.3 or feel more comfortable with 5.2.3.

[dean_warez]

i cant do the PPP multilink because my ISP doesnt support it (NTL)!

o well... wingate does me fine to be honest. It practically is doubling my connection when using a download manager that has proxy and mutliple connection settings (DAP). :-)

I got 2x 1.5mb cable connections... now i can download at 355bps i think is the right unit.

Dean

[kgoodknecht]

Okay. Your internal IP address is 169.254.158.179. All of that is setup fine. However, two problems:

1. You've bound your WWW Proxy Service to 127.0.0.1 ONLY. Which means that it will be listening for connections from the WinGate Server only.

2. You've put the WWW Proxy Service on port 1111. Which means the Transparent Redirection for it won't work (In 5.2.3, in 6.0 it's possible to have that kind of setup working)

3. The options for 169..... should be "Public:No", "Trusted:Yes".

The first question is - why that range of IP addresses?
Secondly, why put the WWW Proxy Service on port 1111?

If you make the change for the interface (3) then all should be functional - although it won't be going through the WWW Proxy Service.

If ALL you want to use is the WWW Proxy Service (Web browsing, nothing else) then the easiest option might be to:

Client
Open Internet Explorer, go into "Options" menu and into the "Connections" tab and click "LAN Settings". In there, click "Use a proxy server for ...." and specify the IP address as 169.254.158.179 and the port as 1111. Then okay out of it.

Server
Bind the WWW Proxy Service to 169.254.158.179 (As per screenshot 3).

Your client should now be browsing through WinGate.

I see a big problem, The Wingate server is using a APIPA number, it should have a static address. Don't use 169.254.x.x as your private range. The APIPA number is used when a machine cannot contact a DHCP server, and can result in a conflicted IP address. there is no way to predict which APIPA number windows is going to use a start up and is why you shouldn't use that IP address range. But if you do get a machine with an APIPA number then you should check the cables or DHCP server.

[Pascal]

The first question is - why that range of IP addresses?

From the screenshots, it seemed as if those IPs were actually assigned manually. Hence the question. Apologies, I should have pointed out that it was an improper range, rather than ask why. Thanks for that, Kevin.

[kgoodknecht]

The first question is - why that range of IP addresses?

From the screenshots, it seemed as if those IPs were actually assigned manually. Hence the question. Apologies, I should have pointed out that it was an improper range, rather than ask why. Thanks for that, Kevin.

With all due respect Pascal, I just wanted to point that out since on screen shot 9 the ipconfig /all states that it is using an AutoConfiguration IP address which tells me it's not static. I saw where you asked why he was using that range, and the question you put forward was not answered. I just wanted to make it clear it is not recommended to use an APIPA range in a network, and definitely never as a staticly assigned address.

[Pascal]

I completely agree with you! Which is what I'm trying to say, but it must be my Monday today. (Even though it's Tuesday)

What got me about the ips was the client config (Think that's screenshot 10?) which was in the same range, but with an IP of 169.254.158.178 (Not .179 as the server) and with the default gateways and dns servers pointing at the server. That was the bit that made it seem as if those were 'configured'.