SQL Port 1433 Workaround

[Powerhouse]

I know that 1433 is blocked on SB. I have been able to connect from my desktop SQLEM to my SQL server on SB.

But, now I have an application that requires connecting to a server that uses 1433 as the default port.

Normally, I get around this problem by using my computer as a intermediary. But since the application uses ASP to fire a script that updates a table on the server use 1433, it fails.

I have spoken to the admin of the other server, but he said that he cannot open another port on his firewall and "pipe" that into his SQL box without completely reconfiguring the server.

Is there a better workaround?

Thanks in advance,
Ryan

[DXD]

So what your saying is your ASP file connects to a SQL server outside of SB to update something, and your wanting a work around to get around the 1433 being blocked.

Since I just went around and around setting all of this up on my own SERVER at SB, I can not think of any options for you. SB has 1433 blocked (1434 too) and unless the person your trying to connect to changes their port I don't believe there is anything you can really do.

Maybe someone else can shed some light on this. If it was on a different port you could just create a Alias in the Client Network Utility for ASP to use.

[KyleMulligan]

If you connect two servers together via a VPN, you will be able to use any port you want.

[Powerhouse]

Thanks. I will check into that. I have also found an article on the MS site about adding additonal ports to a SQL server listener list. That might also be a good solution. IF the other hosting company will add the ports and then open the ports on the firewall.

Ryan