connection issue from our developer

Hi,
SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
From my client machine, my window account and that developer window account
all can login into this server with ODBC, sql client, telent to 1433 or VS
connection. But, this developer can't login to SQL server from him machine
with any appliction. He is in the same domain as server and my machine. I
don't know what's the reason to cause this issue now.
Please advise. Thank you.
Lynn
Best Regards,
Lynn
What is the exact error message and error number he gets
when he tries to log into SQL Server?
-Sue
On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Hi,
>SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
>From my client machine, my window account and that developer window account
>all can login into this server with ODBC, sql client, telent to 1433 or VS
>connection. But, this developer can't login to SQL server from him machine
>with any appliction. He is in the same domain as server and my machine. I
>don't know what's the reason to cause this issue now.
>Please advise. Thank you.
>Lynn
|||We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting.
osql -- SQL server doesn't exist or access denied
Query Analyzer -- General network error. Check your network documentation
VS 2005 -- (without specifing TCP protocal in connection) A connection was
succssfully established with the server, but then an error occured during the
pre-login handshake. When connecting ....(provider: Named Pipes provider,
error: 0 - No process is on the ther end of the pipe)
VS 2005 -- (specify TCP protocal in connection) An error has occurred while
establishing a connection to the server. When connecting to SQL server 2005,
this failure may be caused by the fact that under the default settings ...
(provider: TCP provider: 0 -- A connection attempt failed because the
connected party didn't not properly respond after a period of tiem, or
established connection failed because connected host has failed to respond.)
Again, this developer is able to login by using my machine with his WIN
account.
After I enable Named Pipes in server. This developer is able to connect to
server on his machine by using Named Pipe.
Firewall is off in the server, so I can't think of the issue for TCP
connection on developer's machine.
Please advise. Thank you.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> What is the exact error message and error number he gets
> when he tries to log into SQL Server?
> -Sue
> On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||Check the following article in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
-Sue
On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>We only enable Shared Memory and TCP/IP protocal in server side. And, those
>are the error they are getting.
>osql -- SQL server doesn't exist or access denied
>Query Analyzer -- General network error. Check your network documentation
>VS 2005 -- (without specifing TCP protocal in connection) A connection was
>succssfully established with the server, but then an error occured during the
>pre-login handshake. When connecting ....(provider: Named Pipes provider,
>error: 0 - No process is on the ther end of the pipe)
>VS 2005 -- (specify TCP protocal in connection) An error has occurred while
>establishing a connection to the server. When connecting to SQL server 2005,
>this failure may be caused by the fact that under the default settings ...
>(provider: TCP provider: 0 -- A connection attempt failed because the
>connected party didn't not properly respond after a period of tiem, or
>established connection failed because connected host has failed to respond.)
>Again, this developer is able to login by using my machine with his WIN
>account.
>After I enable Named Pipes in server. This developer is able to connect to
>server on his machine by using Named Pipe.
>Firewall is off in the server, so I can't think of the issue for TCP
>connection on developer's machine.
>Please advise. Thank you.
|||Sue,
The developer's client protocol order is TCP and NP. We didn't enable Named
Pipe in server at the beginning, that's why the first message is NP message
due to client will try to connect in the protocol order in the client. As I
menetioned, after I turn on Named Pipes in server, user's machine is able to
connect to server. But, the issue our developers had is that they couldn't
connect with TCP protocol from their machine. (I can connect by TCP protocol
from my machine. The developer login to my machine and his win account can
connect to the server as well). His machine is able to connect to our SQL
2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
was thinging is firewall in server to caused this issue, but firewall didn't
enable in the server at all. So, I don't know what cause the issue.
Please advise.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> Check the following article in Books Online:
> http://msdn2.microsoft.com/en-us/library/ms175496.aspx
> -Sue
> On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||When you get symptoms like this where it only affects the
user on a particular PC then you need to look at that PC.
You'd probably start by testing basic connectivity to the
server from the PC: Can the user ping the server by name,
can the user ping the server by IP, what network related
issues are found in the Event logs on the PC, can the user
connect to the server using sqlcmd, etc. Also, have you
tried logging in from that users PC?
If you find that the issue is comes up only with Management
Studio, have the user increase the connect timeout in SSMS:
When logging on, click on the options button in the Connect
to Server window and increase the connection timeout to
something greater than the 15 second default.
It would also be worth checking the users MDAC installation
using the component checker. You can download this from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
You may also want to look at applying the latest SQL Server
service pack to the client on that PC having problems.
-Sue
On Thu, 29 Mar 2007 15:38:05 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Sue,
>The developer's client protocol order is TCP and NP. We didn't enable Named
>Pipe in server at the beginning, that's why the first message is NP message
>due to client will try to connect in the protocol order in the client. As I
>menetioned, after I turn on Named Pipes in server, user's machine is able to
>connect to server. But, the issue our developers had is that they couldn't
>connect with TCP protocol from their machine. (I can connect by TCP protocol
>from my machine. The developer login to my machine and his win account can
>connect to the server as well). His machine is able to connect to our SQL
>2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
>was thinging is firewall in server to caused this issue, but firewall didn't
>enable in the server at all. So, I don't know what cause the issue.
>Please advise.
|||Sue,
Thank you again. Definitely, we already checked the network connect from
those developers machine. The connection issue happens to all related
developers. The developers were able to ping the server by name and IP from
their machine. But, the issue only happened on connecting to SQL 2005 with
TCP protocol. We tested through ODBC (with TCP/IP), osql, telnet to 1433
port, VS, but all connection were failed.
One developer already reinstall SQL 2005 client, but the problem is still
resisted. Will ask them to update to sp2 and go from there.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> When you get symptoms like this where it only affects the
> user on a particular PC then you need to look at that PC.
> You'd probably start by testing basic connectivity to the
> server from the PC: Can the user ping the server by name,
> can the user ping the server by IP, what network related
> issues are found in the Event logs on the PC, can the user
> connect to the server using sqlcmd, etc. Also, have you
> tried logging in from that users PC?
> If you find that the issue is comes up only with Management
> Studio, have the user increase the connect timeout in SSMS:
> When logging on, click on the options button in the Connect
> to Server window and increase the connection timeout to
> something greater than the 15 second default.
> It would also be worth checking the users MDAC installation
> using the component checker. You can download this from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> You may also want to look at applying the latest SQL Server
> service pack to the client on that PC having problems.
> -Sue

