Node.js无法连接指定IP的MS SQL服务器问题求助

Hey there! Let’s work through this MS SQL Server connection issue together. Looking at your code snippet, I notice you haven’t included the actual database connection setup—this is usually where the problem starts. Here’s a step-by-step breakdown to get your API connected:

1. Add a Complete Connection Configuration #

First, you need to define a valid connection object with all necessary details. Without this, your app can’t reach the remote server. Add this to your code:

// SQL Server connection configuration
const sqlConfig = {
  user: "your_sql_username", // e.g., 'sa' or a dedicated DB user
  password: "your_sql_password",
  server: "target_ip_address", // Replace with your server's IP (e.g., '192.168.0.100')
  database: "your_database_name",
  port: 1433, // Default SQL port; change if you use a custom one
  options: {
    encrypt: false, // Set to true if using Azure SQL or encrypted connections
    trustServerCertificate: true, // Temp fix for dev environments (avoid in production)
  },
};

// Establish connection with error handling
sql.connect(sqlConfig)
  .then(() => console.log("Successfully connected to SQL Server!"))
  .catch((err) => console.error("Connection failed:", err.message));

2. Verify Remote Server Accessibility #

Even with correct code, network or server settings can block connections:

• Enable TCP/IP in SQL Server: Open SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for [Your Instance] → Enable TCP/IP. Restart the SQL Server service afterward.
• Firewall Rules: Ensure the remote server’s firewall allows inbound traffic on port 1433 (or your custom port). On your local machine, also check that outbound traffic to that port isn’t blocked.
• Test Connectivity: Run these commands in your terminal to confirm the server is reachable:

  ping target_ip_address # Checks if the server is online
  telnet target_ip_address 1433 # Checks if the SQL port is open
  

• Authentication Mode: Make sure the SQL Server is set to Mixed Mode Authentication (Windows + SQL Server). If you’re using a SQL account, it won’t work with Windows-only auth.

3. Debug with Error Details #

Always capture and log connection errors—they’ll tell you exactly what’s wrong (e.g., wrong credentials, blocked port, invalid database name). The .catch() block in the code above will print specific messages like:

• Login failed for user 'your_username': Credentials are incorrect or the user doesn’t have access.
• Failed to connect to target_ip_address:1433: Network/firewall issue.
• Cannot open database "your_db" requested by the login: Database name is wrong or the user doesn’t have permissions to access it.

4. Check Dependency Versions #

Outdated mssql packages can cause compatibility issues. Update to the latest stable version:

npm update mssql

Quick Note on Your CORS Middleware #

Your CORS header for Access-Control-Allow-Headers is cut off—complete it to avoid future API request issues:

res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept, Authorization");

Start with these steps, and the error message from your connection attempt will point you to the exact fix you need.

内容的提问来源于stack exchange，提问作者Raja Osama