No Dialing on request OR no internet from WinGate machine

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

Moderator: Qbik Staff

No Dialing on request OR no internet from WinGate machine

Postby Ronnay » Jun 22 05 3:04 pm

I'm still evaluatng WinGate 6.0.4.

I've read topic http://forums.qbik.com/viewtopic.php?t=3505 and my problem is almost the same:

WinGate runs on a Windows 2000 professional (workstation) machine. There is no AD running and no DNS server (except WinGate).
This machine has two 3Com Ethernet NIC's. One is connected to the internal network, the other is connected to an ISDN/ADSL modem (not router). This modem can only connect to the internet by a DialUp connection.

IP-config /all info:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : oilmillfiles
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter 3COM to ADSL:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC (3C905-TX)
Physical Address. . . . . . . . . : 00-60-08-78-16-D7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.160.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

Ethernet adapter 3COM to Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC (3C905-TX) #2
Physical Address. . . . . . . . . : 00-60-08-78-F1-68
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :


Running WinGate with these NIC settings results in automatically dialing whenever one of the 2 clients (Windows XP home) tries to access the internet. When connected to the internet there is a third network device shown in ipconfig:

PPP adapter HCC-Net:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.xxx.yyy.zzz
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 62.xxx.yyy.zzz
DNS Servers . . . . . . . . . . . : 62.251.0.6
62.251.0.7
NetBIOS over Tcpip. . . . . . . . : Disabled


And all seems to work fine.
HOWEVER:
There is no internet access possible from the WinGate machine. This is a problem, because the running antivirus program is not able to retrieve updates. Also Windows update is not running for the same reason.
On the two clients there are no gateway or proxy settings, they get their IP-addresses automatically from the WinGate's DHCP server, including the WinGate's internal NIC IP-address as the default gateway and as DNS server address. I'm not using the Wingate Client.
On the WinGate machine there are no proxy settings in IE and no WinGate client.

To "solve" this problem I've assigned a gateway to the NIC connected with the ADSL modem (IP-address of the modem) as mentioned in a .gif file somewhere on your server. (This .gif shows (top to bottom): Internet cloud; Router with 2 Interface cards; WinGate Server with 2 Interface cards; Lan Hub; 2 WinGate Clients.)
Now the NIC shows like this:

Ethernet adapter 3COM to ADSL:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC (3C905-TX)
Physical Address. . . . . . . . . : 00-60-08-78-16-D7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.160.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.160.2
DNS Servers . . . . . . . . . . . :


Now all 3 machines (2 clients and WinGate machine) can access the internet, whenever the connection is established. However the connection has to be made manually by pressing the "Dial" button in the Dialer properties window. Rebooting the WinGate machine results in a running WinGate engine but no internet connection and the dialup connection is not triggered by a NAT/DNS requests.

(Part of) WinGateConfix.txt:
3.01 ---------------------------------------------
3.02 Licence details
3.03 ---------------------------------------------
3.04 License Key 1
3.05 Version: WinGate 6 Enterprise 250+ concurrent users
3.06 Expiry: 03/Jul/2005
3.07
4.01 ---------------------------------------------
4.02 Dialer information
4.03 ---------------------------------------------
4.04 Dialer is enabled
4.05 Profiles:
4.06 HCC-Net (Enabled) 3 retries
4.07 Overall retries: 5
4.08
5.01 ---------------------------------------------
5.02 Network Interfaces
5.03 ---------------------------------------------
5.04 HCC-Net (VPN) external
5.05 3COM to ADSL (Ethernet) external
5.06 3COM to Netwerk (Ethernet) internal
5.07 Internal loopback interface for 127.0.0 network (Loopback)
5.08
.....
7.01 ---------------------------------------------
7.02 System Route Table
7.03 ---------------------------------------------
7.04 Current Route Table:
7.05 ---------------------------------------------
7.06 Network Mask Gateway Interface Metric
7.07 0.0.0.0 0.0.0.0 62.251.86.132 62.251.86.132 1
7.08 62.251.86.132 255.255.255.255 127.0.0.1 127.0.0.1 1
7.09 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
7.10 127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
7.11 192.168.16.0 255.255.255.0 192.168.16.1 192.168.16.1 1
7.12 192.168.16.1 255.255.255.255 127.0.0.1 127.0.0.1 1
7.13 192.168.160.0 255.255.255.0 192.168.160.1 192.168.160.1 1
7.14 192.168.160.1 255.255.255.255 127.0.0.1 127.0.0.1 1
7.15 224.0.0.0 240.0.0.0 192.168.16.1 192.168.16.1 1
7.16 224.0.0.0 240.0.0.0 192.168.160.1 192.168.160.1 1
7.17 255.255.255.255 255.255.255.255 192.168.16.1 192.168.16.1 1
7.18 255.255.255.255 255.255.255.255 192.168.160.1 192.168.160.1 1
7.19
8.01 ---------------------------------------------
8.02 Enhanced Network Support
8.03 ---------------------------------------------
8.04 Enhanced Network Support: Qbik NDIS Hook 6.0 - Installed and active
8.05 Driver: Enabled
8.06 NAT: Enabled
8.07 Router: Enabled
8.08 Firewall level: Custom
8.09
8.10 Firewall
8.11 ---------------------------------------------
8.12 Disable network name broadcasts to the Internet: Enabled
8.13 Allow users to ping this machine locally: Enabled
8.14 Allow users to ping this machine from the Internet: Disabled
8.15 Discard spoofed packets: Enabled
8.16
8.17 Routing
8.18 ---------------------------------------------
8.19 Multiple default routes: Enabled
8.20 Relay UDP broadcast packets: Enabled


