connection failed port 25

I have two w2k3 SP1 server setup with smtp for relay. Both servers are
pretty much a mirror of each other. Locally, I can telnet from one server
but not the other. When I tried to telnet locally from the servers with its
own local IP to port 25, I get connection failed to port 25. There is no
differences between the two servers except their IP.
There must be a differnece between them, did you try to portscan these
servers to see wheter the port is activated and listens. What dies
Netstat -a say ? Once we had an issue about port 25, becasue a virus scanner
was installed which blocked the port 25 to forbid open relays, perhaps this
could be a point.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"manoa" <manoa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:F8B1E423-3882-4A79-9077-113018F558D1@.microsoft.com...
>I have two w2k3 SP1 server setup with smtp for relay. Both servers are
> pretty much a mirror of each other. Locally, I can telnet from one server
> but not the other. When I tried to telnet locally from the servers with
> its
> own local IP to port 25, I get connection failed to port 25. There is no
> differences between the two servers except their IP.

connection failed port 25

I have two w2k3 SP1 server setup with smtp for relay. Both servers are
pretty much a mirror of each other. Locally, I can telnet from one server
but not the other. When I tried to telnet locally from the servers with its
own local IP to port 25, I get connection failed to port 25. There is no
differences between the two servers except their IP.There must be a differnece between them, did you try to portscan these
servers to see wheter the port is activated and listens. What dies
Netstat -a say ? Once we had an issue about port 25, becasue a virus scanner
was installed which blocked the port 25 to forbid open relays, perhaps this
could be a point.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"manoa" <manoa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:F8B1E423-3882-4A79-9077-113018F558D1@.microsoft.com...
>I have two w2k3 SP1 server setup with smtp for relay. Both servers are
> pretty much a mirror of each other. Locally, I can telnet from one server
> but not the other. When I tried to telnet locally from the servers with
> its
> own local IP to port 25, I get connection failed to port 25. There is no
> differences between the two servers except their IP.

connection failed port 25

I have two w2k3 SP1 server setup with smtp for relay. Both servers are
pretty much a mirror of each other. Locally, I can telnet from one server
but not the other. When I tried to telnet locally from the servers with its
own local IP to port 25, I get connection failed to port 25. There is no
differences between the two servers except their IP.There must be a differnece between them, did you try to portscan these
servers to see wheter the port is activated and listens. What dies
Netstat -a say ? Once we had an issue about port 25, becasue a virus scanner
was installed which blocked the port 25 to forbid open relays, perhaps this
could be a point.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"manoa" <manoa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:F8B1E423-3882-4A79-9077-113018F558D1@.microsoft.com...
>I have two w2k3 SP1 server setup with smtp for relay. Both servers are
> pretty much a mirror of each other. Locally, I can telnet from one server
> but not the other. When I tried to telnet locally from the servers with
> its
> own local IP to port 25, I get connection failed to port 25. There is no
> differences between the two servers except their IP.

Connection broken

We have added a new firewall to our network and now I keep getting my
connection dropped when running from home. Port 1433 is open.
I am connecting via a VPN and it was working fine. Nothing has changed in
this respect. If I disconnect my Firewall at home and go to the internet
directly, I have no problems (but this firewall worked fine before and does
now sporadically).
Now, however, I can connect fine but my queries give me the following
message after about 30 seconds:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
This says I was connected, but now the Connection is broken.
If I were to give it an invalid command such as "who_is", I do get the
following results:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'who_is'.
This comes directly from Sql Server, so I know the my machine at home can
talk to the Server fine.
Why am I not able to query without losing connection?
Thanks,
Tom
I found out what is happening, but not why.
Apparently, Sql Server using UDP service 17 port 1434 for something.
I looked at my firewall settings and it is dropping my packets because they
are fragmented. It was confusing at first, because it worked fine without
the firewall. But what must be happening is that the data is being passed
on 1433 (which I would expect) and since there is no firewall to strip bad
packets it lets the fragmented packet through. For some reason, because of
this packet the connection is dropped (not sure what constitutes a dropped
connection) so I assume the actual response hasn't been sent yet and now it
can't send it because the connection is now gone (I think).
Anyone know why this is happening or what this port (1434) is used for? I
knew about 1433, but this is the first I had heard about 1434.
Thanks,
Tom
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
> We have added a new firewall to our network and now I keep getting my
> connection dropped when running from home. Port 1433 is open.
> I am connecting via a VPN and it was working fine. Nothing has changed in
> this respect. If I disconnect my Firewall at home and go to the internet
> directly, I have no problems (but this firewall worked fine before and
> does now sporadically).
> Now, however, I can connect fine but my queries give me the following
> message after about 30 seconds:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> This says I was connected, but now the Connection is broken.
> If I were to give it an invalid command such as "who_is", I do get the
> following results:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'who_is'.
> This comes directly from Sql Server, so I know the my machine at home can
> talk to the Server fine.
> Why am I not able to query without losing connection?
> Thanks,
> Tom
>
|||UDP 1434 is the SQL Server Resolution Service used to find
what port number a named instance is listening on.
You can find more information in the following articles:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
How to use static and dynamic port allocation in SQL Server
2000
http://support.microsoft.com/?id=823938
-Sue
On Fri, 10 Mar 2006 08:41:32 -0800, "tshad"
<tscheiderich@.ftsolutions.com> wrote:

