May 14, 2008 at 8:11 pm
Hello, I have over 100 clients using MSDE 2000 with specific port setting. I cannot upgrade them to SQL 2005, because not being able to change port on 2005 and make it work. Port settings in 2005 actually get saved, but I no longer can connect to server unless I set port back 1433. What am I missing? Any help appreciated.
P.S. I am changing port settings on client and server together and it worked fine on 2000.
thank you, Paul.
May 14, 2008 at 8:35 pm
When you change the port in SQL 2005 you have to start the SQL Server Browser Service or you need to specify the port in your application's connection string.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 15, 2008 at 2:47 pm
i can think of two things:
open the port on th fire wall if any.
and make sure when connecting to sql server throw the Management Studio to choose this port, if u connect then the sql server is listenning to this port.
i dont mean to be stupped but have u restared the service after changing the port?
..>>..
MobashA
May 16, 2008 at 7:02 am
I have restarted server, i have opened port on router and firewall ( I have also disabled firewall), I have changed port while connecting to server. According Microsoft docs it should work (I am doing that for years in SQL 2000 wihout a single issue). I just want to know if anyone ever tried to connect using anything but 1433. As soon as I set back to 1433, works right away.
P.S. I am trying on LAN with no firewall as well as on WAN. It just wont work.
thanks anyway for suggestions.
May 16, 2008 at 9:22 pm
Have you verifies that the SQL Browser Service is running? Did you add the port to the connection string?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 17, 2008 at 9:19 am
When you change the port and then stop and restart SQL Server, bring up a command prompt and run the following command:
netstat -ano
Look to see if you have something listening on your newly specified port. If you're not on a cluster it should have an entry like 0.0.0.0:**port**
Using the -o tells you the PID, which you can match up in Task Manager. If you don't see that, then it means SQL Server isn't listening on that port for some reason, and this is usually documented in the SQL Server log as to why it couldn't start up.
K. Brian Kelley
@kbriankelley
May 17, 2008 at 2:35 pm
if i was using cluster dose this command will work?
cos we r going to change the port soon, and i dont wont to face unexpected problems.
..>>..
MobashA
May 17, 2008 at 5:55 pm
If you're on a cluster, you must first determine which physical node is hosting the virtual node. Then run it on that physical node.
K. Brian Kelley
@kbriankelley
May 17, 2008 at 9:10 pm
sarkisp (5/16/2008)
I have restarted server, i have opened port on router and firewall ( I have also disabled firewall), I have changed port while connecting to server. According Microsoft docs it should work (I am doing that for years in SQL 2000 wihout a single issue). I just want to know if anyone ever tried to connect using anything but 1433. As soon as I set back to 1433, works right away.P.S. I am trying on LAN with no firewall as well as on WAN. It just wont work.
thanks anyway for suggestions.
Yep, I do it all the time on SQL2005.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
May 18, 2008 at 10:23 am
i have verified that browser is running. i am not even trying to change code because i cannot even connect using SQL Management Studio. I just tried today again. worked only as I set everything back to 1433.
May 18, 2008 at 10:26 am
netstat shows following:
TCP 0.0.0.0:4605 LISTENING 3912
I guess thats where the problem is.
May 18, 2008 at 11:45 am
if u stop the sql server, change the port, start the service, then go to the event log u then can make sure if the sql server is listening to the port u have chosen.
..>>..
MobashA
May 19, 2008 at 3:08 pm
The port change only takes effect on a SQL Server restart. The value is actually stored in the registry and the SQL Server service only reads it when the service restarts. That's why you get the warning saying the value won't take effect until the service is restarted.
With that said, was 4605 the port you set SQL Server to listen on? If it is and SQL Server is not responding, check in Task Manager on that server to see what the PID corresponds to. In the example you gave, it was 3912 that you're interested in matching up. However, you'll want to make the comparison at the time you run the netstat -ano command.
K. Brian Kelley
@kbriankelley
May 19, 2008 at 5:49 pm
well, i did all the things as I mentioned before many times. we are talking about basics here, obviously we cannot find a good explanation of what's really going on. I mean restarting server, checking ports, checking firewalls, networks, connections, etc etc. was exist in previous versions, right? and I am working with SQL since version 4.2. I did all that stuff, trust me. appreciate everyones help.
May 21, 2008 at 7:52 am
Are there any interesting events in either the SQL Server error log or the system's application event log?
K. Brian Kelley
@kbriankelley
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply