Problem with network

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Problem with network

Postby Radar » May 13 04 3:59 am

Hi,

I'm having problems with the wingate client computer connecting to the internet. This is what my setup looks like:

Wingate Server Machine
----------------------------
2 NICs
"Internet NIC", connects directly to the dsl modem. (169.254.102.239 is the local autoconfigured ip)
"LAN NIC", connects to a router (192.168.0.1)

DSL Router (192.168.0.2)
-------------
Can be setup as dynamic/static IP address or PPPoE.
Does not run a DHCP service.

Wingate Client Machine (192.168.0.5, gateway 169.254.102.239)
---------------------------
Connects to the router.
Is able to ping the router and the "LAN NIC" on the wingate server.


Do I need a switch in order to run wingate, or does wingate run fine through routers as well? What can be wrong with this setup? Do you need any more information to look into my problem?
Radar
 
Posts: 6
Joined: May 13 04 3:49 am

Postby MattP » May 13 04 4:02 pm

The 169.254.*.* address is the address that a NIC usually gets when it can't communicate with a DHCP server, it's the default address.

I'm a bit confused about your setup, you say your DSL Modem has an IP address 192.168.0.2 and the server connects to it over a NIC with IP address 169.254.102.239? This won't be working. The two NICs will need to be on the same subnet. You should probably set the NIC to a static IP address and set it manually on the same range as the modem.

Your internal NIC, the one that points to your router should ideally be on a different subnet to the external NIC in order to prevent routing confusion. You could change your LAN address range to 192.168.1.*, so the router would be 1.2, the internal NIC on the WinGate server would be 1.1 and the other pcs would be on the same subnet.

The client pcs should have their IP address on the same subnet as the WinGate servers' internal NIC, you should set their default gateway and DNS server IP address to be the internal NIC of the WinGate server, ie 192.168.1.1 (from above). You can now make a NAT connection from the client to the server.

I hope I've answered your questions,

Matt
MattP
Qbik Staff
 
Posts: 991
Joined: Sep 08 03 4:30 pm

Postby Radar » May 13 04 10:16 pm

To clear out on some of your confusion:

All NICs running on subnet mask 255.255.255.0

---------------
|dsl modem|
---------------
--|
--|
--|
------------------------------------------------------
|Internet NIC, ISP IP + autoconf. 169.254.*.*|
------------------------------------------------------
---------------------------
|LAN NIC, 192.168.0.1|
---------------------------
--|
--|
--|
-------------------------
|Router, 192.168.0.2|
-------------------------
--|
--|
--|
--------------
|Client PCs|
--------------


Going to try the setup you suggested a bit later today, cheers.
Radar
 
Posts: 6
Joined: May 13 04 3:49 am

Postby Radar » May 14 04 1:09 am

I just tried the setup you suggested, and at least I am making some progress. Here is my current setup:

"Internet NIC"
IP: 192.168.1.3
Subnet mask: 255.255.255.0

"LAN NIC"
IP: 192.168.1.2
Subnest mask: 255.255.255.0

Router
IP: 192.168.1.1
Subnest mask: 255.255.255.0

Client Machine:
IP: 192.168.1.4
Subnest mask: 255.255.255.0
Default gateway/Preferred DNS: 192.168.1.2

I still can't browse web pages on the client machine, but I noticed something interest in GateKeeper on the server machine:

Under "History" I can see the following entry:

Computer: 192.168.1.4
WG Username: Guest
Activity: DNS: A lookup "www.wingate.com"

Also, on the client machine running WinGate I can see the server machine.
Radar
 
Posts: 6
Joined: May 13 04 3:49 am

Postby Radar » May 14 04 1:24 am

Oh, sorry. On the Wingate client I noticed that IEXPLORE.exe had "Mixed Access", and put it to "Global Access". It now works (setting it to "global access" was hopefully the right thing to do).
Radar
 
Posts: 6
Joined: May 13 04 3:49 am

Postby MattP » May 14 04 10:57 am

so everything is working now? IExplore.exe should work as mixed access.

I think the way you have it set up now will cause some routing confusion. You have 192.168.1.* between your WinGate server and the router which connects to the internet. If you also have 192.168.1.* as the address range for you LAN then the OS won't know where to send the right traffic. Try changing the IP address range on your LAN to 192.168.2.*

Matt
MattP
Qbik Staff
 
Posts: 991
Joined: Sep 08 03 4:30 pm

Postby Radar » May 14 04 9:01 pm

What's the difference between global and mixed access? Because right now I got it set to global access on all clients and every application/game works fine.
Radar
 
Posts: 6
Joined: May 13 04 3:49 am

Postby genie » May 15 04 3:52 pm

Global mode means that the application is allowed to receive connections originated from the outside.
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am


Return to WinGate

Who is online

Users browsing this forum: No registered users and 5 guests

cron