connection from virtual ip address to firewall?

Hi,
We try to connect from a same named instance to a linked sql server in the
DMZ. The firewall has been set up to allow connections from the virtual ip
address of the instance to pass through and the linked server has been set
up correctly to connect through TCP/IP and the correct port. However, we
cannot connect and we see on the firewall that the requests are coming from
the active cluster node, not from the virtual ip address (even if we open a
Remote Desktop connection to the virtual server name). How can we solve
this?
Hans
This is how clustering works. Make sure you have the Node's IP defined for
access through the firewall.
Cheers,
Rod
"HVE" <eylenh@.hotmail.com> wrote in message
news:1e3yhnhwapvac.q9iklq79zipt$.dlg@.40tude.net...
> Hi,
> We try to connect from a same named instance to a linked sql server in the
> DMZ. The firewall has been set up to allow connections from the virtual ip
> address of the instance to pass through and the linked server has been set
> up correctly to connect through TCP/IP and the correct port. However, we
> cannot connect and we see on the firewall that the requests are coming
from
> the active cluster node, not from the virtual ip address (even if we open
a
> Remote Desktop connection to the virtual server name). How can we solve
> this?
> Hans

connection failed

Hello,
I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
But I cannot connect to sql server. I receive this message "Unable to
connect to server xxxxxx: SQL Server does not exist or access denied"; or
Login failed for user xxxxx. With QA same problem... I created the alias
with client network utility... but no way... i cannot access sql server.
anyone have an idea?
Thanks in advance
Alex
You would want to start with this article and the links it
references - the problems depend on protocols, what the
exact full error message is, what ports you have opened (if
any), etc:
How to configure Windows XP Service Pack 2 (SP2) for use
with SQL Server
http://support.microsoft.com/?id=841249
-Sue
On Fri, 11 Mar 2005 09:15:54 +0200, ".:alex:."
<alex_77ro@.yahoo.com> wrote:

>Hello,
> I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
>But I cannot connect to sql server. I receive this message "Unable to
>connect to server xxxxxx: SQL Server does not exist or access denied"; or
>Login failed for user xxxxx. With QA same problem... I created the alias
>with client network utility... but no way... i cannot access sql server.
>anyone have an idea?
>Thanks in advance
>Alex
>

