Changing port? Options?

[Dutchk]

I'm in a quandary here and its getting tougher by the minute. I'm also not a database admin type and I barely know enough to set things up using the wizards.

I have a small business with web sites and databases hosted through various hosting services. My databases are SQL Server 2000. My connection to the internet is a cable broadband through Adelphia. It is the only broadband connection available in my area except for a satellite connection. Adelphia decided to block port 1433 in response to the latest virus attacks and I'm told by their service it is nationwide and indefinite. I've went round and round with what passes for their support and they basically say they can do what they want....read the terms and conditions, etc, etc..

My business is dependent on access to the databases. This is killing me. I've got some rudimentary functionality back by setting up web based (ASP)queries. However, I have hundreds of queries, reports, and user interfaces built with MS Access and Crystal Reports front ends through an ODBC connection that no longer works. Needless to say, Enterprise Manager is sneakers up too.

I can't do much about my hosting provider's setup with respect to port assignment, but is there anything I can do on my end? What are my options?

I'm looking at a dial up connection until my lease runs out so that I can move out from under this Adelphia mess.

Many thanks.

Dutch

 

[SQLBill]

Go to Enterprise Manager ON THE SQL SERVER. Drill down to the server you need to change. Right click on it. Select Properties. Select the GENERAL tab. Click on Network Configuration..., in the right window pane of the pop-up, select TCP/IP, click on Properties...

Change the Port number in the popup window.

LASTLY, remember to notify your users of the Port number change.

-SQLBill

 

[Dutchk]

Thanks Bill,

Perhaps my ignorance is showing here, but doesn't this have to take place on the server side? My hosting provider hosts the databases, I'm just trying to remotely access them with Enterprise Manager or ODBC.

A related question comes to mind now. If the host server has to do this, is this something that hosting services typically will do to accomodate their users?

Dutch

 

[JayKusch]

Morning Dutchk ....

You are right about this having to occur on the server-side. Its as if your provider has turned the water off on your business.

I would be really ticked if my provider sold me a connectivity package and then decided to shut the ports down to access my DBs. You may want to look into the legalities of what they have done.

Database connectivity seems to be the very backbone of your operation and I am sure your provider should have another method(s) to secure ports that are vital to business users are accessible as well as secured. I am sure other providers are choosing options other that what you are currently experiencing or I would have expected a rush of posts and rants against all providers by now.

Let us know how this turns out!

Thanks

J. Kusch

 

[SQLBill]

Yes, it has to be done on the SQL Server itself.

I don't know if it's something done normally by hosting services. But they don't want to lose your business and in the SQL Server world, port 1433 is being blocked more and more for security.

I would let your hosting service know the problem (1. your ISP blocks port 1433, 2. you need access to your SQL Server database, 3. the SQL Server currently is using port 1433.).

Offer these solutions to the hosting service.
1. Request they change the port. Include the fact that this change will help with their security as TCP Port 1433 is know by all hackers to be used by SQL Server and that changing it would increase security.

2. If they can't do that (remember, if they change the port they have to notify ALL users and that could be ALOT of people/businesses). Request they contact your ISP and maybe they can get the ISP to add a rule to the firewall allowing your IP/MAC address through on port 1433.

Before you get the hosting service involved, you might want to talk to your ISP about #2...and see if they can accomodate you by creating a rule that allows your IP/MAC address through the firewall on TCP Port 1433.

-SQLBill