Connect to sql server 2000 remotely
-
Hello World... I want to connect to a sql server 2000 db remotely(Lan Network). I write a c# test project and set server, my server IP but after run it ,give me this error: Time out, your server computer not response. I beleve, i must to configure my server sqlserver but ...!!!??? sry for my very bad en... :rolleyes: TanX World...
-
Hello World... I want to connect to a sql server 2000 db remotely(Lan Network). I write a c# test project and set server, my server IP but after run it ,give me this error: Time out, your server computer not response. I beleve, i must to configure my server sqlserver but ...!!!??? sry for my very bad en... :rolleyes: TanX World...
I think it is because of your ConnectionString, do you addressed your SqlDB correctly, in ConnectionString?
While (true) { Human.isLearnable = true; }
-
I think it is because of your ConnectionString, do you addressed your SqlDB correctly, in ConnectionString?
While (true) { Human.isLearnable = true; }
my connectionstring is corrent because when I change my server Name to (local) my app haven't any error... ...:confused:
-
Hello World... I want to connect to a sql server 2000 db remotely(Lan Network). I write a c# test project and set server, my server IP but after run it ,give me this error: Time out, your server computer not response. I beleve, i must to configure my server sqlserver but ...!!!??? sry for my very bad en... :rolleyes: TanX World...
Basically three possibilities: 1. Your SQL Server isn't configured to use TCP/IP, use Configuration Manager at server 2. Your connection string is faulty, bad ip-address, port etc 3. IP traffic isn't routed to server, for example because of an firewall
The need to optimize rises from a bad design
-
Basically three possibilities: 1. Your SQL Server isn't configured to use TCP/IP, use Configuration Manager at server 2. Your connection string is faulty, bad ip-address, port etc 3. IP traffic isn't routed to server, for example because of an firewall
The need to optimize rises from a bad design
- In sqlserver I see tcp/ip connection & I ticked it... - If my connectionstring faulty ,i can not connect with it localy... my connectionstring:
public void Connect()
{
string cs = "Server = 192.168.10.190; database = DB1; user=u1; password=123";
con.ConnectionString = cs;
con.Open();
} -
- In sqlserver I see tcp/ip connection & I ticked it... - If my connectionstring faulty ,i can not connect with it localy... my connectionstring:
public void Connect()
{
string cs = "Server = 192.168.10.190; database = DB1; user=u1; password=123";
con.ConnectionString = cs;
con.Open();
} -
Few questions: - is the SQL Server running on the same computer where you're running the app? - if you can connect to it locally but not remotely, what's the difference in connection string?
The need to optimize rises from a bad design
diference of it , is i change servername to (local)... I have some pc with Lan network in one of these I have sqlserver with my database, and in other pcs i have app for connect to that.
-
diference of it , is i change servername to (local)... I have some pc with Lan network in one of these I have sqlserver with my database, and in other pcs i have app for connect to that.
Then the three choices I listed are most common reasons. It's a very different situation to use IP than to connect to localhost. Few things you should check, - try to ping the IP-address - check on server side that the listening port is 1433 or if it isn't, specify the correct port in connection string - check on server side that the other pc can listen to port 1433 (no Windows firewall blocking) - check that it isn't a named instance on the server or if it is, specify the instance name in connection string
The need to optimize rises from a bad design