>I found out what is happening, but not why.
>Apparently, Sql Server using UDP service 17 port 1434 for something.
>I looked at my firewall settings and it is dropping my packets because they
>are fragmented. It was confusing at first, because it worked fine without
>the firewall. But what must be happening is that the data is being passed
>on 1433 (which I would expect) and since there is no firewall to strip bad
>packets it lets the fragmented packet through. For some reason, because of
>this packet the connection is dropped (not sure what constitutes a dropped
>connection) so I assume the actual response hasn't been sent yet and now it
>can't send it because the connection is now gone (I think).
>Anyone know why this is happening or what this port (1434) is used for? I
>knew about 1433, but this is the first I had heard about 1434.
>Thanks,
>Tom
>"tshad" <tscheiderich@.ftsolutions.com> wrote in message
>news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
>

Connection broken

We have added a new firewall to our network and now I keep getting my
connection dropped when running from home. Port 1433 is open.
I am connecting via a VPN and it was working fine. Nothing has changed in
this respect. If I disconnect my Firewall at home and go to the internet
directly, I have no problems (but this firewall worked fine before and does
now sporadically).
Now, however, I can connect fine but my queries give me the following
message after about 30 seconds:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
This says I was connected, but now the Connection is broken.
If I were to give it an invalid command such as "who_is", I do get the
following results:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'who_is'.
This comes directly from Sql Server, so I know the my machine at home can
talk to the Server fine.
Why am I not able to query without losing connection?
Thanks,
TomI found out what is happening, but not why.
Apparently, Sql Server using UDP service 17 port 1434 for something.
I looked at my firewall settings and it is dropping my packets because they
are fragmented. It was confusing at first, because it worked fine without
the firewall. But what must be happening is that the data is being passed
on 1433 (which I would expect) and since there is no firewall to strip bad
packets it lets the fragmented packet through. For some reason, because of
this packet the connection is dropped (not sure what constitutes a dropped
connection) so I assume the actual response hasn't been sent yet and now it
can't send it because the connection is now gone (I think).
Anyone know why this is happening or what this port (1434) is used for? I
knew about 1433, but this is the first I had heard about 1434.
Thanks,
Tom
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
> We have added a new firewall to our network and now I keep getting my
> connection dropped when running from home. Port 1433 is open.
> I am connecting via a VPN and it was working fine. Nothing has changed in
> this respect. If I disconnect my Firewall at home and go to the internet
> directly, I have no problems (but this firewall worked fine before and
> does now sporadically).
> Now, however, I can connect fine but my queries give me the following
> message after about 30 seconds:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> This says I was connected, but now the Connection is broken.
> If I were to give it an invalid command such as "who_is", I do get the
> following results:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'who_is'.
> This comes directly from Sql Server, so I know the my machine at home can
> talk to the Server fine.
> Why am I not able to query without losing connection?
> Thanks,
> Tom
>|||UDP 1434 is the SQL Server Resolution Service used to find
what port number a named instance is listening on.
You can find more information in the following articles:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
How to use static and dynamic port allocation in SQL Server
2000
http://support.microsoft.com/?id=823938
-Sue
On Fri, 10 Mar 2006 08:41:32 -0800, "tshad"
<tscheiderich@.ftsolutions.com> wrote:
>I found out what is happening, but not why.
>Apparently, Sql Server using UDP service 17 port 1434 for something.
>I looked at my firewall settings and it is dropping my packets because they
>are fragmented. It was confusing at first, because it worked fine without
>the firewall. But what must be happening is that the data is being passed
>on 1433 (which I would expect) and since there is no firewall to strip bad
>packets it lets the fragmented packet through. For some reason, because of
>this packet the connection is dropped (not sure what constitutes a dropped
>connection) so I assume the actual response hasn't been sent yet and now it
>can't send it because the connection is now gone (I think).
>Anyone know why this is happening or what this port (1434) is used for? I
>knew about 1433, but this is the first I had heard about 1434.
>Thanks,
>Tom
>"tshad" <tscheiderich@.ftsolutions.com> wrote in message
>news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
>> We have added a new firewall to our network and now I keep getting my
>> connection dropped when running from home. Port 1433 is open.
>> I am connecting via a VPN and it was working fine. Nothing has changed in
>> this respect. If I disconnect my Firewall at home and go to the internet
>> directly, I have no problems (but this firewall worked fine before and
>> does now sporadically).
>> Now, however, I can connect fine but my queries give me the following
>> message after about 30 seconds:
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
>> (CheckforData()).
>> Server: Msg 11, Level 16, State 1, Line 0
>> General network error. Check your network documentation.
>> Connection Broken
>> This says I was connected, but now the Connection is broken.
>> If I were to give it an invalid command such as "who_is", I do get the
>> following results:
>> Server: Msg 2812, Level 16, State 62, Line 1
>> Could not find stored procedure 'who_is'.
>> This comes directly from Sql Server, so I know the my machine at home can
>> talk to the Server fine.
>> Why am I not able to query without losing connection?
>> Thanks,
>> Tom
>

Connection broken

