March 24, 2011 at 12:01 pm
I have a Server 2003 R2
SQL Server 2005 SP3 CU 11
Default Instance
Enabled Protocols:
TCP/IP
Remote Connections
Shared Memory
TCP/IP:
Enabled Yes
Keep Alive 30000
Listen All Yes
No Delay No
IP1 not enabled
IP2 not enabled
IPAll set to nothing in Dynamic Ports, TCP Port is non-standard port 1143x
SQL Browser is ON
Firewall not an issue this is all behind the firewall
Aliases: Yes (I tested this with and without the Alias)
Alias Name: MyServer
Server: MyServer
Protocol: tcp/ip
Parameter: 1143x
Connecting over SSMS with tcp:MyServer
When Named Pipes is Disabled I cannot connect without specifying the port number.
Why isn't SQL Browser identifying the port number, passing that to the client and the client then using that to connect as described by msdn explanation of how SQL Browser works?
I have tested this with and without the alias, with and without the browser, with the alias and without the browser, with the browser and without the alias and with both. Nothing worked except to specify the port.
What DOES work is tcp:MyServer from the local machine ... curious.
Any help and ideas is much appreciated!
Thanks!!
March 24, 2011 at 12:47 pm
Is the server firewalled off from the computer that is having problems connecting to it (without port number)?
Maybe a router/firewall in between the server and the desktop machine is not allowing UDP:1434 which is needed by the browser.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 24, 2011 at 2:43 pm
well I checked and there's no firewall but port 1434 isn't open or listening even though the browser is running...
ideas?
Thanks for your help!
March 24, 2011 at 2:45 pm
Is the windows firewall on the server disabled or running?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 24, 2011 at 3:20 pm
It is disabled.
If it helps I logged onto the server and did telnet localhost 1434 and it responded but it wouldn't respond when I did
telnet mesa 1434 from my client
March 24, 2011 at 3:23 pm
Does it matter if the service is running under:
NT AUTHORITY\NetworkService
March 24, 2011 at 3:38 pm
No - you should be able to see that port listening from remote and you should get a response when telnet to it. Something is blocking you from seeing that port from outside the server itself.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 24, 2011 at 3:54 pm
When I run netstat -a I don't see port 1434 listed on the server,
How can I tell what port it is running under?
March 24, 2011 at 4:03 pm
It's not configurable. Browser service is tied to UDP 1434. Port UDP:1434 has to be open
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 24, 2011 at 4:04 pm
Hmm , wonder why it doesn't show up when I netstat but I definately can telnet to it on the localhost.
Any ideas why I cannot telnet to the host using the servername with the port number?
Thanks again for your help!
March 25, 2011 at 10:22 am
This is still an issue if anyone has ideas...
I'd really like to get rid of my named pipes connections on that server without having to make all users change their connection files.
Thanks in advance for your help!
March 25, 2011 at 10:36 am
Do you have windows firewall on your client machine (the one that can't connect)?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 25, 2011 at 11:39 am
Yes but it is disabled. I can telnet to the SQL Server port, just not port 1434
March 25, 2011 at 11:41 am
K. Odd
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 25, 2011 at 1:36 pm
Ok, got it here,
SQL Browser runs under UDP port 1434 not TCP port. telnet doesn't work with UDP because there is no acknowledgement from UDP protocol.
So.. how I figured out what port/protocol was used:
http://msdn.microsoft.com/en-us/library/ms181087.aspx
then went to the server, did a netstat -a -o -n to see the ports and the process id, compared the process id (2368) for sqlbrowser.exe and see it is on
UDP 0.0.0.0:1434 *:* 2368
Still don't know why the browser won't connect the client to sql server using tcp protocol though, perhaps because it isn't using that protocol itself..
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply