Can't ping anything on my network from remote client

[dmorris]

you could verify this using tcpdump (or the packet test) on untangle to see if the ping packets are reaching untangle.

[rsn]

you could verify this using tcpdump (or the packet test) on untangle to see if the ping packets are reaching untangle.

It looks like tracert already shows that nothing is making it to my untangle network as the first hop is the gateway on my client's local network.

[rsn]

Ok, so the problem exists entirely on your client. (since your client is making the routing decision).

Figure out why your client is deleting the route. OpenVPN has a nice log file somewhere in it's directory structure. Is the tunnel going down?

And yeah, sorry, I misread your IP as 174.24... my bad.

If the tunnel does go down, it should automatically come back up. That log file will tell you more.

This is all I see in my log file. I'm not sure which of these messages, if any, indicates a problem:

Wed Oct 06 09:17:41 2010 OpenVPN 2.1.1 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Dec 11 2009
Wed Oct 06 09:17:41 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Wed Oct 06 09:17:41 2010 LZO compression initialized
Wed Oct 06 09:17:41 2010 UDPv4 link local: [undef]
Wed Oct 06 09:17:41 2010 UDPv4 link remote: xx.xx.xxx.xxx:1194
Wed Oct 06 09:17:42 2010 [server.does.not.exists] Peer Connection Initiated with 69.21.227.160:1194
Wed Oct 06 09:17:44 2010 TAP-WIN32 device [{407535D5-CB87-4D36-95E6-A1E46EA475BC}] opened: \\.\Global\{407535D5-CB87-4D36-95E6-A1E46EA475BC}.tap
Wed Oct 06 09:17:44 2010 Notified TAP-Win32 driver to set a DHCP IP/netmask of 192.168.51.5/255.255.255.252 on interface {407535D5-CB87-4D36-95E6-A1E46EA475BC} [DHCP-serv: 192.168.51.6, lease-time: 31536000]
Wed Oct 06 09:17:44 2010 Successful ARP Flush on interface [524292] {407535D5-CB87-4D36-95E6-A1E46EA475BC}
Wed Oct 06 09:17:49 2010 Initialization Sequence Completed

[mrunkel]

That's normal. So it's something else that is doing this. I don't know what you have running on your PC, but something is causing that route to be deleted.

[rsn]

That's normal. So it's something else that is doing this. I don't know what you have running on your PC, but something is causing that route to be deleted.

Hmm, I don't know what that would be. I was afraid there would be complications w/ OpenVPN. I was previously using PPTP and had no issues on any of these client machines.

What are possible candidates for the cause of this problem? I'm not sure what would cause this to happen?

[raditude]

What happens if you manually add the route (routeadd) from the CLI after you connect your VPN? Does it work then? Or does something remove the route again after a short period?

[rsn]

What happens if you manually add the route (routeadd) from the CLI after you connect your VPN? Does it work then? Or does something remove the route again after a short period?

Hmm, interesting idea. What is a CLI? I'm not familiar w/ that acronym.

Also, what specific route needs to be added? That is, what would the route look like in the routing table?

[raditude]

CLI = Command Line Interface

Here is MS info on adding a route in XP: http://www.microsoft.com/resources/d....mspx?mfr=true

I would not do the -p switch to start with as you want this to be flushed when you reboot.

[rsn]

CLI = Command Line Interface

Here is MS info on adding a route in XP: http://www.microsoft.com/resources/d....mspx?mfr=true

I would not do the -p switch to start with as you want this to be flushed when you reboot.

I'm not 100% sure what I am routing, specifically.

Here is my routing table, currently. What needs to change, specifically, and in what way?

Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      172.24.96.2   172.24.97.163       10
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      172.24.96.0    255.255.254.0    172.24.97.163   172.24.97.163       10
    172.24.97.163  255.255.255.255        127.0.0.1       127.0.0.1       10
    172.24.100.27  255.255.255.255      172.24.96.1   172.24.97.163       1
    172.24.100.28  255.255.255.255      172.24.96.1   172.24.97.163       1
    172.24.101.28  255.255.255.255      172.24.96.1   172.24.97.163       1
   172.24.255.255  255.255.255.255    172.24.97.163   172.24.97.163       10
     192.168.51.4  255.255.255.252     192.168.51.5    192.168.51.5       30
     192.168.51.5  255.255.255.255        127.0.0.1       127.0.0.1       30
   192.168.51.255  255.255.255.255     192.168.51.5    192.168.51.5       30
        224.0.0.0        240.0.0.0    172.24.97.163   172.24.97.163       10
        224.0.0.0        240.0.0.0     192.168.51.5    192.168.51.5       30
  255.255.255.255  255.255.255.255    172.24.97.163   172.24.97.163       1
  255.255.255.255  255.255.255.255     192.168.51.5    192.168.51.5       1

[rsn]

CLI = Command Line Interface

Here is MS info on adding a route in XP: http://www.microsoft.com/resources/d....mspx?mfr=true

I would not do the -p switch to start with as you want this to be flushed when you reboot.

That worked, I can now ping IPs on my Untangle network. However, I can't ping by hostname. Any idea why that might be? Normally, when the connection "works" I can also ping by hostname.

Thanks for your suggestion. Any idea why I needed to add this route manually?