We have added a new firewall to our network and now I keep getting my
connection dropped when running from home. Port 1433 is open.
I am connecting via a VPN and it was working fine. Nothing has changed in
this respect. If I disconnect my Firewall at home and go to the internet
directly, I have no problems (but this firewall worked fine before and does
now sporadically).
Now, however, I can connect fine but my queries give me the following
message after about 30 seconds:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForD
ata
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
This says I was connected, but now the Connection is broken.
If I were to give it an invalid command such as "who_is", I do get the
following results:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'who_is'.
This comes directly from Sql Server, so I know the my machine at home can
talk to the Server fine.
Why am I not able to query without losing connection?
Thanks,
TomI found out what is happening, but not why.
Apparently, Sql Server using UDP service 17 port 1434 for something.
I looked at my firewall settings and it is dropping my packets because they
are fragmented. It was confusing at first, because it worked fine without
the firewall. But what must be happening is that the data is being passed
on 1433 (which I would expect) and since there is no firewall to strip bad
packets it lets the fragmented packet through. For some reason, because of
this packet the connection is dropped (not sure what constitutes a dropped
connection) so I assume the actual response hasn't been sent yet and now it
can't send it because the connection is now gone (I think).
Anyone know why this is happening or what this port (1434) is used for? I
knew about 1433, but this is the first I had heard about 1434.
Thanks,
Tom
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
> We have added a new firewall to our network and now I keep getting my
> connection dropped when running from home. Port 1433 is open.
> I am connecting via a VPN and it was working fine. Nothing has changed in
> this respect. If I disconnect my Firewall at home and go to the internet
> directly, I have no problems (but this firewall worked fine before and
> does now sporadically).
> Now, however, I can connect fine but my queries give me the following
> message after about 30 seconds:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckFo
rData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> This says I was connected, but now the Connection is broken.
> If I were to give it an invalid command such as "who_is", I do get the
> following results:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'who_is'.
> This comes directly from Sql Server, so I know the my machine at home can
> talk to the Server fine.
> Why am I not able to query without losing connection?
> Thanks,
> Tom
>|||UDP 1434 is the SQL Server Resolution Service used to find
what port number a named instance is listening on.
You can find more information in the following articles:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
How to use static and dynamic port allocation in SQL Server
2000
http://support.microsoft.com/?id=823938
-Sue
On Fri, 10 Mar 2006 08:41:32 -0800, "tshad"
<tscheiderich@.ftsolutions.com> wrote:

>I found out what is happening, but not why.
>Apparently, Sql Server using UDP service 17 port 1434 for something.
>I looked at my firewall settings and it is dropping my packets because they
>are fragmented. It was confusing at first, because it worked fine without
>the firewall. But what must be happening is that the data is being passed
>on 1433 (which I would expect) and since there is no firewall to strip bad
>packets it lets the fragmented packet through. For some reason, because of
>this packet the connection is dropped (not sure what constitutes a dropped
>connection) so I assume the actual response hasn't been sent yet and now it
>can't send it because the connection is now gone (I think).
>Anyone know why this is happening or what this port (1434) is used for? I
>knew about 1433, but this is the first I had heard about 1434.
>Thanks,
>Tom
>"tshad" <tscheiderich@.ftsolutions.com> wrote in message
>news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
>

Connecting without SQL Browser

