| | |
|
|
|
| BT OpenWorld SQL Server blocking??? |
|---|
| message from Laurie Sinnett on 3 Feb 2003 |
Hi,
In the light of last week's fun and games with SQL Slammer, are there any
web / database developers out there who have had any problems using SQL
Enterprise Manager to connect to remote SQL Servers through their OpenWorld
router / internet connection?
I'm trying to confirm /deny that Openworld, as a response to last week's
virus, have been blocking the ports that SQL Server uses to communicate (TCP
1433).
Our connection worked fine up until Friday and since Friday we have been
unable to connect through Openworld to any SQL box. The SQL boxes themselves
are fine, and through Claranet, for example, are responding to connect
requests correctly.
Any one run into similar probs?
Laurie Sinnett
|
| Bazza replied to Laurie Sinnett on 3 Feb 2003 |
Thanks to Ians post we can see that they are blocking the default SQL ports.
So, your SQL Server is located elsewhere on the Internet?
Do you have access to the remote server? Are you allowed to make
configuration changes to it?
How about configuring SQL to listen on another port?
Either that, or could you use a VPN between the two sites/servers?
Bazza
barry dot mccauley at btopenworld dot com
|
| Reckless replied to Laurie Sinnett on 4 Feb 2003 |
You mean you have a FFA SQL Server running on a default port open to the
Internet - EEK!
Do you really have to run it with an open access point? I access the work
SQLServer but only once connected via VPN!
"Laurie Sinnett" <laurie@softwarehse.com> wrote in message
news:BA642843.80E5%laurie@softwarehse.com...
|
| Laurie Sinnett replied to Reckless on 4 Feb 2003 |
Ah well, at least this confirms this (he said waiting for the BT Technical
CallBack that I had booked for 5.30pm!!!).
The problem is this - the majority of web hosting companies will not let you
(or even set up) a VPN for you to get to the SQL box - sure if it were your
own company that you were trying to 'remote access' then you could see how
this wouldn't be a problem.
The generally accepted method - SQL Enterprise Manager - communicates on TCP
port 1433 - the Slammer worm operated through UDP port 1434 - blocking TCP
1433 has no effect whatsoever on the worm, but what it does do is block the
default port used by Enterprise Manager. And not all ISP's are taking such a
'heavy-handed' approach - those with a little more savvy will have already
blocked UDP 1434 and service-packed any SQL boxes.
In my case, the external web hosting company that my client is using are not
going to reconfigure their SQL web farm so that they change the
communication port from TCP port 1433 - why should they? Not all customers
are affected - I can go through my Claranet dial-up and connect fine - it's
the ISP that is at fault.
Laurie Sinnett
|
|
Archived message: BT OpenWorld SQL Server blocking??? (UK Broadband - Wireless, Internet, Routers etc.)
