dbTalk Databases Forums  

Connection Strangeness

microsoft.public.sqlserver.connect microsoft.public.sqlserver.connect


Discuss Connection Strangeness in the microsoft.public.sqlserver.connect forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
firebalrog
 
Posts: n/a

Default Re: Connection Strangeness - 05-06-2010 , 09:46 AM






On May 5, 9:47*am, firebalrog <barrettpa... (AT) gmail (DOT) com> wrote:
Quote:
Yes Pinging it works with anything, 10.10.9.x, or lvac03dmz,lvac09dmz,
dmzserver all pinging works. All pings regardless of address or
address methodology *resolve in 126ms or less on the *t1 point to
point.

We will try forcing tcp:x\sqlexpress next I have also directed one of
the programmers to capture the execption information and post it here
once we have it caught. That might also help for diagnosis.
exact exception follows:

System.Data.SqlClient.SqlException: A network-related or instance-
specific error occurred while establishing a connection to SQL Server.
The server was not found or was not accessible. Verify that the
instance name is correct and that SQL Server is configured to allow
remote connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server)
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout,
Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject)
at
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject)
at
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance,
SqlConnection owningObject, SqlConnectionString connectionOptions,
Int64 timerStart)
at
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String
newPassword, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String newPassword, SqlConnection owningObject, Boolean
redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.QuietOpen(IDbConn ection
connection, ConnectionState& originalState)
at System.Data.Common.DbDataAdapter.FillInternal(Data Set dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables,
Int32 startRecord, Int32 maxRecords, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at
LVACID.dsCardsTypeTableAdapters.GetCardsTypeTableA dapter.Fill(GetCardsTypeDataTable
dataTable) in C:\CurrentLVAC\MembershipNet\trunk\LVACPhoto\LVACI D
\dsCardsType.Designer.cs:line 778
at LVACID.frmID.frmID_Load(Object sender, EventArgs e) in C:
\CurrentLVAC\MembershipNet\trunk\LVACPhoto\LVACID\ frmID.cs:line 777

Reply With Quote
  #12  
Old   
firebalrog
 
Posts: n/a

Default Re: Connection Strangeness - 05-06-2010 , 10:35 AM






On May 6, 7:46*am, firebalrog <barrettpa... (AT) gmail (DOT) com> wrote:
Quote:
On May 5, 9:47*am, firebalrog <barrettpa... (AT) gmail (DOT) com> wrote:> Yes Pinging it works with anything, 10.10.9.x, or lvac03dmz,lvac09dmz,
dmzserver all pinging works. All pings regardless of address or
address methodology *resolve in 126ms or less on the *t1 point to
point.

We will try forcing tcp:x\sqlexpress next I have also directed one of
the programmers to capture the execption information and post it here
once we have it caught. That might also help for diagnosis.

exact exception follows:

System.Data.SqlClient.SqlException: A network-related or instance-
specific error occurred while establishing a connection to SQL Server.
The server was not found or was not accessible. Verify that the
instance name is correct and that SQL Server is configured to allow
remote connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server)
* *at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection)
* *at
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj)
* *at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout,
Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject)
* *at
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject)
* *at
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance,
SqlConnection owningObject, SqlConnectionString connectionOptions,
Int64 timerStart)
* *at
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String
newPassword, Boolean redirectedUserInstance)
* *at
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String newPassword, SqlConnection owningObject, Boolean
redirectedUserInstance)
* *at
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection owningConnection)
* *at
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
* *at
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject)
* *at
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject)
* *at
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject)
* *at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
* *at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
* *at System.Data.SqlClient.SqlConnection.Open()
* *at System.Data.Common.DbDataAdapter.QuietOpen(IDbConn ection
connection, ConnectionState& originalState)
* *at System.Data.Common.DbDataAdapter.FillInternal(Data Set dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
* *at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables,
Int32 startRecord, Int32 maxRecords, IDbCommand command,
CommandBehavior behavior)
* *at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
* *at
LVACID.dsCardsTypeTableAdapters.GetCardsTypeTableA dapter.Fill(GetCardsTypeDataTable
dataTable) in C:\CurrentLVAC\MembershipNet\trunk\LVACPhoto\LVACI D
\dsCardsType.Designer.cs:line 778
* *at LVACID.frmID.frmID_Load(Object sender, EventArgs e) in C:
\CurrentLVAC\MembershipNet\trunk\LVACPhoto\LVACID\ frmID.cs:line 777
tcp:dmzserver\sqlexpress still didn't work.

