We have several sites that use MSSQL12. We now cannot connect to them from our development environment, even using the previously suggested IP address and suggested port. This connection string has always worked great in the past. I’m assuming it’s something to do with the migration.
I don’t want to post the IP address we’re using or the port here in the thread, but if this information has recently changed, please let me know. We have been using a 173 IP address for quite a while, so I don’t think it’s an IP address issue.
Ticket RS #HMS-78117-131 submitted 1 hour ago with no response. Our development has ceased without connection to the DB. Strangely enough, this ticket doesn’t show in my helpdesk tickets, even though I received the auto response confirming the ticket submission.
Nothing to do with migration, all settings and IP the same on MSSQL12 for quite a while now, it is just that sometimes the external port system needs a firm boot kick to get going! Should be set now.
Having the same issue with mssql13 this morning. Development/testing comes to a halt waiting on this to be resolved. This is a very expensive situation for us.
Seems that there are too many people using it to connect their website to the DB server, we’ll try to hunt those down and close them off.
I know you know but just in case another reads this. DO NOT use the outside IP and port for your web to SQL app, it is not required, it works directly.
We have found a major source of problems with someone using it from web server to sql server, and blocking, but going to be issues for next 20 minutes because we are correcting some rules now.
Win18, Win33 had users utilizing this for their main connections from their websites, and had to be blocked off, also one VPS user (which we can trace down whom to mail easier) was given notice of using the correct IP to access from inside systems, and blocked off.
I’m having an issue connecting to my MSSQL db on MSSQL2 is it also having a similar issue? Do I need to change to an IP in my web.config? currently it’s connecting via mssql2.mydomainname…
I have been having this same issue for the past few weeks with different MSSQL servers. This has cost me thousands of dollars in development/testing downtime. I see nothing to convince me that Jodo has this issue handled. If I don’t see a resolution very soon, I will be moving all new development to a different host. It would be irresponsible to keep sending new development to Jodo.
Stephen, what’s the deal? Why can’t this get a true resolution?
It was down again when I got back from lunch. I sent our static IP in a PM to you Stephen if that helps. Though it would be nice to be able to connect from anywhere as I do not always work from the office.
Anything that can be done to resolve the issue for good would be very appreciated. We’ve had nearly 2 full days now of getting hardly any work done because of this.
I have a live website that has an error on it that I can’t fix because I can’t get to the DB. The client is irate, and I don’t blame him. This is pure shit!!! Fix it or I’m out. This has gone on way too long.
