Page 1 of 1

Openvpn connection to server but mail fails to open

Posted: Fri Sep 24, 2010 11:45 am
by jerry
Hi,
I am having problems opening mail once the Openvpn connection is created. The mail client fails to connect with the server. I need to know how or what to change on the Openvpn server to get this to work?

-- background material--
The company has a non Openvpn firewall setup. I have installed a rule in it that will let all Openvpn traffic through the firewall. The users do connect with the Openvpn server and a tunnel is setup. "All this is due to Windows 7 64-bit and Linux users connecting from home."
--
When the user tries to open the mail client it is failing to connect to the mail host that is also behind the firewall.

thanks for your help!

Re: Openvpn connection to server but mail fails to open

Posted: Tue Sep 28, 2010 4:10 am
by george
Can a connected client ping the mail server by FQDN or IP address?

Re: Openvpn connection to server but mail fails to open

Posted: Tue Sep 28, 2010 8:14 am
by jerry
Yes, a connected client can ping the ip address of the mail host.

I have asked the client if he was using the MS firewall, and if he is to turn it off. But I have not heard from the client.

thanks

Re: Openvpn connection to server but mail fails to open

Posted: Thu Sep 30, 2010 4:54 am
by george
Ensure his mail client is using the IP address and not the FQDN, if the client is using the FQDN then it might be as simple as switching the mail client settings to use the IP.

Re: Openvpn connection to server but mail fails to open

Posted: Thu Oct 07, 2010 7:23 am
by jerry
I think I figured it out. I changed a number of rules on the firewall regarding email so that they would log. Turned out that the user needed to be added to one of the groups within the firewall. :)


thanks for all the help.

Re: Openvpn connection to server but mail fails to open

Posted: Fri Oct 08, 2010 11:54 am
by Douglas
jerry wrote:I think I figured it out. I changed a number of rules on the firewall regarding email so that they would log. Turned out that the user needed to be added to one of the groups within the firewall. :)


thanks for all the help.
Glad to hear its resolved! :)