I'm unable to connect to my named instance of SQL Server 2005 when the
Browser service isn't running on the server.
I do specify the port that the SQL Server instance is listening to in the
connection string, as in SERVER:PORT
Is it impossible to connect to an instance of SQL Server when the browser
isn't running? I have verified that the server will accept remote
connections, and I can connect as soon as I start the browser.Hello,
You may want to check the SQL 2005 process ID in task manager, and then run
the following command to see if the PID is listening on the proper port
netstat -aon
If it is OK, please try to telnet the port from client:
telnet <server name> <port number>
If not, it seems there is firewall blocking the port. Please check
Windows/third party firewall on the server to test
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==>X-WBNR-Posting-Host: 84.147.139.248
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>Subject: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 00:18:27 -0800
>Lines: 7
>Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I'm unable to connect to my named instance of SQL Server 2005 when the
>Browser service isn't running on the server.
>I do specify the port that the SQL Server instance is listening to in the
>connection string, as in SERVER:PORT
>Is it impossible to connect to an instance of SQL Server when the browser
>isn't running? I have verified that the server will accept remote
>connections, and I can connect as soon as I start the browser.
>|||From the SQL Server log:
Server process ID is 1552
Server is listening on [ 'any' <ipv4> 1743].
Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\S5 ].
Server local connection provider is ready to accept connection on [
\\.\pipe\MSSQL$S5\sql\query ].
Server is listening on [ 127.0.0.1 <ipv4> 1744].
Dedicated admin connection support was established for listening locally on
port 1744.
SQL Server is now ready for client connections. This is an informational
message; no user action is required.
From netstat -aon
TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
Connecting with Telnet from the client gives "Connect failed", also when the
Browser is started.
"Peter Yang [MSFT]" wrote:
> Hello,
> You may want to check the SQL 2005 process ID in task manager, and then run
> the following command to see if the PID is listening on the proper port
> netstat -aon
> If it is OK, please try to telnet the port from client:
> telnet <server name> <port number>
> If not, it seems there is firewall blocking the port. Please check
> Windows/third party firewall on the server to test
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> >Thread-Topic: Connecting without SQL Browser
> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==> >X-WBNR-Posting-Host: 84.147.139.248
> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
> >Subject: Connecting without SQL Browser
> >Date: Wed, 8 Mar 2006 00:18:27 -0800
> >Lines: 7
> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
> >Newsgroups: microsoft.public.sqlserver.server
> >Path: TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >X-Tomcat-NG: microsoft.public.sqlserver.server
> >
> >I'm unable to connect to my named instance of SQL Server 2005 when the
> >Browser service isn't running on the server.
> >I do specify the port that the SQL Server instance is listening to in the
> >connection string, as in SERVER:PORT
> >Is it impossible to connect to an instance of SQL Server when the browser
> >isn't running? I have verified that the server will accept remote
> >connections, and I can connect as soon as I start the browser.
> >
>|||Hello,
Apparently you have firewall on the server blocks port 1552. Please
temporarily disable firewalls to test the situation. If it works, you could
open port on firwall to solve the problem.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==>X-WBNR-Posting-Host: 84.147.139.248
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 04:00:29 -0800
>Lines: 87
>Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>From the SQL Server log:
>Server process ID is 1552
>Server is listening on [ 'any' <ipv4> 1743].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\SQLLocal\S5 ].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\MSSQL$S5\sql\query ].
>Server is listening on [ 127.0.0.1 <ipv4> 1744].
>Dedicated admin connection support was established for listening locally
on
>port 1744.
>SQL Server is now ready for client connections. This is an informational
>message; no user action is required.
>From netstat -aon
>TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
>TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
>Connecting with Telnet from the client gives "Connect failed", also when
the
>Browser is started.
>
>"Peter Yang [MSFT]" wrote:
>> Hello,
>> You may want to check the SQL 2005 process ID in task manager, and then
run
>> the following command to see if the PID is listening on the proper port
>> netstat -aon
>> If it is OK, please try to telnet the port from client:
>> telnet <server name> <port number>
>> If not, it seems there is firewall blocking the port. Please check
>> Windows/third party firewall on the server to test
>> Best Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================>>
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --
>> >Thread-Topic: Connecting without SQL Browser
>> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==>> >X-WBNR-Posting-Host: 84.147.139.248
>> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>> >Subject: Connecting without SQL Browser
>> >Date: Wed, 8 Mar 2006 00:18:27 -0800
>> >Lines: 7
>> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>> >Newsgroups: microsoft.public.sqlserver.server
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >X-Tomcat-NG: microsoft.public.sqlserver.server
>> >
>> >I'm unable to connect to my named instance of SQL Server 2005 when the
>> >Browser service isn't running on the server.
>> >I do specify the port that the SQL Server instance is listening to in
the
>> >connection string, as in SERVER:PORT
>> >Is it impossible to connect to an instance of SQL Server when the
browser
>> >isn't running? I have verified that the server will accept remote
>> >connections, and I can connect as soon as I start the browser.
>> >
>>
>|||1552 is the process id of sql server in the example.
"Peter Yang [MSFT]" wrote:
> Hello,
> Apparently you have firewall on the server blocks port 1552. Please
> temporarily disable firewalls to test the situation. If it works, you could
> open port on firwall to solve the problem.
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> >Thread-Topic: Connecting without SQL Browser
> >thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==> >X-WBNR-Posting-Host: 84.147.139.248
> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
> >References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
> <ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
> >Subject: RE: Connecting without SQL Browser
> >Date: Wed, 8 Mar 2006 04:00:29 -0800
> >Lines: 87
> >Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
> >Newsgroups: microsoft.public.sqlserver.server
> >Path: TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >X-Tomcat-NG: microsoft.public.sqlserver.server
> >
> >From the SQL Server log:
> >Server process ID is 1552
> >Server is listening on [ 'any' <ipv4> 1743].
> >Server local connection provider is ready to accept connection on [
> >\\.\pipe\SQLLocal\S5 ].
> >Server local connection provider is ready to accept connection on [
> >\\.\pipe\MSSQL$S5\sql\query ].
> >Server is listening on [ 127.0.0.1 <ipv4> 1744].
> >Dedicated admin connection support was established for listening locally
> on
> >port 1744.
> >SQL Server is now ready for client connections. This is an informational
> >message; no user action is required.
> >
> >From netstat -aon
> >TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
> >TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
> >
> >Connecting with Telnet from the client gives "Connect failed", also when
> the
> >Browser is started.
> >
> >
> >
> >"Peter Yang [MSFT]" wrote:
> >
> >> Hello,
> >>
> >> You may want to check the SQL 2005 process ID in task manager, and then
> run
> >> the following command to see if the PID is listening on the proper port
> >>
> >> netstat -aon
> >>
> >> If it is OK, please try to telnet the port from client:
> >>
> >> telnet <server name> <port number>
> >>
> >> If not, it seems there is firewall blocking the port. Please check
> >> Windows/third party firewall on the server to test
> >>
> >> Best Regards,
> >>
> >> Peter Yang
> >> MCSE2000/2003, MCSA, MCDBA
> >> Microsoft Online Partner Support
> >>
> >> When responding to posts, please "Reply to Group" via your newsreader so
> >> that others may learn and benefit from your issue.
> >>
> >> =====================================================> >>
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >>
> >>
> >> --
> >> >Thread-Topic: Connecting without SQL Browser
> >> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==> >> >X-WBNR-Posting-Host: 84.147.139.248
> >> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
> >> >Subject: Connecting without SQL Browser
> >> >Date: Wed, 8 Mar 2006 00:18:27 -0800
> >> >Lines: 7
> >> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
> >> >Newsgroups: microsoft.public.sqlserver.server
> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> >X-Tomcat-NG: microsoft.public.sqlserver.server
> >> >
> >> >I'm unable to connect to my named instance of SQL Server 2005 when the
> >> >Browser service isn't running on the server.
> >> >I do specify the port that the SQL Server instance is listening to in
> the
> >> >connection string, as in SERVER:PORT
> >> >Is it impossible to connect to an instance of SQL Server when the
> browser
> >> >isn't running? I have verified that the server will accept remote
> >> >connections, and I can connect as soon as I start the browser.
> >> >
> >>
> >>
> >
>|||Hello Pat,
Sorry. My typo. Server port 1743 shall be opened by firewall. Also, client
network shall be configured to 1743 as well.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZMNgMtU2vKHeRwTEqMU7ZbMxx2xA==>X-WBNR-Posting-Host: 84.147.154.98
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
<7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
<PBj2TK1QGHA.6216@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Connecting without SQL Browser
>Date: Mon, 20 Mar 2006 07:50:29 -0800
>Lines: 146
>Message-ID: <B93CC259-A26F-444C-93C7-1155FDC5310C@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:424932
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>1552 is the process id of sql server in the example.
>"Peter Yang [MSFT]" wrote:
>> Hello,
>> Apparently you have firewall on the server blocks port 1552. Please
>> temporarily disable firewalls to test the situation. If it works, you
could
>> open port on firwall to solve the problem.
>> Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --
>> >Thread-Topic: Connecting without SQL Browser
>> >thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==>> >X-WBNR-Posting-Host: 84.147.139.248
>> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>> >References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>> <ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
>> >Subject: RE: Connecting without SQL Browser
>> >Date: Wed, 8 Mar 2006 04:00:29 -0800
>> >Lines: 87
>> >Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>> >Newsgroups: microsoft.public.sqlserver.server
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >X-Tomcat-NG: microsoft.public.sqlserver.server
>> >
>> >From the SQL Server log:
>> >Server process ID is 1552
>> >Server is listening on [ 'any' <ipv4> 1743].
>> >Server local connection provider is ready to accept connection on [
>> >\\.\pipe\SQLLocal\S5 ].
>> >Server local connection provider is ready to accept connection on [
>> >\\.\pipe\MSSQL$S5\sql\query ].
>> >Server is listening on [ 127.0.0.1 <ipv4> 1744].
>> >Dedicated admin connection support was established for listening
locally
>> on
>> >port 1744.
>> >SQL Server is now ready for client connections. This is an
informational
>> >message; no user action is required.
>> >
>> >From netstat -aon
>> >TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
>> >TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
>> >
>> >Connecting with Telnet from the client gives "Connect failed", also
when
>> the
>> >Browser is started.
>> >
>> >
>> >
>> >"Peter Yang [MSFT]" wrote:
>> >
>> >> Hello,
>> >>
>> >> You may want to check the SQL 2005 process ID in task manager, and
then
>> run
>> >> the following command to see if the PID is listening on the proper
port
>> >>
>> >> netstat -aon
>> >>
>> >> If it is OK, please try to telnet the port from client:
>> >>
>> >> telnet <server name> <port number>
>> >>
>> >> If not, it seems there is firewall blocking the port. Please check
>> >> Windows/third party firewall on the server to test
>> >>
>> >> Best Regards,
>> >>
>> >> Peter Yang
>> >> MCSE2000/2003, MCSA, MCDBA
>> >> Microsoft Online Partner Support
>> >>
>> >> When responding to posts, please "Reply to Group" via your newsreader
so
>> >> that others may learn and benefit from your issue.
>> >>
>> >> =====================================================>> >>
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> >>
>> >>
>> >> --
>> >> >Thread-Topic: Connecting without SQL Browser
>> >> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==>> >> >X-WBNR-Posting-Host: 84.147.139.248
>> >> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>> >> >Subject: Connecting without SQL Browser
>> >> >Date: Wed, 8 Mar 2006 00:18:27 -0800
>> >> >Lines: 7
>> >> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>> >> >Content-Transfer-Encoding: 7bit
>> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >Content-Class: urn:content-classes:message
>> >> >Importance: normal
>> >> >Priority: normal
>> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>> >> >Newsgroups: microsoft.public.sqlserver.server
>> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> >X-Tomcat-NG: microsoft.public.sqlserver.server
>> >> >
>> >> >I'm unable to connect to my named instance of SQL Server 2005 when
the
>> >> >Browser service isn't running on the server.
>> >> >I do specify the port that the SQL Server instance is listening to
in
>> the
>> >> >connection string, as in SERVER:PORT
>> >> >Is it impossible to connect to an instance of SQL Server when the
>> browser
>> >> >isn't running? I have verified that the server will accept remote
>> >> >connections, and I can connect as soon as I start the browser.
>> >> >
>> >>
>> >>
>> >
>>
>

