March 28, 2005 at 9:31 am
Hi,
i have 2 sql 2000 servers at same lan.
after i performed some failure test for distributed transaction, i have this problem :
connection timed out for
osql -S server_name -U user -P pass
and it does connect with IP
and now all my replications stopped couse it cann't connect to "server_name"..
may be somebody knows how it can be repaired ?
10x
March 28, 2005 at 9:34 am
I would check that there is no issue with you DNS servers. If you are able to connect with the IP and not the server name it would indicate that the server could not be resolved. Try pinging the server name and see if you get a "server could not be resolved" issue.
March 28, 2005 at 9:43 am
Hi Nicholas,
it answers to ping ( resolves right IP ), and still can't connect
March 28, 2005 at 9:59 am
How about checking the port that SQL is listening on?
March 28, 2005 at 10:20 am
for tcp/ip the default port is 1433, and telnet answers to it
March 28, 2005 at 10:47 am
But is it actually listening on 1433? Check the server configuration utlity.
March 28, 2005 at 10:57 am
yes yes, it is 1433
the ODBC ( of another server ), for example, finds this one by name, but on login it gets timeout
March 28, 2005 at 11:38 am
Have you tried rebooting all the servers involved (if you are able) ?
March 29, 2005 at 6:16 am
Thanks alot, i just added alias to client network utility, and it works !! ; ))
If somebody needs here is article about sql server 2000 connectivity
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply