Connection over internet

I need to connect to a sql server through the internet.
Inside the LAN everything works great, but if try to connect from a pc
outside the lan over the internet I get an error message saying SQLstate
01000 and SQL state 08001 error 17.
What's wrong '
Thank You since now to anyone can help me
Bye
PaoloGian,
How are you addressing the SQL Server? The external IP address should be
different to the one on your LAN. I personally would not be comfortable
with my SQL Server accessible over the internet.
1. Make sure that the correct ports are open on your firewall.
2. Check that SQL Server is listening on TCP/IP, and the port number
3. For named instances set up an alias and "hard code" the port using
the Server Network Utility.
4. Do not allow access through port 1434 on the firewall.
Take a look at this article also:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/?id=328306
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Gian Paolo Piscopo wrote:
> I need to connect to a sql server through the internet.
> Inside the LAN everything works great, but if try to connect from a pc
> outside the lan over the internet I get an error message saying SQLstate
> 01000 and SQL state 08001 error 17.
> What's wrong '
> Thank You since now to anyone can help me
> Bye
> Paolo
>|||Hi
There are a few things you'll have to check.
1. Have you got a route from your external PC into the SQL server.? If you
connect via an IP address, you'll have to make sure that this IP address has
a route through your FireWall. If you connect via a name, you'll have to
make sure that this name is bound to the correct IP address.
2. Have you opened the right ports in your FireWall? By default SQL server
uses port 1433, so you need to have a rule in your FireWall that allows this
traffic.
Also, it might help if you tell how you try to connect to the server - with
EM, QA or an application?
Regards
Steen
Gian Paolo Piscopo wrote:
> I need to connect to a sql server through the internet.
> Inside the LAN everything works great, but if try to connect from a pc
> outside the lan over the internet I get an error message saying
> SQLstate 01000 and SQL state 08001 error 17.
> What's wrong '
> Thank You since now to anyone can help me
> Bye
> Paolo

Connection Manager in SSIS packages

I am trying to run a package outside of the Business Intelligence development Studio. It continuously fails and tell me that my username cannot logon due to a password failure. When I check my connections the password never shows in the connection string and remains blank in the connection properties although I have checked Save Password in the connection properties. Does anyone know how I can save the password in the connection string being utilized in the SSIS package?Passwords are not shown in the properties due to security. I am assuming you are using SQL Server authentication instead of Windows Authentication. When you specify the password and save password, it saves it. But if you open the connection manager again, it won't show you the password (though it is still saved). However, to be able to leave it in the current state, you should now click Cancel to exit the connection manager, instead of OK. If you press OK, it will expect you to enter the password again. I think you must have opened the connection manager, and then pressed Ok, instead of Cancel, which erased the password.|||

I don't think that's the problem. I experiencing the same problem in my development Environment (using SQL Server authentication):

We're a group of developers working on the same package. after setting the connection managers with the correct username and password (and checking the save option) and saving the package by a certain user, when a different user accessing it, he cannot run the package and have to go through all the connection managers and ser the user and passwords all over again.

Any solution?

|||

Liran,

Check the ProtectionLevel property of your package. My guess is that you have ProtectionLevel=EncryptSensitiveWithUserKey

This means that all passwords are encrypted with a user-specific value meaning that only that user can run it.

If you follow best practice (http://blogs.conchango.com/jamiethomson/archive/2006/01/05/2554.aspx) of making your packages location-independant (http://www.windowsitpro.com/SQLServer/Article/ArticleID/47688/SQLServer_47688.html) then this should not be a problem.

-Jamie

sqlsql