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 |
|
iminore
Posting Yak Master
141 Posts |
 Posted - 2009-03-09 : 12:36:29
|
| I'm running SQL Express and ASP web pages on a 2003 machine. I reckon I've read all the logs on here and much beside relating to ports but I'm still struggling. I don't think my problem is Express specific.Some months ago I changed the listening port to 8123 (made that up) and changed the connection string on my ASP files to connect via that port. All worked fine. Then last week a particular site connection failed and I could only connect by removing the port from the connection. That's continued working but so has another site which continues to connect to another database in the same SQL instance, via 8123.According to the configuration manager I'm using port 8123. I can't see in any log entry which port it's listening to. I beginning to wonder whether for local connections the port has any meaning.Any meaningful advice would be greatly appreciated. Yes, I stop/start SQL after making changes.My word is my code. |
|
|
iminore
Posting Yak Master
141 Posts |
Posted - 2009-03-09 : 13:08:57
|
| Reading more about network protocols if the website pages are on the same machine as the SQL Server can they just run with 'shared memory' protocol. Could I disable 'named pipes' and 'TCP/IP'.My word is my code. |
 |
|
|
iminore
Posting Yak Master
141 Posts |
Posted - 2009-03-09 : 16:44:57
|
| Well, I've disabled named pipes and TCP/IP and it works fine - via shared memory presumably.Am I talking to myself? Wouldn't be the first time ...My word is my code. |
|
|
|
hey001us
Posting Yak Master
185 Posts |
Posted - 2009-03-09 : 20:57:15
|
| can you try this at cmd. netstat -anand check which port the sql is listening. Did you reinstalled sql recently?hey |
|
|
|
iminore
Posting Yak Master
141 Posts |
Posted - 2009-03-12 : 06:38:55
|
| hi there. Sorry for delay - went away.Ran 'netstat -an' not sure how to interpret the resulting list.No, didn't reinstall recently.I think I'm OK. Using IIS and SQL on the same machine 'shared memory' is adequate and presumably no external user can connect to the SQL.My word is my code. |
|
|
|
|
|
|
SQL Server connection ports