Why can't I connect to my discountasp.net dbase server from SQL?

I'm able to connect via telnet without a problem. Yet still cannot connect from SQL Server Management Studio. I also tried using the "tcp:" prefix in the server name and also tried ",14330" for the port.


What next?

 

OK--new news... up until now, i have tried connecting WITHOUT registering a new server. This time, i discovered the "Registered Servers" button, and registered the server thru that. Then i connected via that... and it seems to have connected.


Should i not have been trying to connect via the "normal" Connect dialog that i usually used to connect to my local server?


Or is something else different?

 

MORE news...!

I failed to mention i connected on my other machine(!) I just went back to my laptop (original machine) and it doesnt connect via the Registered server Now, i installed telnet on my other machine, not this one--other than that, i can't think of any differences between the two.

I NEED the laptop to work, as i travel with that one...

 

OK... well, found a typo on the laptop for the server registration, and it now works as well

So... thanx for all your help...

'Course, now i have to find out why i cannot log into my website... but i imagine it has something to do with the Membership dbase/etc... on to the next problem...

thx!
--g

 

I'm sure this has been dealt with a ton of times here, but i cannot find any topics here that have helped me so far re: this.

I JUST added on SQL2005 support to my website. So, i'm struggling with just getting my dbase transferred to my site. When i try connecting from SQL Server Management Studio, it spends about 30 seconds trying to connect then fails with an error:

TITLE: Connect to Server
------------------------------
Cannot connect to sql2k511.discountasp.net.
------------------------------
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------

This is driving me nuts! Do i have to enable TCP/IP? I've enabled it in the client protocols folder in the SQL Server Config Manager.

It really shouldnt be this difficult, should it?

I've already blown a good tow hours trying to resolve this... any help from discountasp.net people here would be greatly appreciated... or perhaps give me a call?

thx!
--glenn

 

The error is a little misleading with 'under the default settings SQL Server does not allow remote connections'. This makes it seems that the db server is not configured to take incoming connection when in fact it is a network connectivity issue. If you are certain that your DBMS is configured with TCP protocol, try checking if the ports are being blocked. By default it should use port 1433, if this is blocked you can try using port 14330. As a test try performing a telnet test to the db server. Open a MS DOS command prompt and type ---- telnet [the db server name] 1433 ----- If you get a blank screen then it means it connected. If you get an error, it should be similar to the one you are getting with SQL Server Management Studio. Try also performing the test with 14330.

Additionally you can force your DBMS to use the tcp protocal and the over ride the port number by specifying it in the server name. As an example for the server name you can try and input tcp:sql2k501.discountasp.net,1433

I'm not sure what your server name is by sql2k501.discountasp.net is just an example but this example will make sure that SQL Server Management Studio uses the TCP protocol and port 1433. This can also be used to connect to the alternative SQL port 14330.

rcp
DiscountASP.NET
www.DiscountASP.NET

 

It was purely a connection string issue--my code was still using a hardcoded string in one function, which was referring to localhost. Quick fix.


All is good now


Off topic, kinda, but--what's the preferred way to move a dbase to the website? Dump the whole thing to a script (been using the Database Publishing Wizard to do this), then run it in SQL to build the dbase? Do you support the Publishing Wizard directly (cool addon--if not, check it out!)? Or is detach/attach the way it's done here? Looks like it is based on the tools page.


thx again


--g

 

Whats the error message your getting. Maybe we can help or point you to the right direction.

rcp
DiscountASP.NET
www.DiscountASP.NET