Missing Network Interfaces

[HenriLemmers]

Hi there,

I've just made a transition from NT-4.0 to Server 2003 using Wingate 5.2.3. The server (DC) has 2 NIC's: 10.2.1.2 (mask 255.255.0.0) for the internal network, and 10.0.0.100 (mask 255.255.0.0) connected to my ADSL modem.
At first both NIC's showed up in Advanced Options, Network interfaces. However, after a couple of reinstalls my external NIC (10.0.0.100) vanished. Wingate seems to be working all the same, and the dialup VPN through this NIC is working.
I also wanted to install a dial-in RAS connection. This interface is not listed in Advanced options either, even when stopping wingate, connecting the dialup link en restarting the wingate service. The real problem is that the dialup line seems to be shielded by the firewall, therefore internal networking as well as Internet access is impossible. Even worse, disabling the firewall opens the dialup line to the internal network, but setting it to custom again results in a black screen and reboot of the server when a Internet Explorer attempt is made from the dialup line.

How can I make Wingate recognise these missing interfaces, to make wingate know that my RAS line is trusted?

Henri Lemmers

[adrien]

Hi

WinGate 5.2.3 enumerates available IP addresses when it starts up, so any addresses not currently assigned will not be shown. This is one of the reasons we designed Dynamic Binding in WinGate 6.0.

When you type "ipconfig /all" from the command prompt, do you see all the Ip addresses you would expect? What about if you restart WinGate?

The issue of trusting dial-in connections is also a bit of a tricky one for Wingate 5.2.3. We have done a lot of work in this area in WinGate 6.0 RC2 (due out on Monday).

By default, WinGate will determine how an interface should be treated by its IP address. So which range of addresses is being assigned to dialin users?

Also, these users should be able to connect to any proxy that you specify binds to "any interface".

Hope this helps.

Adrien

[HenriLemmers]

Hello Adrien,

Thanks for your answer. The answers:
With ipconfig/all all interfaces seem to show up:
10.2.1.2 local network
10.0.0.100 external interface to dsl-modem
10.2.1.41 internal RAS connection
80.60.124.115 VPN internet connection
These all show up in view traffic inside wingate, as well as 127.0.0.1
In network interfaces only
10.2.1.2
80.60.124.115 show up, as well as the two dial-up connections ZMC (ISDN not started), and ADSL-MXstream (internet connection).
A restart of the Wingate engine does not make a difference.

I don't know if it may have to do with a former install of the windows firewall and ENS which I disabled when installing Wingate. An odd thing may be the interface numbering by route print:
C:\Documents and Settings\Administrator>route print

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 c0 9f 34 79 89 ...... Intel(R) PRO/1000 MT Network Connection - Packet Scheduler Miniport
0x10003 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x10004 ...00 02 b3 eb f9 33 ...... Intel(R) PRO/100 S Server Adapter
0x60005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
The "missing interfaces" start with 0x1000, but I don't know the meaning, nor how to correct them.
The complete listing will be sent by e-mail.

I will be out for the next 2 weeks, but look forward to new suggestions.

Henri Lemmers

[HenriLemmers]

Hello Adrien,

Returned from the hollidays I installed Wingate 6.0.0.984 over my 5.2.3.
My interfaces problem seems to be over, they all show up although I had to switch my second adapter to external again to prevent connection problems. Even the dial in connection now came through as an internal connection as I hoped.

However, all my WRP (WGIC) connections were lost (no activity at all) and I had to switch to NAT which worked well. Also my 2003 server now gave 3 random reboots and one lockup within one day, maybe because of one client accessing a certain IE page by NAT, or another one starting up still not switched from WGIC.

As a result I removed Wingate 6.0.0, and performed a clean reinstall. The problem I now have will be described in a new thread: WGIC-Outlook problem.

For now thanks for solving the interfaces problem.
Henri