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 |
|
jmangione
Starting Member
7 Posts |
 Posted - 2004-10-22 : 16:25:31
|
| I have a Win 2003 SQL Server with SQL 2000 on it. We are running into problems with NamedPipes (http://support.microsoft.com/default.aspx?scid=kb;en-us;827452&Product=sql2k) which reccomends using TCP/IP instead. I can't get that to work and when I run Portqury.exe (http://support.microsoft.com/default.aspx?scid=kb;en-us;310099) I find out that both 1433 and 1434 are "not listening."Has anyone encountered this issue or does anyone have any advice? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-10-22 : 16:27:19
|
| What port is your SQL Server listening on? Check Server Network Utility.Tara |
 |
|
|
jmangione
Starting Member
7 Posts |
Posted - 2004-10-22 : 16:30:56
|
| It says 1434 in Server Network Utility... |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-10-22 : 16:50:15
|
| A couple of people here have had that same problem. I wonder if port 1434 is blocked by default on Win2k3. Try another port, restart the services, then try connecting. If it works, then we know 1434 is blocked.Tara |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-10-23 : 14:01:01
|
| You have port 1434 listed for TCP/IP???? That won't work, because that's the UDP port it tries to use for named pipes or to do port discovery. I would place it on a non-standard port, make sure the computers connecting to it all have MDAC 2.6 SP1 Refresh or later, and call it a day. You don't need NamedPipes normally and shouldn't use it unless you just have a good reason for it.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
Can't connect via TCP/IP