![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
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: |
#12
| |||
| |||
|
|
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 |
#13
| |||
| |||
|
#14
| |||
| |||
|
#15
| |||
| |||
|
|
lvac03dmz\sqlexpress does work without the tcp: in front of it. |
#16
| |||
| |||
|
#17
| |||
| |||
|
| 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 |
#18
| |||
| |||
|
#19
| |||
| |||
|
|
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. |
![]() |
| Thread Tools | |
| Display Modes | |
| |