Reply With Quote
  #13  
Old   
firebalrog
 
Posts: n/a

Default Re: Connection Strangeness - 05-06-2010 , 10:47 AM



hint maybe?
tcp:lvac03dmz/sqlexpress didn't work also so it looks like it may be
using named pipes.
I will look at the router config but I believe that it is already
allowing 1434 through.

Reply With Quote
  #14  
Old   
firebalrog
 
Posts: n/a

Default Re: Connection Strangeness - 05-06-2010 , 10:48 AM



lvac03dmz\sqlexpress does work without the tcp: in front of it.

Reply With Quote
  #15  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: Connection Strangeness - 05-06-2010 , 04:43 PM



firebalrog (barrettpaulj (AT) gmail (DOT) com) writes:
Quote:
lvac03dmz\sqlexpress does work without the tcp: in front of it.
Interesting. Now force TCP from one of the machines that can use
the DMZSERVER name. If they also fail on TCP, there is probably some
permissions issue with regards to the path for the named pipe. (I know
nothing about that. :-(

Did you check the network configuration for SQL Server? You can review
this in SQL Configuration Manager under Server Protocols. But a caveat:
if TCP is enabled, but it was enabled after SQL Server last was started,
it has not taken effect yet.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Reply With Quote
  #16  
Old   
firebalrog
 
Posts: n/a

Default Re: Connection Strangeness - 05-06-2010 , 05:05 PM



All protocols are enabled on the sqlserver and the firewall is off.

I will crack open the cisco routers and see what their settings are.
The working computers do not route through the same cisco routers,
they connect via vpn which I should have thought of before. Problem
probably is that something for tcp is blocked so it is using named
pipes but dmzserver doesn't work because it is not in wins.

Thank you for your help in diagnosing the problem you put a lot of
effort in helping. Once I fix the routers we will be able to move the
sql server database to the new server.

Paul

Reply With Quote
  #17  
Old   
Rick Byham, MSFT
 
Posts: n/a

Default Re: Connection Strangeness - 05-06-2010 , 05:46 PM



Another vague idea. I had trouble once before with TCP v4 and TCP v6 getting
confused. Consider disabling the one you aren't using. That is, you might be
able to ping with v4, but then fail to connect with v6.
--
Rick Byham, MSFT
(Implies no warranty or rights)


"firebalrog" <barrettpaulj (AT) gmail (DOT) com> wrote

Quote:

All protocols are enabled on the sqlserver and the firewall is off.

I will crack open the cisco routers and see what their settings are.
The working computers do not route through the same cisco routers,
they connect via vpn which I should have thought of before. Problem
probably is that something for tcp is blocked so it is using named
pipes but dmzserver doesn't work because it is not in wins.

Thank you for your help in diagnosing the problem you put a lot of
effort in helping. Once I fix the routers we will be able to move the
sql server database to the new server.

Paul

Reply With Quote
  #18  
Old   
firebalrog
 
Posts: n/a

Default Re: Connection Strangeness - 05-07-2010 , 11:33 AM



Well it appears that tcp is not going through the cisco routers for
some reason and if we put np: in front of the hostname things connect
instantly but if we use tcp: it doesn't work at all.

I am not exactly sure what is wrong with the ciscos because they do
show 1434 udp permit and 1433 tcp permit to the subnet where the
server is. Also sqlcmd tcp:servername\sqlexpress works from another
computer in the dmz. so it appears that tcp is ok on the sqlserver and
just not getting through the routers.

Reply With Quote
  #19  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: Connection Strangeness - 05-07-2010 , 04:42 PM



firebalrog (barrettpaulj (AT) gmail (DOT) com) writes:
Quote:
Well it appears that tcp is not going through the cisco routers for
some reason and if we put np: in front of the hostname things connect
instantly but if we use tcp: it doesn't work at all.

I am not exactly sure what is wrong with the ciscos because they do
show 1434 udp permit and 1433 tcp permit to the subnet where the
server is. Also sqlcmd tcp:servername\sqlexpress works from another
computer in the dmz. so it appears that tcp is ok on the sqlserver and
just not getting through the routers.
Network configuration is fun, isn't it? :-)

I don't envy you.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.