connection failed

Hello,
I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
But I cannot connect to sql server. I receive this message "Unable to
connect to server xxxxxx: SQL Server does not exist or access denied"; or
Login failed for user xxxxx. With QA same problem... I created the alias
with client network utility... but no way... i cannot access sql server.
anyone have an idea?
Thanks in advance
AlexYou would want to start with this article and the links it
references - the problems depend on protocols, what the
exact full error message is, what ports you have opened (if
any), etc:
How to configure Windows XP Service Pack 2 (SP2) for use
with SQL Server
http://support.microsoft.com/?id=841249
-Sue
On Fri, 11 Mar 2005 09:15:54 +0200, ".:alex:."
<alex_77ro@.yahoo.com> wrote:

>Hello,
> I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
>But I cannot connect to sql server. I receive this message "Unable to
>connect to server xxxxxx: SQL Server does not exist or access denied"; or
>Login failed for user xxxxx. With QA same problem... I created the alias
>with client network utility... but no way... i cannot access sql server.
>anyone have an idea?
>Thanks in advance
>Alex
>

connection error

Hi

I am getting following error while connecting in sql server. i have already disabled firewall, enabled remote connections using pipe and tcp and made sure the sql server and sql browser services are running.

but still the problem persists...can any help me ?

Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

thanks in advance

Do you have a named instacne or a default one ? how are you connecting, you will have to provide some more information on your situation to make it easier forus to give you the right suggestions.

Jens K. Suessmeyer

http://www.sqlserver2005.de

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...
>

Connection and /share file and printer/ option in Windows firewall

Hello
Is there any relation between SQL2005 connection and /share file and
printer/ option in Windows firewall?
When I check the option I can connect from remote client via script, while
not that when I unchecked the option.
I can't easily believe the two entities are related. I checked over and over
again...
If my script matters,
set con=createobject("adodb.connection")
login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
Trusted_connection=yes; "
con.open login3
msgbox con.stateOn Dec 26 2006, 2:18 pm, "Han" <hp4...@.kornet.net.korea> wrote:
> Hello
> Is there any relation between SQL2005 connection and /share file andprinte
r/ option in Windows firewall?
> When I check the option I can connect from remote client via script, while
> not that when I unchecked the option.
> I can't easily believe the two entities are related. I checked over and ov
er
> again...
> If my script matters,
> set con=createobject("adodb.connection")
> login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
> Trusted_connection=yes; "
> con.open login3
> msgbox con.state
I again experiencde same phenomena? Do anyone know about that?

Connection and /share file and printer/ option in Windows firewall

Hello
Is there any relation between SQL2005 connection and /share file and
printer/ option in Windows firewall?
When I check the option I can connect from remote client via script, while
not that when I unchecked the option.
I can't easily believe the two entities are related. I checked over and over
again...
If my script matters,
set con=createobject("adodb.connection")
login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
Trusted_connection=yes; "
con.open login3
msgbox con.state
On Dec 26 2006, 2:18 pm, "Han" <hp4...@.kornet.net.korea> wrote:
> Hello
> Is there any relation between SQL2005 connection and /share file andprinter/ option in Windows firewall?
> When I check the option I can connect from remote client via script, while
> not that when I unchecked the option.
> I can't easily believe the two entities are related. I checked over and over
> again...
> If my script matters,
> set con=createobject("adodb.connection")
> login3="provider=SQLOLEDB; server=w3a; Initial Catalog=air;
> Trusted_connection=yes; "
> con.open login3
> msgbox con.state
I again experiencde same phenomena? Do anyone know about that?

Connecting web pages to SQL Server

Can anyone advise me how connect web pages hosted by our ISP to an SQL
Server that is hidden behind our Company Firewall.
We are able to connect to the SQL Server using a VPN, but we are unable
to connect or using web pages that are hosted by our ISP.
Thanks
LC
Hi
Check out
http://support.microsoft.com/default...b;en-us;287932
John
"Lyndon Cushing" wrote:

> Can anyone advise me how connect web pages hosted by our ISP to an SQL
> Server that is hidden behind our Company Firewall.
> We are able to connect to the SQL Server using a VPN, but we are unable
> to connect or using web pages that are hosted by our ISP.
> Thanks
> LC
>

