Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
SAFEKOM
Starting Member
2 Posts |
Posted - 2010-07-13 : 12:39:29
|
Promblem:How can I access SQL server on WAN????????????????????????????????-----------------------------------------------------------Error: (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)------------------------------------------------------------------------Information: Windows Sever 2008 R1 (64bit OS) Service Pack 2Microsoft SQL 2008 Server Management Studio (10.0)(64bit)Microsoft .Net Frame work 3.5 SP1------------------------------------------------------------------------------Additional Information:IIS 7 installedIn TCP/IP properties TCP Dynamic ports : 49157 All services are running except SQL Server Agent(instance name), and their start mode is automatic.There is not any Alies configure that have problem .------------------------------------------------------------------What I already done:1) SQL SERVER is up and the instance connect is running. 2) All required ports on Firewall is open/ also try to disable Firewall but no success. 3) TCP/IP protocol is ENABLE. SQL SERVER port is by Default 1433.4) Also try this:the probelm is the Instance name from the client is not resolved, to do that follow the below shown steps.1. navigate to C:\Windows\System32\drivers\etc2. Open hosts file in notepad3. add the entry at the end of line, as i did for example213.165.131.65 KSSQLSRVR213.165.131.65 KSSQLSRVR\SPDEV01those were my instances i am tried to connect remotely5) In Server Name I tried IP address of Server (also with port number like 213.165.131.65,1433 )and also server name and instance name.I m pulling out my hairs becoz of ANNOYING error. KINDLY HELP ME OUT OF THIS.M Nasir. |
|
beniaminus
Starting Member
21 Posts |
Posted - 2010-07-14 : 10:04:28
|
Can you ping the server from the client? You could trying doing a port scan of the server to see if the sql server port is open.Also, I'm sure you've done this, but its worth checking: Have you ticked 'Enable remote connections' in SQL Server Management studio on the server?Ben :) |
 |
|
|
|
|