Untangle isn't DNS server but OpenVPN needs to see internal network

[smclellan]

First off, Untangle is an excellent product. However, I already have a DHCP server and a DNS server on my network and do NOT want or need to change to allow Untangle to act as those servers. Untangle is set as a gateway with two WAN connections. I can connect to VPN using the distributed OpenVPN client on Windows XP. I can ping the IP addresses of the hosts that use the Untangle server as their gateway, but I cannot change the gateway on all the hosts to the Untangle server for various reasons. How can I access ALL the hosts on my internal network regardless of their gateway?

[dmorris]

smclellan, welcome to the forums.

just turn of DHCP and DNS inside config->networking if you have DNS and DHCP servers.
(or just turn off DHCP - the DNS server won't do any harm.)

For hosts not using untangle as their gateway you can't talk to them via VPN over untangle because their reply packets won't go to untangle so untangle can't route them back to the remote client. you may be able to add a route on your other gateway to try and get the packets destined for the openvpn address pool over to the untangle gateway.

hope that helps!

[smclellan]

The DHCP and DNS are turned off in Untangle. I will try to set a route on the other gateways for VPN traffic to come back out of the Untangle gateway.

[smclellan]

Well played dmorris... well played. That was just what the doctor ordered. I set a static route for 172.16.0.0/24 (the default VPN addresses that Untangle OpenVPN assigns) to point back to the internal network on all my gateways and now everything seems to work pretty well.

[dmorris]

nice!

[nabicom]

Not sure if it relates to above but I have a similar problem as follows:
I have a site to site vpn between 2 untangle servers site 1(host) and site 2(client).
- Site 2 can connect to all workstations on site 1. But when connecting to a windows 2003 server (not domain, just application server) cannot even ping from site 2.
- Curious though is that from site 2 server can ping up to the windows server 2003 but from a client connected to site 2 server cannot. gateway of windows is site 1 untangle server.

Any ideas?

[BryanFry]

Originally Posted by smclellan

Well played dmorris... well played. That was just what the doctor ordered. I set a static route for 172.16.0.0/24 (the default VPN addresses that Untangle OpenVPN assigns) to point back to the internal network on all my gateways and now everything seems to work pretty well.

I am having a similar problem, but setting the static route doesn't seem to fix the problem (although I was hopeful). Any other suggestions?

[WebFooL]

Hi BryanFry and welcome to the forum,

Can you do a tracert from a client on the networks to a VPN ip ?
And then from a VPN Client a tracert to a Inside resource.

And post a simple network layout so that we can help you.

And it might be good to start your own thread.

[BryanFry]

This thread perfectly describes the problem we are having -- we can access everything inside the network via IP, but not by name.

Basic network layout:

                                   Internet
                                        |
                                   UT Box  (192.168.10.1 and 192.168.11.1)
                                       /\
                                      /  \
                                     /    \
                         Win2000Server    Win2003Server
                       192.168.11.2            192.168.10.2
                            /                           \
                           /                             \
      About 25 computers                          About 25 computers
     192.168.11.X                                          192.168.10.X

Both of the servers run their own DHCP/DNS services. The tracert does what I would expect it to do:

From outside (172.16.0.5) to inside (192.168.10.20):

172.16.0.1
192.168.10.20

From inside (192.168.10.74) to outside (172.16.0.5):

192.168.10.1
172.16.0.5

Thanks for your prompt help!

[WebFooL]

Then the route workt.
Have you exported the DNS and then enabled DNS override?
And do a check from the DNS server and see if that can tracert to a VPN ip.