MSSQL IP mappings if using IP for connection string!

Stephen

US Operations
Staff member
CLuster2:
If you HAVE in string 64.71.228.8 please change to - 173.0.138.12

If you HAVE 64.71.229.11 change to 173.0.138.16

if you have 66.232.25.15 change to 173.0.139.236

As an alternative, use the mssql1/2/3 dns name listed in your control panel as it will map to the correct IP properly automatically.

If you have the old IP in, it will work for a short time more, but it will be much slower.

note:

This only applies for web servers connecting to SQL servers. you cannot connect directly to SQL servers from outside the web servers at this time. We will apply a work around for that soon.

This si so far a very common thread/complaint seen today, so this is a self help fix as well.
 
We were previously able to access msql1 by using remote connections and this is disabled for new mssql1. Our applications depend on this and our business is on stand by for over 24h now. When exactly you are going to enable remote access for mssql1 again as noted in another post of yours ("External SQL access is NOT available from/to these IPs. For management purposes we will be getting you a special port and access shortly.")
 
We were previously able to access msql1 by using remote connections and this is disabled for new mssql1. Our applications depend on this and our business is on stand by for over 24h now. When exactly you are going to enable remote access for mssql1 again as noted in another post of yours ("External SQL access is NOT available from/to these IPs. For management purposes we will be getting you a special port and access shortly.")

Please consider VPS for this purpose. Our shared servers are not meant for use outside our network.
 
You were supposed to announce this change of policy so we could move our site to another hosting on time. Instead we are now offline for 24h. What about ("External SQL access is NOT available from/to these IPs. For management purposes we will be getting you a special port and access shortly." post? Can you confirm that you are not going to enable this at all so we can make a decision and move to another hosting?

While I'm here is there any way to make a backup of ms sql database from control panel?
 
You were supposed to announce this change of policy so we could move our site to another hosting on time. Instead we are now offline for 24h. What about ("External SQL access is NOT available from/to these IPs. For management purposes we will be getting you a special port and access shortly." post? Can you confirm that you are not going to enable this at all so we can make a decision and move to another hosting?

While I'm here is there any way to make a backup of ms sql database from control panel?
SQL is unaccounted traffic and it is for web to sql traffic, it is NOT for making external apps based on direct access. It has been blocked for a long time when seen.

VPS services can make SQL Servers with traffic accounted at the network level.
 
SQL is unaccounted traffic and it is for web to sql traffic, it is NOT for making external apps based on direct access. It has been blocked for a long time when seen.

VPS services can make SQL Servers with traffic accounted at the network level.

Main application is working on web server and accessing sql server locally. We need remote access in order to be able to access database from ms sql sms (in order to manage it) and we have a specific need for accessing sql server from our in-house application for minor synchronization tasks. None of above will and was not generating significant traffic. Anyway, if you measure the traffic through email server (which is also accessed remotely) you should also be able to measure traffic made to sql server (based on logged user). We have no problem with this. I never though that this traffic was unaccounted and in our case this traffic was minimal.

Btw, we lost 24h and we had to move our db to another hosting company.

If you prevent remote access you should state this somewhere. This was one of the requirements when we were choosing the hosting solution.
 
Main application is working on web server and accessing sql server locally. We need remote access in order to be able to access database from ms sql sms (in order to manage it) and we have a specific need for accessing sql server from our in-house application for minor synchronization tasks. None of above will and was not generating significant traffic. Anyway, if you measure the traffic through email server (which is also accessed remotely) you should also be able to measure traffic made to sql server (based on logged user). We have no problem with this. I never though that this traffic was unaccounted and in our case this traffic was minimal.

Btw, we lost 24h and we had to move our db to another hosting company.

If you prevent remote access you should state this somewhere. This was one of the requirements when we were choosing the hosting solution.


External access has been made available already now. We cannot list it here, but it is in the customer only section.

http://support.jodohost.com/showthread.php?t=21822

We are prepping a mail to send about this now, and for your purposes that was never intended to remain blocked for the long term, we understand it is needed, it just took us some time to get that workaround in place.
 
We still can't access SQL through MS SQL Server Studio.

we already 1 week that we cannot o any SQL table change becuase of that.

it's a teribble situation, please provide access immediately as previously stated in the last post (stephen)

hawana team
 
Back
Top