@Diavolino:
Looks like you re-post the same question for the 4th times ... (registered name or IP, SQL or NT auth, ...) if you don't understand a topic / concept (such as the purpose of a DNS) google it but don't re-ask the exact same question.
Name or IP
Quote:
|
The server is identified by its IP address or by its name if it can be resolved by DNS, Wins or NetBIOS
|
NetBios exists since the 80s, it allows to assign an human-readable-name to machine on a local network.
WINS is a Microsoft-specific extension of NetBios, it was the main naming system before apparition of Active Directory. The names managed by the WINS layer are usable in a domestic network (2+ PC connected with or w/o a switch or hub) as well as a domain (private network with 10 or 100+ computers).
DNS resolve names (give the actual IP of a server) on the internet (large private networks/domains frequently also use private DNS).
In your case, the SQL Server is on internet, so using its actual IP or its name (one of its registered name) is just exactly the SAME.
With your browser, requesting the page "google.fr" or "173.194.40.120" is EXACTLY the same (and that IP is just one of the numerous IP owned by google).
NT or SQL Authentication
yet answered and a lot of available pages, if required start with
[Only registered and activated users can see links. Click Here To Register...].
In your case (remote SQL serveur), you may have full access to the server (ie you are able to do a remote login using
remote desktop service) or, more likely, you have a SQL account (or probably a sFTP account and so on).
In this case - meaning if you have *no* NT/AD/... account on the server - you will of course NOT use the NT authentication.
Meantime, if you have a MS account you DONT want to use it to connect in plain (expect of course if you want your server to be attacked and corrupted in a very short time)(4th time: you don't send your CB info on a HTTP server, so you must NOT connect w/o SSH to a remote server; but it's still up to you).
Regarding your error:
as already indicated, error 13226 "may also due to invalid or unreachable IP".
with your indication, we don't know if you're using a valid IP or name, we don't know if an host with that IP exist / is reachable on the net; we don't know if the used name can be resolved by a DNS; nor if a SQL server is actually running AND reachable on this host.
The statement
Quote:
|
"Because the server is turning well and everything isworking just trying to connect via my personal computer to the server..."
|
is not that helpfull, since you indicate a) every thing is OK, b) but I can't connect on it ("tout marche super bien mais pas moyen de se connecter, donc rien ne marche").
Quote:
That means that i should opening Server management first to use studio ?
Quote:
|
Did you try to connect using SQL Server Management Studio first, to see if everything works?
|
|
No it means "did you try to connect to your (suuposed working) server using MSSQL Management Studio".
If you success to connect, use the same login information when trying to connect with shStudio.
If you don't success to connect, fix the issue with MS tools (with the SQL Management studio assistance) and possibly info from your provider.
The SQL login from shStudio should be used only if all potential issues (including security) are under control and solved; if some issues still exist, manage them with the right tools and methods.