7 มิถุนายน 2555 11:46
I have an client application which make 2 connections to the database.
When my application connects to my test server both connections are on port 1433
When my application connects to my production server the first connection is on port 1433 but the second connection tries to connect on port 445 and hangs.
Both conection use the same connection string does anaybody has a clue why the client tries to connect on port 445.
8 มิถุนายน 2555 6:04
Such cases mark for some routering issue for identifying the appropriate network protocol to connect SQL Server either IPX or shared or VIA or Named Pipes and even TCP/IP is selected , it is still remaining to identifying the appropriate
IP +TCP ports which yield to with much time consumed to reach DB server ending you with such outage cases.
Therefore, I do recommend to work out the solution of SQL Server Client network utility through
Run>>Cliconfg.exe >>Alias >>>Add >>>TCP /IP >>>then specify the appropriate alias (MAY be the same as the original connection string) >>>>and mark out dynamic port to let static by the same port ( 1433 ex by our current case)
Please work out it and let me know your feedback
Shehap (DB Consultant/DB Architect) Think More deeply of DB Stress Stabilities
- ทำเครื่องหมายเป็นคำตอบโดย Iric WenModerator 17 มิถุนายน 2555 5:14