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

NAT not working in wingate 604

Sep 27 05 4:35 am

I setup WG604 with ENS enabled, but can't get NAT working
everything works fine on server
clients are configured by dhcp
dns is working fine on clients
pinging url from clients returns ipaddress, but requests time out
connecting trough wwwproxy works fine
interfaces are correctly identified by WG , but external interface has status unknown
I checked all the bindings and they look right to me.
The network used to work fine on ICS (Now uninstalled)

This is the server (Win98se) configuration:
Windows 98 IP Configuration
Host Name . . . . . . . . . : B2B.xx.nl
DNS Servers . . . . . . . . : 194.xx.xx.xx , 194.xx.xx.xx
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :
Description . . . . . . . . : HP 10/100TX PCI Ethernet Driver
Physical Address. . . . . . : 00-A0-xx-xx-xx-xx
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 192.168.1.200
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . :
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

1 Ethernet adapter :
Description . . . . . . . . : HP 10/100TX PCI Ethernet Driver
Physical Address. . . . . . : 00-A0-xx-xx-xx-xx
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 82.xx.xx.xx
Subnet Mask . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . : 82.xx.xx.1
DHCP Server . . . . . . . . : 212.xx.xx.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 09 26 05 16:25:21
Lease Expires . . . . . . . : 09 26 05 17:25:21

This is one of the clients (XP Pro sp2) configuration:
Windows IP Configuration
Host Name . . . . . . . . . . . . : b2a
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810X Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-01-xx-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.200
DHCP Server . . . . . . . . . . . : 192.168.1.200
DNS Servers . . . . . . . . . . . : 192.168.1.200
Lease Obtained. . . . . . . . . . : Monday, September 26, 2005 2:44:00 PM
Lease Expires . . . . . . . . . . : Friday, November 25, 2005 2:44:00 PM

This is the route table of the server:
Code:
Network Address Netmask        Gateway Address      Interface      Metric
  Network Address          Netmask  Gateway Address        Interface  Metric
          0.0.0.0          0.0.0.0       82.xx.xx.1     82.xx.xx.134       1
       82.xx.xx.0    255.255.254.0     82.xx.xx.134     82.xx.xx.134       1
     82.xx.xx.134  255.255.255.255        127.0.0.1        127.0.0.1       1
   82.255.255.255  255.255.255.255     82.xx.xx.134     82.xx.xx.134       1
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1       1
      192.168.1.0    255.255.255.0    192.168.1.200    192.168.1.200       1
    192.168.1.200  255.255.255.255        127.0.0.1        127.0.0.1       1
    192.168.1.255  255.255.255.255    192.168.1.200    192.168.1.200       1
        224.0.0.0        224.0.0.0     82.xx.xx.134     82.xx.xx.134       1
        224.0.0.0        224.0.0.0    192.168.1.200    192.168.1.200       1
  255.255.255.255  255.255.255.255    192.168.1.200    192.168.1.200       1


Any ideas?

Sep 27 05 11:44 am

Hi

In order for NAT to work, the interfaces in your system must be recognised by WinGate to be the correct 'type' e.g. internal/external or DMZ.

By default WinGate will assume what type of adapter an interface is by its IP address, but for various reasons, sometimes you need to override the automatic settings.

In GateKeeper, go to the network tab. Down the bottom you will see all your adapters. Check the usage column. The adapter connected to your LAN needs to be "internal", and the one connected to your Internet connection needs to be "external".

Double click on an adapter in GateKeeper to change its settings.

regards

Adrien

Re: NAT not working in wingate 604

Sep 28 05 9:47 am

bbuggy wrote:interfaces are correctly identified by WG , but external interface has status unknown


Wingate guessed righ :)
I don't know why the status of my external interface is unknown.
It is configured by my isp's dhcp, working fine and the card is identical to my local card.
Both cards are HP Netserver 10/100TX PCI Lan Adapters.

I can't find any other clues, but this is the first time i'm trying wingate so i might have missed something.

Sep 28 05 10:26 am

There's another Strange thing.
I just saw that WG uses 2 different names for my 2 identical interfaces.

External

In the network tab:
Name: HP 10/100TX PCI Ethernet Driver
Device Name: HP 10/100TX PCI Ethernet Driver

In the dynamic binding policy window:
HP 10/100TX PCI Ethernet Driver(HP 10/100TX PCI Ethernet Driver)

Internal

In the network tab:
Name: HP Netserver 10/100TX PCI Lan Adapter
Device Name: HP Netserver 10/100TX PCI Lan Adapter

In the dynamic binding policy window:
HP Netserver 10/100TX PCI Lan Adapter(HP Netserver 10/100TX PCI Lan Adapter)

In Windows device manager both interfaces apear as "HP Netserver 10/100TX PCI Lan Adapter"
and in ipconfig as "HP 10/100TX PCI Ethernet Driver"

Can it be that wingate is confused here?
I am !

Sep 28 05 11:29 pm

A few passing comments:

1. How did you stop ICS?
2. Do you have any firewalls or security suites installed? Have you tried disabling them for the sake of testing?
3. Have you ever had any other NAT software installed on that computer?

Sep 29 05 12:29 am

Hi

On OSes earlier than Win2000, the OS doesn't query network cards as to their status - that's why the adapter status shows up as unknown.

If you unplugged the network cable however, WinGate does then get an update. I would just ignore this "unknown" - it is normal on win98SE

Adrien

Sep 30 05 9:20 am

jamesc wrote:A few passing comments:

1. How did you stop ICS?
2. Do you have any firewalls or security suites installed? Have you tried disabling them for the sake of testing?
3. Have you ever had any other NAT software installed on that computer?


Hi James

I made a fresh install of win98se with ICS enabled and all essential windows updates and Norton AV 2003 installed on an AMD K6II 550 with 320 MB ram and tested the network.
Everything was fine.
I uninstalled ICS using windows setup (add remove programs cpl) and installed wingate



Hi Adrien
Thanks for clearing up the status issue.
Post a reply