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 |
scottpt
Posting Yak Master
186 Posts |
Posted - 2011-02-04 : 14:11:38
|
Windows firewall is off on both server and machine.Change port to 24559.I can connect to SQLSERVERNAME,24559.I cannot connect to SQLSERVERNAME.Sql browser is running under a user account that is a sysadmin and in the administrator group.Reg looks fine.This is driving me nuts. I have done this before why does it not work now? |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
scottpt
Posting Yak Master
186 Posts |
Posted - 2011-02-04 : 14:20:37
|
Alias works also, but it would require touching over 2000 PCs |
 |
|
scottpt
Posting Yak Master
186 Posts |
Posted - 2011-02-04 : 14:21:43
|
Port Query also returns successfule when hittin UDP port 1434 |
 |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-02-04 : 15:18:43
|
quote: Originally posted by scottpt Alias works also, but it would require touching over 2000 PCs
No, you don't need to create the alias at every client. Use SQL Configuration manager. Or it can be done in Active Directory. |
 |
|
scottpt
Posting Yak Master
186 Posts |
Posted - 2011-02-04 : 15:42:00
|
The alias has top be on every client. HOw can you not touch all 2000+? |
 |
|
scottpt
Posting Yak Master
186 Posts |
Posted - 2011-02-07 : 09:23:27
|
It basically comes down to this SQL browser is working and returning the port. However SSMS does not recognized the port change. Also ADO 3.5 app using the SQL Server Native CLient 10 has the same problem. If I was using dynamic ports it works, but I have to put a hole in the firewall for this port, so dynamic is not a option. How can I get SQL to work with a static PORT and not have to specifically state that port, basically have the apps work with sql browser. |
 |
|
|
|
|