Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2008-05-15 : 11:09:21
|
| I think I'm having this problem but on a 2000 server:http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspxI have a .NET app that works fine from people's desktops, but from Terminal Services, they get the connectivity error.By testing with telnet from Terminal Services. I've established that the server is listening on 1623. Could that be causing the problem?UPDATE:That was indeed the problem.When I ran cliconfg.exe on the client, it was still listening on 1433. changed it to 1623 and bam! |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-05-15 : 21:48:08
|
| You need to check sql server log to find out which port sql is listening on, then set connection string with that port. |
 |
|
|
|
|
|
Terminal Services problem