Re: error 10060 - going nuts

Well port 1434 is usually reserved for the SQL Browser service which is what the client would use to find the correct port number if all you gave it was the server address or instance. If you are going to specify a port then you should specify the actual port that SQL Server is using not the browser. If it is the default instance it will be 1433 by default and it could be anything if it is a named instance. If the browser is up and running you don't need to specify the port at all. What happens if you specify the IP address instead of the name? Try it with the actual port and without and see what you get. But my guess is that if you have a firewall you will need to open or forward port 1433 or what ever port that that instance is running under.

Example: 192.168.1.1:1433

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Rodrigo Guerra" <emaildorodrigo@xxxxxxxxx> wrote in message news:uCPi%239JWIHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
hi andrew,

sorry, I think I should've said register instead of connect. by "don't connect" I mean that I get this error trying to register my server in sql 2000 enterprise manager and/or SQL 2005 Managment Studio, not in a dynamic page.

I defined the port after the server name. "mssql.mynetkeepers.ca,1434" isn't that enought?

Both versions fails when trying to register this specific server.

I've registered sucessfuly at this adress using both sql's in other network(at work), so, I don't think that the problem is that. I forgot to say that in the problematic net (at home) I were able to register other SQL server without problem (in both sql 2000 and 2005), it only fails with this specific server *and* at home.

that's why I believe that the problem is some configuration... but where?

wired huh?



Moreover, I should mention that the problem is specific with this server


I believe that this way the the server will use the port specified
"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message news:OUWcvmIWIHA.2000@xxxxxxxxxxxxxxxxxxxxxxx
Are you really using port 1434 to connect? That is the port for the sql browser service. Maybe the msg is misleading but make sure the connection string is using the correct port if one is specified at all.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Rodrigo Guerra" <emaildorodrigo@xxxxxxxxx> wrote in message news:u$dbRUIWIHA.3940@xxxxxxxxxxxxxxxxxxxxxxx
hi all,

I'm having a hard time trying to connect to a database using sql 200 or 2005.
this is the message I get:

-----------------------------
Cannot connect to mssql.mynetkeepers.ca,1434.
-----------------------------
ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------


I believe that this is something related with my router/proxy at home, I use a Linksys wireless router.

I say that because I've tried to connect thru another network (work) and the connection goes fine with BOTH sql 2000 and 2005 (with the default parameters), and at home it just doesn't connect.

I've configured SQL 2005 to accept remote connections in the Surface Configuration Area but it doesn't work, also I'm not using any firewall (even windows).

please help!
thank you,
rodrigo.
Loading