Wingate not sending DNS to client with DHCP

[alyork]

Hi.

Maybe I'm missing something here.

My 3rd Winproxy to Wingate conversion. We were using Winproxy's DHCP and DNS. So no problem I thinks and uses Wigate's DNS and DHCP. After much hair tearing I finally noticed that the client was getting the IP and gateway IP addresses OK by no DNS. So they couldn't connect properly.

------------------------

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

c:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : maybe
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-14-2A-14-F7-40
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 90.0.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 90.0.0.1
DHCP Server . . . . . . . . . . . : 90.0.0.1
Lease Obtained. . . . . . . . . . : June 14, 2008 18:02:49
Lease Expires . . . . . . . . . . : August 13, 2008 18:02:49


-------------------

Ok. So to test , I hard code the IP address, gateway and dns in the network adapter properties on the client and it all works.

------------------

c:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : maybe
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-14-2A-14-F7-40
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 90.0.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 90.0.0.1
DNS Servers . . . . . . . . . . . : 90.0.0.1

c:\>

-----------------

Now that is OK for my test client but not OK for the rest of the networked clients.

The question is, what do I need to do to Wingate to have the DNS server work?

Thanks - Al

[Nev]

Hi,

The public IP range in your network could be a fault.

Here in Australia that Server IP you have chosen is accessible like this so that could cause network lookup conflicts.

Pinging 90.0.0.1 with 32 bytes of data:

Reply from 90.0.0.1: bytes=32 time=488ms TTL=229
Reply from 90.0.0.1: bytes=32 time=471ms TTL=229
Reply from 90.0.0.1: bytes=32 time=480ms TTL=229
Reply from 90.0.0.1: bytes=32 time=471ms TTL=229

Ping statistics for 90.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 471ms, Maximum = 488ms, Average = 477ms

Drive_C:\>

Can you try another network subnet for the Internal circuit such as Class A 10.0.0.x for example.

[alyork]

Winproxy recommended 90.0.0.1 for years and just recently has acknowledged the other ip address ranges to be used.

If the network is behind Wingate, why should it matter what IP address the internal adapter is using?

Converting to another subnet isn't going to be practical in some cases as there is a combination of DHCP and static IP addresses scattered throughout the LAN.

The other thing I've noted is there is no problem with the DNS when we use the servers DNS instead of Wingate's.

I'm sure we are doing something wrong, just not quite sure what as we are still going through the Wingate learning curve.

- Al

[logan]

If the network is behind Wingate, why should it matter what IP address the internal adapter is using?

There are 2 main reasons why you shouldn't use a public IP range for a private network. The first being that WinGate will detect the IP as a public IP and mark the adaptor as an external internet facing adaptor. This means the firewall will be raised and no services will be bound to that adaptor after installation. This can be overcome by manually setting the adaptor as internal.

The second reason is that your network will not be able to access any servers on the internet that use an IP in the 90.x.x.x range, because your computers will think these servers can be accessed locally when they must be accessed through the internet gateway. In this case, there are 16,581,375 hosts that will be inaccessible by your network, or 1/254~ of the internet. This cannot be overcome as easily as the first reason, so you must change your local network to a private IP range (that isn't used by any internet servers) to reobtain access to this IP range on the internet.

You can continue using the 90.x.x.x IP range if you wish, as long as you understand and are satisfied with the adverse effects of using a public IP range for a private network.


In regards to DNS assignment not working through WinGate's DHCP server, you can change the DHCP server from "fully automatic" to "manual" and adjust the DNS DHCP option yourself.

- GateKeeper -> System -> DHCP Service -> DHCP Mode -> Set the mode to Manual

- GateKeeper -> System -> DHCP Service -> DHCP Settings
- Double click on the DHCP Scope
- Click Options
- Add "DNS server" to the options in use if it isn't already added
- Double click on "DNS server" in the right hand pane
- Add your DNS server IP address(s) to the list and click OK
- OK your way out of the DHCP settings