Connecting without SQL Browser

I'm unable to connect to my named instance of SQL Server 2005 when the
Browser service isn't running on the server.
I do specify the port that the SQL Server instance is listening to in the
connection string, as in SERVER:PORT
Is it impossible to connect to an instance of SQL Server when the browser
isn't running? I have verified that the server will accept remote
connections, and I can connect as soon as I start the browser.Hello,
You may want to check the SQL 2005 process ID in task manager, and then run
the following command to see if the PID is listening on the proper port
netstat -aon
If it is OK, please try to telnet the port from client:
telnet <server name> <port number>
If not, it seems there is firewall blocking the port. Please check
Windows/third party firewall on the server to test
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==
>X-WBNR-Posting-Host: 84.147.139.248
>From: examnotes <pat@.online.nospam>
>Subject: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 00:18:27 -0800
>Lines: 7
>Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I'm unable to connect to my named instance of SQL Server 2005 when the
>Browser service isn't running on the server.
>I do specify the port that the SQL Server instance is listening to in the
>connection string, as in SERVER:PORT
>Is it impossible to connect to an instance of SQL Server when the browser
>isn't running? I have verified that the server will accept remote
>connections, and I can connect as soon as I start the browser.
>|||From the SQL Server log:
Server process ID is 1552
Server is listening on [ 'any' <ipv4> 1743].
Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\S5 ].
Server local connection provider is ready to accept connection on [
\\.\pipe\MSSQL$S5\sql\query ].
Server is listening on [ 127.0.0.1 <ipv4> 1744].
Dedicated admin connection support was established for listening locally on
port 1744.
SQL Server is now ready for client connections. This is an informational
message; no user action is required.
From netstat -aon
TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
Connecting with Telnet from the client gives "Connect failed", also when the
Browser is started.
"Peter Yang [MSFT]" wrote:

