Data Access problem

Data Access problem

• LynnR

  Connecting To execjobstat01...Could not open a connection to host on port 1433 :
   Connect failed

   I restart the IPsec service by executing:

  net stop policyagent
  net start policyagent

  still not working

   

  - (on the client machine, perhaps blocking outgoing connections to port 1433. )

  I install sql server server on my machine.

  telnet to local is connected.

  how can I open this port for remote access
  

   

   

   

   

  
  
  

• Stanley_fu2000

  Thank you for your reply.

  ping is working.

  telnet can't open connection to sqlservermachine, connection failed.

  (telnet is working on my colleage's machine.)

  What should I do

  thank you

  
  
  

• .blogspot.com

  if "telnet <sqlServerMachineName> 445" works from your machine, and "telnet <sqlServerMachineName> 1433" works from other people's machines but not from yours then the most likely explanation is that some firewall is blocking your connections.

  Do you have any 3rd party (non-MS) firewalls or proxies installed in any of the systems or network components

  Did you check settings of any firewalls that may be involved

  Unfortunately, the MDAC client stack does not provide detailed error information.

  Easier to troubleshoot is our new client stack called SQL Native Client, which can be downloaded from http://msdn.microsoft.com/data/sqlnative/default.aspx.

  If you install it on your client machine you can test a connection by creating a user DSN through the ODBC Data Source Administration tool, which can be started from command line by running odbcad32.exe, then follow:

  - User DSN -> Add...

  - scroll down, and select "SQL Native Client" -> Finish

  - Name: test

  - Server: tcp:<sqlServerMachineName>,1433

  - How should SQL Server verify the authenticity of the login ID Choose what's appropriate -> Next

  Paste the error back here, *repalcing* any confidential information if present.

  
  
  

• Jallman

  telnet <sqlServerMachineName> 445 is working

  how to change configuration in sql server, make my remote connection working

  
  
  

• wirelessdeveloper

  Is there network connectivity from the machine running the web application to the machine running SQL Server What do you get if your run the following commands on the web application's machine (replace <sqlServerMachineName> with the actual name):

  telnet <sqlServerMachineName> 1433

  ping <sqlServerMachineName>

  
  
  

• abdou

  Most of the time these cases turn out to be some sort of network configuration issues. What I would suggest is to find another listening TCP port on the same server machine if available ("netstat -an | findstr LISTENING"), and then try to use telnet against that port. Port 445 if frequqntly a good candidate, e.g.

  telnet <sqlServerMachineName> 445

  If that succeeds the failure is SQL Server specific. If it fails it points to network configuration.

  As far as to the question on how to open ports - that depends on whether and what kind of firewall there may be in the system. E.g., the built-in Windows firewall on the server machine can be opened from Control Panel, and then you can examine whether it blocks port 1433 - either fully or with some exceptions.

  
  
  

• estump1

  These symptoms are most typically caused either by firewall or IPsec settings.

  A firewall (either built-in Windows or 3rd part software or hardware) can be:

  - on the server machine, perhaps allowing connections from certain machines only.

  - inside the network.

  - on the client machine, perhaps blocking outgoing connections to port 1433.

  Does either of the machines use/require IPsec

  You can restart the IPsec service by executing:

  net stop policyagent
  net start policyagent
  

  What is the full error message you get when you run the telnet command

  
  
  
• Data Access problem