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 |
|
bshannon
Starting Member
3 Posts |
 Posted - 2010-01-29 : 08:21:46
|
| I recently changed the domain that my SQL Server was joined to. It worked fine on the Test server, but the Live server got screwed up somehow. It quit listening on ports 1433 and 1434.We didn't have a default instance installed, so we did that and it fixed 1433, however, 1434 still wasn't open. I installed a 'temp' instance to try to get it to fix the 1434 port, but it still doesn't work. I'm googling it, but not finding many answers. The SQL Browser service starts just fine! Any help? |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-01-29 : 09:26:46
|
| I thought SQL (out of the box) only listened on 1433 - if you need it to listen on 1434 I reckon you'll have to add that. |
 |
|
|
bshannon
Starting Member
3 Posts |
Posted - 2010-01-29 : 09:33:12
|
| The SQL Browser service binds to 1434 UDP. For some reason mine stopped doing that. |
|
|
|
|
|
|
SQL Browser no longer bound to 1434?