exported host - can't connect

[danbergan]

I'm using OpenVPN successfully with a few exported hosts on my network. I can ping and connect by remote desktop successfully to all those computers.

I just added a new computer and added it's IP address to the OpenVPN Exported Hosts (ip 192.168.100.32, netmask 255.255.255.255). However, I'm unable to ping or connect by windows remote desktop. Inside the network, I'm able to ping and connect with remote desktop (so, it doesn't appear to be an issue with windows firewall).

I have the untangle firewall set up to log (but allow) the windows remote desktop port, and I'm not seeing anything logged when I attempt to connect.

One final piece of information - when I try to traceroute to the newly exported host, I get:
Tracing route to 192.168.100.32 over a maximum of 30 hops

1 59 ms 66 ms 58 ms 172.16.0.1
2 * * * Request timed out.

172.168.0.1 is the untangle VPN. So, it is getting to the untangle box, but no further.

It looks like I have set this exported host up just like all the others, but maybe I've missed something... Does anyone have any ideas for me?

Thanks -
Dan

[sky-knight]

What version of Untangle... what version of windows is the client doing the connecting... does that client connect to other stuff?

[danbergan]

untangle 7.0.0

I'm trying to connect using Windows Vista Home Premium. I'm able to connect using remote desktop (through the VPN) to XP Pro and Server 2003 machines. I am now trying to connect to a client on Vista Business.

Dan

[sky-knight]

The only explanation has to be the windows firewall on the Vista Biz box...

[danbergan]

I was thinking the same thing so I turned the firewall off completely.

Also, I was able to connect by remote desktop from a computer within the internal network.

The one thing that really confuses me is that I never see the remote desktop connection logged in the untangle firewall - while the other connections I make do show up there.

Dan

[sky-knight]

Right but that VPN client can connect to other resources on the lan? This means the VPN is working correctly. The only possibilities are now on the host station in question.

Common issues here are windows firewall related, or the box has an incorrect default gateway.

[danbergan]

Thanks, Sky-Knight!

This was harder to track down than I expected. I had the Windows Firewall turned completely off, and I was able to connect by remote desktop from within the network, so I thought I was able to rule out firewall issues. BUT, there was some McAfee security program running that was blocking the connection coming from the VPN and not from the internal network.... SIGH...

Thanks again -
Dan

[sky-knight]

If I've said it once I've said it 1000 times....

1.) McAfee sucks
2.) Anything "Internet Security" sucks twice as hard

:P Glad you found it