> Hello,
> You may want to check the SQL 2005 process ID in task manager, and then ru
n
> the following command to see if the PID is listening on the proper port
> netstat -aon
> If it is OK, please try to telnet the port from client:
> telnet <server name> <port number>
> If not, it seems there is firewall blocking the port. Please check
> Windows/third party firewall on the server to test
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> --
>|||Hello,
Apparently you have firewall on the server blocks port 1552. Please
temporarily disable firewalls to test the situation. If it works, you could
open port on firwall to solve the problem.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==
>X-WBNR-Posting-Host: 84.147.139.248
>From: examnotes <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 04:00:29 -0800
>Lines: 87
>Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>From the SQL Server log:
>Server process ID is 1552
>Server is listening on [ 'any' <ipv4> 1743].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\SQLLocal\S5 ].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\MSSQL$S5\sql\query ].
>Server is listening on [ 127.0.0.1 <ipv4> 1744].
>Dedicated admin connection support was established for listening locally
on
>port 1744.
>SQL Server is now ready for client connections. This is an informational
>message; no user action is required.
>From netstat -aon
>TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
>TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
>Connecting with Telnet from the client gives "Connect failed", also when
the
>Browser is started.
>
>"Peter Yang [MSFT]" wrote:
>
run[vbcol=seagreen]
rights.[vbcol=seagreen]
the[vbcol=seagreen]
browser[vbcol=seagreen]
>|||1552 is the process id of sql server in the example.
"Peter Yang [MSFT]" wrote:

> Hello,
> Apparently you have firewall on the server blocks port 1552. Please
> temporarily disable firewalls to test the situation. If it works, you coul
d
> open port on firwall to solve the problem.
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> --
> <ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
> on
> the
> run
> rights.
> the
> browser
>|||Hello Pat,
Sorry. My typo. Server port 1743 shall be opened by firewall. Also, client
network shall be configured to 1743 as well.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZMNgMtU2vKHeRwTEqMU7ZbMxx2xA==
>X-WBNR-Posting-Host: 84.147.154.98
>From: examnotes <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
<7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
<PBj2TK1QGHA.6216@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Connecting without SQL Browser
>Date: Mon, 20 Mar 2006 07:50:29 -0800
>Lines: 146
>Message-ID: <B93CC259-A26F-444C-93C7-1155FDC5310C@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:424932
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>1552 is the process id of sql server in the example.
>"Peter Yang [MSFT]" wrote:
>
could[vbcol=seagreen]
rights.[vbcol=seagreen]
locally[vbcol=seagreen]
informational[vbcol=seagreen]
when[vbcol=seagreen]
then[vbcol=seagreen]
port[vbcol=seagreen]
so[vbcol=seagreen]
the[vbcol=seagreen]
in[vbcol=seagreen]
>

Connecting without SQL Browser