Connecting web pages to SQL Server

Can anyone advise me how connect web pages hosted by our ISP to an SQL
Server that is hidden behind our Company Firewall.
We are able to connect to the SQL Server using a VPN, but we are unable
to connect or using web pages that are hosted by our ISP.
Thanks
LCHi
Check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
John
"Lyndon Cushing" wrote:
> Can anyone advise me how connect web pages hosted by our ISP to an SQL
> Server that is hidden behind our Company Firewall.
> We are able to connect to the SQL Server using a VPN, but we are unable
> to connect or using web pages that are hosted by our ISP.
> Thanks
> LC
>

Connecting web pages to SQL Server

Can anyone advise me how connect web pages hosted by our ISP to an SQL
Server that is hidden behind our Company Firewall.
We are able to connect to the SQL Server using a VPN, but we are unable
to connect or using web pages that are hosted by our ISP.
Thanks
LCHi
Check out
http://support.microsoft.com/defaul...kb;en-us;287932
John
"Lyndon Cushing" wrote:

> Can anyone advise me how connect web pages hosted by our ISP to an SQL
> Server that is hidden behind our Company Firewall.
> We are able to connect to the SQL Server using a VPN, but we are unable
> to connect or using web pages that are hosted by our ISP.
> Thanks
> LC
>

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 through firewall

SQL server seems to be having problems writing to another
sql server database server behind a firewall. The ip
address is able to be pinged through the firewall but
trying to access sql server gives "server does not exist
or access is denied" message. The firewall has been
setup to allow for this particular ip address. Port 1433
is selected and TCP/IP is selected from Client Network
Utility and Server Network Utility.
Any ideas anyone? TIA!Hi Steve:
Suggest you try these steps:
1.Try to close firewell a moment, at that moment, test if the remote
connect work well.
2. If it does not work well, not the problem of firewall, but the
problem of network
If it work well, enable the firewall can try to ping 1433 port on the
remote machine
After these two steps, we can see what problem it is then we can do
more
Best Wishes
Wei Ci Zhou|||Dear Wei,
I did as you suggested and it was indeed the firewall. There was a rule
allowing port 1433 but another rule above that that barred all ports.
Thank you again for your response and your assistance!
Steve
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

Connecting to SQL server through a firewall

Hi,
Could someone please tell me what ports I need to open to pass SQL
connection requests through a firewall?
Thanks,
Steve287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
If you're using ISA Server, you can just run the Server Publishing Wizard
and Publish SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

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/

Connecting to SQL Server from IIS in DMZ

My Web Server is standalone, in a DMZ and not a member of the domain the SQL server belongs to. The SQL server is internal and behind a firewall.

I followed the recommendations on Microsoft's website Using the ASP.NET process identity
and local mirrored ASPNET accounts:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch12.asp

But get the error: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

From what I read in the document it should try and connect with the ASPNET Process identity.

I have tested with Impersonation using a local windows account and UserID and Password in the connection string and can connect to the SQL server through the firewall so the relevant ports etc are open.

However I don't want to have user Id's and passwords in the connection string and would like to use integrated security.

Pls help as I am tearing all my hair out!!!!!This must be frustrating for you.

Could you post the connection string that is failing and maybe that will spark the answer?

Terri|||Thanks for your reply, however I organised a contractor to come in and check it out and when I showed him what the problem was it didn't happen and everything worked ok!!

Arrrggghhh!!! And nothing at all has/was changed.

Typical...

Cheers|||I have the EXACT same problem, only mine isn't fixing itself! I used the mirrored local ASPNET account and I am getting the login failed for user '(null)' message.

Connection string is: Data Source=<server name>;Initial Catalog=<database name>;Integrated Security=SSPI;

Any ideas?|||I spent hours upon hours trying to fix it.
Have you changed the 'machine' password in machine.config to match your local ASPNET Account?

Basically I changed that and set up the accounts and I got the error you are talking about, it came right by itself, when I think back it is possible I did a reboot of the webserver.|||You were right, I just needed to reboot the webserver. I guess the thing to remember is always reboot when you change machine.cofig.

Thanks, Cove!|||No problem. Probably stopping and starting the relevant services would have done the trick too??