Allow port 1434 throught Openvpn - Page 2

sky-knight · 02-02-2012, 07:52 AM

Untangle in router or bridge mode? Assuming Untangle is in router mode, is the UPS server using Untangle as its default gateway?

If Untangle is in bridge mode, did you configure a static route for the OpenVPN Address pool in your gateway?

Jcook_5xdata · 02-02-2012, 08:46 AM

It is in router mode I am not using untangle DHCP server and overing DNS (push domain DNS server). Yes the UPS server is set to use Untangle as gateway. I thing I found was in the Bypass Rules > Bypass DNS Traffic is UNCHECK is that correct?

joec2000 · 02-02-2012, 08:55 AM

Make sure you're using the latest version of the OpenVPN client (2.2.2 as of this writing). I sometimes work from home and last week, 2.2.1 would not connect to the SQL servers at work. I found an internet post somewhere stating that upgrading to 2.2.2 fixed it for them; well, 2.2.2 fixed it for me as well.

No configuration changes were made on the Untangle OpenVPN server or on the OpenVPN client prior to the 2.2.2 upgrade.

- Joe

Jcook_5xdata · 02-02-2012, 09:57 AM

The client was using 1.0.3 I did update him to 2.2.2, he reporting faster speeds but UPS still fails. with the same error.

sky-knight · 02-02-2012, 10:24 AM

SSH to Untangle

tcpdump -i eth1 port 1434

Have client open software, watch the packets fly. If you see stuff exiting eth1 (default internal interface) Untangle did its job.

Also, MSSQL operates over the TCP protocol with a default port configuration of 1433.

http://support.microsoft.com/kb/287932

Changing the port is irrelevant, but the protocol is a huge change. And I suspect due to that you may have been formatting rules for the wrong protocol.

Is this the only user of the software attempting this process? Do you have any other users of the software that aren't on the local ip network? If all other users are on the IP network you may have an issue with your TCP/IP settings for the MSSQL server. Everyone on the local network can fall back to named pipes and appear to work normally when in fact they are broken.

If the server is on Windows Server 2008 you may have some Windows Firewall work to do.

All the more reason to read the output of TCPDump. If you see packets from the VPN user, exiting the Internal interface, and you don't see a response, your issue is on that server, not Untangle.

Stop guessing, start troubleshooting!

orange · 02-24-2012, 06:43 AM

any resolution to this? I'm having the same issue. Cant connect to a program through VPN but works just fine on the local network. Program uses SQL :/

jcoffin · 02-24-2012, 06:53 AM

Quote:

Originally Posted by orange

any resolution to this? I'm having the same issue. Cant connect to a program through VPN but works just fine on the local network. Program uses SQL :/

This is probably a configuration issue. I suggest creating a new thread for you situation and add more information about your configuration. With VPN problems, it's best to see if the packet are going through the right interface with tcpdump on the Untangle terminal.

orange · 02-24-2012, 08:04 AM

I'm pretty sure its the same issue. I can connect the VPN and do everything (RDP, network shares, etc) but cant access SQL. For anyone that finds this thread like I did, upgrading openvpn to 2.2.2 fixed it for me!

02-02-2012, 07:52 AM	#11 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,460	Untangle in router or bridge mode? Assuming Untangle is in router mode, is the UPS server using Untangle as its default gateway? If Untangle is in bridge mode, did you configure a static route for the OpenVPN Address pool in your gateway? __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879

02-02-2012, 10:24 AM	#15 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,460	SSH to Untangle tcpdump -i eth1 port 1434 Have client open software, watch the packets fly. If you see stuff exiting eth1 (default internal interface) Untangle did its job. Also, MSSQL operates over the TCP protocol with a default port configuration of 1433. http://support.microsoft.com/kb/287932 Changing the port is irrelevant, but the protocol is a huge change. And I suspect due to that you may have been formatting rules for the wrong protocol. Is this the only user of the software attempting this process? Do you have any other users of the software that aren't on the local ip network? If all other users are on the IP network you may have an issue with your TCP/IP settings for the MSSQL server. Everyone on the local network can fall back to named pipes and appear to work normally when in fact they are broken. If the server is on Windows Server 2008 you may have some Windows Firewall work to do. All the more reason to read the output of TCPDump. If you see packets from the VPN user, exiting the Internal interface, and you don't see a response, your issue is on that server, not Untangle. Stop guessing, start troubleshooting! __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879

Protect

Filter

Perform

Connect

Manage

Add-Ons

02-02-2012, 08:46 AM	#12 (permalink)
Jcook_5xdata Newbie Join Date: Jan 2012 Posts: 7	It is in router mode I am not using untangle DHCP server and overing DNS (push domain DNS server). Yes the UPS server is set to use Untangle as gateway. I thing I found was in the Bypass Rules > Bypass DNS Traffic is UNCHECK is that correct?

02-02-2012, 08:55 AM	#13 (permalink)
joec2000 Untangler Join Date: Jun 2010 Posts: 36	Make sure you're using the latest version of the OpenVPN client (2.2.2 as of this writing). I sometimes work from home and last week, 2.2.1 would not connect to the SQL servers at work. I found an internet post somewhere stating that upgrading to 2.2.2 fixed it for them; well, 2.2.2 fixed it for me as well. No configuration changes were made on the Untangle OpenVPN server or on the OpenVPN client prior to the 2.2.2 upgrade. - Joe

02-02-2012, 09:57 AM	#14 (permalink)
Jcook_5xdata Newbie Join Date: Jan 2012 Posts: 7	The client was using 1.0.3 I did update him to 2.2.2, he reporting faster speeds but UPS still fails. with the same error.

02-24-2012, 06:43 AM	#16 (permalink)
orange Untangler Join Date: Oct 2008 Posts: 84	any resolution to this? I'm having the same issue. Cant connect to a program through VPN but works just fine on the local network. Program uses SQL :/

02-24-2012, 08:04 AM	#18 (permalink)
orange Untangler Join Date: Oct 2008 Posts: 84	I'm pretty sure its the same issue. I can connect the VPN and do everything (RDP, network shares, etc) but cant access SQL. For anyone that finds this thread like I did, upgrading openvpn to 2.2.2 fixed it for me!