I'm unable to connect to my named instance of SQL Server 2005 when the
Browser service isn't running on the server.
I do specify the port that the SQL Server instance is listening to in the
connection string, as in SERVER:PORT
Is it impossible to connect to an instance of SQL Server when the browser
isn't running? I have verified that the server will accept remote
connections, and I can connect as soon as I start the browser.
Hello,
You may want to check the SQL 2005 process ID in task manager, and then run
the following command to see if the PID is listening on the proper port
netstat -aon
If it is OK, please try to telnet the port from client:
telnet <server name> <port number>
If not, it seems there is firewall blocking the port. Please check
Windows/third party firewall on the server to test
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==
>X-WBNR-Posting-Host: 84.147.139.248
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>Subject: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 00:18:27 -0800
>Lines: 7
>Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I'm unable to connect to my named instance of SQL Server 2005 when the
>Browser service isn't running on the server.
>I do specify the port that the SQL Server instance is listening to in the
>connection string, as in SERVER:PORT
>Is it impossible to connect to an instance of SQL Server when the browser
>isn't running? I have verified that the server will accept remote
>connections, and I can connect as soon as I start the browser.
>
|||From the SQL Server log:
Server process ID is 1552
Server is listening on [ 'any' <ipv4> 1743].
Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\S5 ].
Server local connection provider is ready to accept connection on [
\\.\pipe\MSSQL$S5\sql\query ].
Server is listening on [ 127.0.0.1 <ipv4> 1744].
Dedicated admin connection support was established for listening locally on
port 1744.
SQL Server is now ready for client connections. This is an informational
message; no user action is required.
From netstat -aon
TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
Connecting with Telnet from the client gives "Connect failed", also when the
Browser is started.
"Peter Yang [MSFT]" wrote:

> Hello,
> You may want to check the SQL 2005 process ID in task manager, and then run
> the following command to see if the PID is listening on the proper port
> netstat -aon
> If it is OK, please try to telnet the port from client:
> telnet <server name> <port number>
> If not, it seems there is firewall blocking the port. Please check
> Windows/third party firewall on the server to test
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
>
|||Hello,
Apparently you have firewall on the server blocks port 1552. Please
temporarily disable firewalls to test the situation. If it works, you could
open port on firwall to solve the problem.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==
>X-WBNR-Posting-Host: 84.147.139.248
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 04:00:29 -0800
>Lines: 87
>Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>From the SQL Server log:
>Server process ID is 1552
>Server is listening on [ 'any' <ipv4> 1743].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\SQLLocal\S5 ].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\MSSQL$S5\sql\query ].
>Server is listening on [ 127.0.0.1 <ipv4> 1744].
>Dedicated admin connection support was established for listening locally
on
>port 1744.
>SQL Server is now ready for client connections. This is an informational
>message; no user action is required.
>From netstat -aon
>TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
>TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
>Connecting with Telnet from the client gives "Connect failed", also when
the[vbcol=seagreen]
>Browser is started.
>
>"Peter Yang [MSFT]" wrote:
run[vbcol=seagreen]
rights.[vbcol=seagreen]
the[vbcol=seagreen]
browser
>
|||1552 is the process id of sql server in the example.
"Peter Yang [MSFT]" wrote:

> Hello,
> Apparently you have firewall on the server blocks port 1552. Please
> temporarily disable firewalls to test the situation. If it works, you could
> open port on firwall to solve the problem.
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> <ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
> on
> the
> run
> rights.
> the
> browser
>
|||Hello Pat,
Sorry. My typo. Server port 1743 shall be opened by firewall. Also, client
network shall be configured to 1743 as well.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZMNgMtU2vKHeRwTEqMU7ZbMxx2xA==
>X-WBNR-Posting-Host: 84.147.154.98
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
<7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
<PBj2TK1QGHA.6216@.TK2MSFTNGXA03.phx.gbl>[vbcol=seagreen]
>Subject: RE: Connecting without SQL Browser
>Date: Mon, 20 Mar 2006 07:50:29 -0800
>Lines: 146
>Message-ID: <B93CC259-A26F-444C-93C7-1155FDC5310C@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:424932
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>1552 is the process id of sql server in the example.
>"Peter Yang [MSFT]" wrote:
could[vbcol=seagreen]
rights.[vbcol=seagreen]
locally[vbcol=seagreen]
informational[vbcol=seagreen]
when[vbcol=seagreen]
then[vbcol=seagreen]
port[vbcol=seagreen]
so[vbcol=seagreen]
the[vbcol=seagreen]
in
>

Connecting VIA IP Address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
Chris
I should have stated this but I am using SQL Server 2000 and the server
is Windows 2003
|||I should have stated this but I am using SQL Server 200 on a Windows
2003 cluster

COnnecting via IP address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
Chris
I should have stated this but I am using SQL Server 200 on a Windows
2003 cluster
|||Your SQL Server instance must be a named instance listening on port 1433. If
it were a default instance, connecting to the IP without specifying a port
would have automatically led to the default port of 1433, and would have
succeeded.
With a named instance, however, you are not directed to 1433 by default.
Either the client has to be told by the server via UDP 1434 as to what port
to use, or it has to identify the port explicitly. And if the client is
using an explicit IP address, you are not using UDP 1434.
Linchi
<cfrank@.investorforce.com> wrote in message
news:1140797262.929065.72080@.i40g2000cwc.googlegro ups.com...
> When I try to connect via IP to a newly created Active Active cluster I
> have to add the port to the IP for it to work. An example is if my IP
> is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
> then it works fine. Am I missing a setting somewhere to make this work
> just by using the IP? Oh... and just to note this work the same accross
> the network or if I am logged on local to the box.
> thanks
> Chris
>

