How to change SQL Server Browser service back to port 1434

Gurus,
Running SQL Server 2005 SP2. The SQL Server Browser service but since I am
running on dynamic ports it is not listening on 1434. In fact, looking thru
Configuration Manager I am not able to tell what port it is listening on or
how to change it back to 1434. Any ideas?
--
SpinSQL Browser always listens to 1434. It is the database engine that might be static or dynamic.
Browser is only there to translate between instance name and port number.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Spin" <Spin@.invalid.com> wrote in message news:67rgfkF2or7t6U1@.mid.individual.net...
> Gurus,
> Running SQL Server 2005 SP2. The SQL Server Browser service but since I am running on dynamic
> ports it is not listening on 1434. In fact, looking thru Configuration Manager I am not able to
> tell what port it is listening on or how to change it back to 1434. Any ideas?
> --
> Spin
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:89DD7ACA-DAB4-40D4-987F-5C6CA9B329B1@.microsoft.com...
> SQL Browser always listens to 1434. It is the database engine that might
> be static or dynamic. Browser is only there to translate between instance
> name and port number.
On my SQL Server I opened a CMP prompt a 'Netsat' command returned nothing
listening on port 1434. SQL Browser service IS running.|||"Spin" <Spin@.invalid.com> wrote in message
news:67ro9qF2q0vlvU1@.mid.individual.net...
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:89DD7ACA-DAB4-40D4-987F-5C6CA9B329B1@.microsoft.com...
> On my SQL Server I opened a CMP prompt a 'Netsat' command returned nothing
> listening on port 1434. SQL Browser service IS running.
Disregard. I've done some reading and the SQL Browser service listens on a
UDP port, netstat only shows TCP ports on which connections are either
established or the server is listening. I have to figure out what UDP ports
are being listened. This may be a bit more difficult.|||"Spin" <Spin@.invalid.com> wrote in message
news:67rrf3F2q34siU1@.mid.individual.net...
> "Spin" <Spin@.invalid.com> wrote in message
> news:67ro9qF2q0vlvU1@.mid.individual.net...
> Disregard. I've done some reading and the SQL Browser service listens on
> a UDP port, netstat only shows TCP ports on which connections are either
> established or the server is listening. I have to figure out what UDP
> ports are being listened. This may be a bit more difficult.
Using TCPView.exe from Microsoft, I can clearly see now on at least one SQL
Server that the SQL Broswer service is listening on UDP 1434!
Tibor, am I correct in believing that the SQL Browser listening port CANNOT
be changed?|||> Tibor, am I correct in believing that the SQL Browser listening port CANNOT be changed?
Yes, that is the way I understand it. The whole purpose of SQL Browser is to be a fixed port. This
is so that outsiders can query it (that specific port) for the port number for an instance name.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Spin" <Spin@.invalid.com> wrote in message news:67rtnuF2qnt8iU1@.mid.individual.net...
> "Spin" <Spin@.invalid.com> wrote in message news:67rrf3F2q34siU1@.mid.individual.net...
>> "Spin" <Spin@.invalid.com> wrote in message news:67ro9qF2q0vlvU1@.mid.individual.net...
>> Disregard. I've done some reading and the SQL Browser service listens on a UDP port, netstat
>> only shows TCP ports on which connections are either established or the server is listening. I
>> have to figure out what UDP ports are being listened. This may be a bit more difficult.
> Using TCPView.exe from Microsoft, I can clearly see now on at least one SQL Server that the SQL
> Broswer service is listening on UDP 1434!
> Tibor, am I correct in believing that the SQL Browser listening port CANNOT be changed?
>
>|||You can use netstat to show UDP ports that are being listened on. Run the
following:
cmd>netstat -ano
One of UDP rows in the result will have port 1434. Find the the PID, and run
tasklist to confirm that the PID is sql browser.
Linchi
"Spin" wrote:
> "Spin" <Spin@.invalid.com> wrote in message
> news:67ro9qF2q0vlvU1@.mid.individual.net...
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> > in message news:89DD7ACA-DAB4-40D4-987F-5C6CA9B329B1@.microsoft.com...
> > On my SQL Server I opened a CMP prompt a 'Netsat' command returned nothing
> > listening on port 1434. SQL Browser service IS running.
> Disregard. I've done some reading and the SQL Browser service listens on a
> UDP port, netstat only shows TCP ports on which connections are either
> established or the server is listening. I have to figure out what UDP ports
> are being listened. This may be a bit more difficult.
>
>sql