August 6, 2004 at 6:58 am
I had a user that received an ODBC MS SQL SERVER timeout error. In my search to fix this I discover that if I went int cliconfg and created an alias to the server and place the port 1433 in the required field that she no longer rec'd the error and could access the data.
I am glad this works but I am wondering if there are any ramifications I am not aware of by editing the Client Network Util on this one client. The other users are having no problems attaching to the server. The server is in our domain but at a remote location??
We are running SLq Serv 7 on a 2000 server - the user is running on an XP client machine. We recently upgraded all our clients to XP.
Also - we will be upgrading to Sql 2000 with in the year and I have read somewhere about issues with more then 1 instance on a server and problems with designating the port 1433. I think I quoted this right - if not please let me know
Thank you in advance for any input
August 6, 2004 at 7:16 am
SQL Server requires exclusive use of whatever port it's listening on. Therefore, if you have multiple instances on a server, each will require its own port. By default, SQL Server will randomly pick an unused port when you install a named instance.
Though this shouldn't be the case for XP, check to see what her default network library is on the client side. Make sure it is set to TCP/IP and not Named Pipes. You'll sometimes see timeouts across named pipes when you won't across TCP/IP. You can also verify how people are connecting through the use of SQL Profiler. Just look at the Existing Connection entries. That can give you a running log of how folks are coming in to SQL Server.
K. Brian Kelley
@kbriankelley
August 6, 2004 at 7:50 am
Thats the funny thing - when I went into client network Util to add the alias - there were no protocols listed on the general tab. I addded tcpip
But by adding the alias - I am not causing any problmes are I?
Thanks for the info Brian!
August 6, 2004 at 7:58 am
If you don't need the alias, you shouldn't use it. Only reason is if another problem shows up, whoever is doing the troubleshooting might forget or not know the alias is present.
K. Brian Kelley
@kbriankelley
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply