Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Need port information

Status
Not open for further replies.

tc3596

Technical User
Mar 16, 2001
283
I have 2000 server and 2000 clients. I have TCP/IP as only protocol enabled on server using port 1433. On the clients, I have TCP/IP as the only protocol enabled and 'Dynamically determining port' is checked. I am using an alias and ip address to sever as server name. Question: On the client, is there a benefit to checking 'Dynamically determining port' or should I just uncheck this and enter port 1433? Basically, I'm getting COM/ADO errors from our 3rd party application and I don't know where to begin tracking this down. Thanks for your thoughts.
 
First thing to check when you have Port problems with a client and SQL Server. Is there a firewall involved? Is Port 1433 blocked? A lot of firewall teams block this port because it's the simplest way to stop the SLAMMER worm.

-SQLBill
 
We do have a firewall, but I'm speaking of our internal users, who should not be affected. The errors happen every now and then, which makes it very frustrating. I'm not even sure if it's port related, but if it's better to hard code the port, then that's what I'll try. Also, tomorrow, we are planning on installing the latest sql server packs.
 
My ports are 'coded' in. I don't check Dynamically determine port.

Can you post the error(s)? Without them it's hard to do anything but guess.

It might be a problem with your DNS. It appears you are connecting using an Alias for the server. If DNS might be having problems with resolving the name.

-SQLBill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top