The gateway IP-address on the NIC to ADSL is mentioned in the Network Connection frame on the Network tab in WinGate. Sometimes once, sometimes twice (comma delimited).

I allready have deleted and recreated the connectoid twice (as stated in http://forums.qbik.com/viewtopic.php?t=3434), but the problem still remains.
Setting 3COM to ADSL as an internal connection results in no internet at all (probably the same problem as http://forums.qbik.com/viewtopic.php?t=3625)

How to solve this problem?
I'm almost running out of evaluation time. I only can test in the evening or weekends because I have a full time job and I'm using WinGate to share internet at home.
Is there more information available about WinGate in a readable form like the Mail_Server_6_Scenarios_and_Configurations.pdf from Neil Gooden? That document was very helpfull.
Evaluating on basis of trial and error is very time consuming. I'm not sure if I should use Transparent Redirection and/or Transparent Proxy settings in my situation.

Can somebody help me with these questions?

Greetings,
Ronnay
Ronnay
 
Posts: 9
Joined: Jun 06 05 4:42 am

Postby MattP » Jun 23 05 2:03 pm

Hi Ronnay,

Does the ADSL modem show up in the dialer profiles in WinGate? If it does then please check to make sure it is enabled for use by WinGate and that the check box "connect as required using the connection list" is also checked.
MattP
Qbik Staff
 
Posts: 991
Joined: Sep 08 03 4:30 pm

Postby jamesc » Jun 23 05 6:17 pm

Does using googles IP address from one of the client machines initiate a connection?

http://64.233.187.104 (in your web browser / internet explorer?)
jamesc
Qbik Staff
 
Posts: 928
Joined: Apr 04 05 2:04 pm
Location: Auckland, New Zealand

Postby Ronnay » Jun 23 05 8:59 pm

MattP wrote:Does the ADSL modem show up in the dialer profiles in WinGate? If it does then please check to make sure it is enabled for use by WinGate and that the check box "connect as required using the connection list" is also checked.

Yes it is shown and yes it is enabled. There is however no automatic DialUp on NAT activity from the clients.

jamesc wrote:Does using googles IP address from one of the client machines initiate a connection?

If the DialUp is not established entering www.google.com nor http://64.233.187.104 nor http://66.102.9.104 in my web browser triggers the DialUp process in spite of the activity shown in GateKeeper.

Removing the IP-address in the NIC to ADSL properties is detected by the running GateKeeper and empties the column Gateway.
In this case DialUp is working properly, but there is no internet access possible from the WinGate machine.



Testing all kind of settings resulted in an error message.
I did the following:
- The WinGate machine is booted. The NIC to ADSL has no gateway IP-address. GateKeeper is started and shows no gateway IP for the NIC to ADSL. The DialUp is NOT established.
- I enter the gateway IP-address in the properties screen of the NIC to ADSL. After closing the last properties window GateKeeper detects the change and shows that IP-address in the gateway column.
- Now I manualy establish the DialUp connection by pressing the Dial button in the Dialer properties screen. As soon as the connection is established the ISP IP-address is shown in GateKeeper and the gateway IP-address for the NIC to ADSL is shown twice.
- Now I remove the gateway IP-address in the properties window of the NIC to ADSL. After closing the last properties window GateKeeper detects the change and removes only one gateway address. So there is still one showing. The DialUp connection stays connected.
- I try to access the internet from one of the clients, resulting in the error message on the WinGate machine. The DialUp connection stays connected. Error message:
Title bar: Windows - Fatal Application Exit
Message: WinRoute Driver: ProtocolReceiveHandler: Unable to find WANARP adapter


I have to go to my work right now. But I shall try to repeat this process this evening to see if I can reproduce the error.

Ronnay
Ronnay
 
Posts: 9
Joined: Jun 06 05 4:42 am

Postby genie » Jun 23 05 10:27 pm

Hold on - do you have Winroute installed as well?
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby Ronnay » Jun 24 05 11:22 am

genie wrote:Hold on - do you have Winroute installed as well?

No.
I had Kerio WinRoute Firewall 6 on my machine to try.
Nice program. But much to expensive for home use. 400 USD, 500 Euro incl tax. So I've removed the complete installation of Kerio WinRoute Firewall and thus the error can't be genereted by WinRoute.exe from Kerio. There is no service in administrative tools/services that uses a winroute.exe and searching all my drives on the WinGate machine reveales no winroute.exe.

Ronnay
Ronnay
 
Posts: 9
Joined: Jun 06 05 4:42 am

Postby genie » Jun 24 05 11:26 am

This message: Message: WinRoute Driver: ProtocolReceiveHandler: Unable to find WANARP adapter

could be generated only by Winroute - probably the de-installation process left the driver behind. It might be the one cluttering the system.
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 1 guest