Please help me with a NAT problem

[minute]

I have a LAN winth 5 users and a XP server, 4 of the users have visible IPs, but the 5th one does not, so, I want to share an IP with the 5th one, but the others to remain visible, can anyone explain me step by step how to do that, I`m new in routing and stuff, and I never use Wingate befor. If this software can solve my problem, it really is a powerfull program.

[MattP]

Hi,

What do you mean by visible IPs? WinGate will allow you to share your internet connection with all the machines on the LAN, so you would only need one external IP address to reach all machines. What exactly are you trying to do?

Regards,

Matt

[minute]

I have on the win server a wireless card connected on the internet and a LAN card, who is connected to a switch. I have visible IPs (routable) let`s say on wireless 80.1.1.1 and on lan 90.1.1.1 (it is just an example). In my network, I have 3 computers with routable IPs like 90.1.1.2 .. .3 ... .4 and another 2 computers who don`t have Internet connectios, they have "invisible IPs" (90.1.1.5 ... .6) and they are not connected on the internet. I want to share a connection, like 90.1.1.2 with one who does not have an internet connection. I wonder if this is possible. I was thinking to assign to another LAN card the IP 90.1.1.2 and connected to another swith, and to conect the other 2 computers on that switch. That LAN card I want to share into the network. That was my ideea. I think it is a difficult example, but this is the best I can do :) If you have another sollution to my problem, please help me

[erwin]

Hi Minute

Sounds like you are trying to use what are called External (Public) Ip addresses on your LAN where you should be using Internal (private) addresses. For a quick introduction to Public versus Private Ips and how WinGate uses them can I suggest you take a read of our knowledge base here:

http://support.qbik.com/index.php?_a=knowledgebase

You will need to number the machines on your LAN with private IP address such as 192.168.1.1, 192.168.1.2 etc (including the Adapter that connects the WinGate server to the LAN).

Once this is done you will then be able to set the Gateway and DNS entries on the clients network properties to the private Ip address(interface) of the WinGate server that connects it to the LAN.

The WinGate server will then use the External IP on the Wireless card that connects to the Internet to resolve Internet requests on behalf of the clients. This is the Network Address Translation (NAT) method of connection.

This way as Matt suggested earlier the Internet will only see on connection coming from the WinGate server rather then the client machines behind.

Hope this helps

Regards
Erwin

[minute]

I understand what you told me, this is not the problem I have.
I will explain it again. I want to have in my network Public IPs and Internal Ips. The public Ips are:
On the server 194.102.200.140 on wireless and 217.156.123.101 on LAN
On "clients" 217.156.123.102, 217.156.123.203. (visible, gw 217.156.123.101) and other 2 Internal Ips 217.156.123.104 and 217.156.123.106, to see the entire network
If I put another LAN card on the server I will assign the External IP 217.156.123.102, and that particulary IP I want to "share" with other 2 computers. That network card will be connected to a switch, and in that switch will be connected those 2 computers. If I do NAT in the way that you told me, all the computers will share the same IP (the wirekless card IP 194.102.200.140) and I don`t want that, because I have on the external IPs diferent limits (bandwith) and the smallest one is on the 194.102.200.140.
I want to know if this is possible, and how to do that in the program.
So this is what I want to do, to share the connection on a public IP with 2 computers, and to keep the connection without NAT with the other computer who has public IP
Thank you for your kindly help

[goff]

Hi, minute

was not so easy to get, what network architecture you've build, but it seems i know, what you mean.
So - at first - you may not have two different machines with same IP's on same network segment. Your idea to build two segments with extra NC in server and second switch is right, but it willn't work so as you want - you don't need to share IP between your machines, you shell share Internet connection of 217.156.123.102.
I would offer you to install wingate on a machine 217.156.123.102 and configure 217.156.123.104 and 217.156.123.106 to connect to internet throuth it. Of course, 217.156.123.102 has to be powered on all the time when 217.156.123.104 and 217.156.123.106 whants to go internet. wingate on 217.156.123.102 will path all request from clints to internet so, as they would be his own requests. Your ISP will see that connection comes from 217.156.123.102 and will not see real IP's of clients. So, basically it is possible.
Even more - 217.156.123.104 and 217.156.123.106 are public IP's and actually you shouldn't use it. You may set legal (privat, f.e. 192.168.123.104 and .106) IP's for your invisible clients and configure wingate on 217.156.123.102 to map request to 217.156.123.203 and 217.156.123.101, so that invisible clients may see others. If i'm not mistaken, you don't need a second card for 217.156.123.102, it should work pretty with only one NIC - i remeber, but not sure, XP may assign several IP's to only one NIC. I think, wingate has to see different IP's on one NIC as different interfaces.
Hope i understood you right and it helps. Anyway you may download trial version of wingate and try it out. I never had problems to uninstall it :-)
Goff