COnnecting via IP address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
ChrisI should have stated this but I am using SQL Server 200 on a Windows
2003 cluster|||Your SQL Server instance must be a named instance listening on port 1433. If
it were a default instance, connecting to the IP without specifying a port
would have automatically led to the default port of 1433, and would have
succeeded.
With a named instance, however, you are not directed to 1433 by default.
Either the client has to be told by the server via UDP 1434 as to what port
to use, or it has to identify the port explicitly. And if the client is
using an explicit IP address, you are not using UDP 1434.
Linchi
<cfrank@.investorforce.com> wrote in message
news:1140797262.929065.72080@.i40g2000cwc.googlegroups.com...
> When I try to connect via IP to a newly created Active Active cluster I
> have to add the port to the IP for it to work. An example is if my IP
> is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
> then it works fine. Am I missing a setting somewhere to make this work
> just by using the IP? Oh... and just to note this work the same accross
> the network or if I am logged on local to the box.
> thanks
> Chris
>

Connecting to SQL Server through firewall

I have a simple asp page that queries a database inside our firewall. It works fine from the inside, and only uses port 1433. But if i put it out on our web server it won't connect and tries to use ports 139 and 445. Has anybody ran across this before?
Thanks,
JohnAre those ports that you see registered with the firewall to allow traffic? You can explicitly specify the port number in your app connection string.|||I have a simple asp page that queries a database inside our firewall. It works fine from the inside, and only uses port 1433. But if i put it out on our web server it won't connect and tries to use ports 139 and 445. Has anybody ran across this before?You are using Named Pipes instead of TCP/IP for the ODBC connection on the ASP server.

-PatP|||is that in the connection string like:

Data Source=172.25.24.30:1433

or is there some other syntax.

Thanks again,

John|||You are using Named Pipes instead of TCP/IP for the ODBC connection on the ASP server.

-PatP

Do you still need to do that for a nonDSN connection?

Thanks Pat,

John|||My first guess would be to go to the ASP server, run the SQL Client Configuration to change the default connection type to TCP/IP. I think that should fix you right up.

-PatP|||Thanks for all your help. It was set to named pipes. Does anyone know if that is the default setting? I always thought the machine came up with TCP/IP as default.

Thanks again.

John|||Different MDAC, SQL Tool, etc combinations have different defaults, and some applications change the default as part of their installation (for which I'd like to fry the developer that came up with that idea!). I don't know of any way to concretely identify just how this came to be, so I just fix it when it bytes me and move on...

-PatP|||I have a similar question. I have installed MSDE 2000 on a Win2k3 Server and everything is working fine with the DB. The MSSQLSERVER servoce has been running for 60 days straight with no issue. MSDE works great. However, I cannot connect to it on port 1433 through the firewall. Using netstat I cannot see that it is not listening on port 1433. I ran the CLICONFG utility and I can see that it has TCP/IP at the top of the list with Named Pipes below it. I have other servers ( Only Win2k servers) with MSDE 200 installed and configured similarily and these servers are listening on port 1433. I looked at the registry settings and they seem OK - nothing out of place.

The DB is now in a production environment and I cannot bounce the MSSQLSERVER service till the weekend during scheduled maintenance.

How can I ensure when I stop/start the MSSQLSERVER service that it is listening on port 1433? Would it be wise using CLICONFG to remove Named Pipes (IIS is the only user of the Database) ? I would prefer not to do that as I believe that NP is faster SQLServer and IIS are on the same box.

Does the version of MDAC have anything to do with this issue?

--Steve|||I can't think of any case where Named Pipes would be faster than TCP/IP that would occur in the real world (yes, I know of a way to construct one, but it would never occur naturally).

You can certainly do as you see fit, but I would recommend using TCP/IP as your default connection type.

If you've recently applied either sp3a to SQL Server, or sp2 to Server 2k3, they will automajikally block port 1433. Read up on the service packs to determine how you want to configure your machine to accomodate the access that you need.

-PatP|||I believe that the problem was that the CLICONFIG was not what I should have been using. There is a SVRNETCN.EXE utility in the C:\Program Files\Microsoft Sql Server\80\Tools\Binn directory that is the program to use. It turns out that the box had no IPC set at all. I added TCP/IP and it won't use the new options till I bounce MSQSQLSERVER service.

--Steve

Connecting to SQL Server on a different port

I have a server running SQL Server 2005 Dev behind a firewall that blocks the default SQL Server port. So, I changed the port that SQL server uses to another port. How do I connect to the database instance with SQL Server Management Studio. I have tried:

xxx.xxx.xxx.xxx\MSSQLSERVER
xxx.xxx.xxx.xxx:port\MSSQLSERVER

name.of.machine\MSSQLSERVER

On all of these, I get an error 25 - Connection string is not valid. I have the surface area configured correctly (i.e. named pipes and TCP/IP are both turned on), and the sql server browser is running. I can ping the server just fine, and when I go to GRC.com and do a shields up report it lists my port of choice as being open.

What am I missing?

I also set the native client configuration's default port to the port I want to connect to, and it appears that that didn't work either.

Ideas? I would like to get this running ASAP.

Thanks in advance!Also, opening up that port on the firewall is not an option. I don't have access to the firewall. I'm doing this for a school project, and I have to work under their restrictions.|||

Use server="servername,port_number" (take note of the comma)

Or,you can create a DNS entry that defines the server name and IP address combination. This is normally done on the DNS server. Just make sure that this entry is allowed in your firewall

http://support.microsoft.com/kb/269882/