Guten Tag,
wir möchten die JTL WaWi auf einem Rootserver betreiben, auf welchen wir per Remote zugreifen, der Server steht in einem Rechenzentrum. Auf dem Server ist Linux installiert und darauf Parallales Desktop VM mit WinXP Pro (dies tut aber eig. nichts zur Sache denke ich)
So, ich habe den Port auf 1433 fest eingestellt, und diesen freigegeben mittels Port Forwarding. Auch habe ich den Port 1434 in den Forwarding Einstellungen drin, für den SQL Brower.
Bis dato ist noch keine Firewall installiert, die von XP ist auch deaktiviert.
Lokal in der VM funktioniert die JTL WaWi einwandfrei. Wir benutzen die Beta Version von JTL, auf dem Client-Rechner ist nur der Beta Client installiert, und keine MSSQL Datenbank.
Ich kann auch von aussen zur VM verbinden, mittels Telnet habe ich die Verbindung getestet. (Per Telnet an Server mit Angabe des Ports 1433, Verbindung funktioniert)
Wenn ich nun von aussen versuche auf den MSSQL Server zuzugreifen, dann kommt die Verbinung auch bis zu diesem durch, was man daran merkt (neben dem Telnet Test), dass Fehler in die MSSQL Log Files geschrieben werden, bzw handelt es sich um genau einen Fehler der immer wiederkehrt, dieser sieht so aus: (kompletter Log File auszug, hier kann man auch sehen an welchem Port der Server hängt usw.)
2010-01-14 11:32:29.07 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2010-01-14 11:32:29.07 Server (c) 2005 Microsoft Corporation.
2010-01-14 11:32:29.07 Server All rights reserved.
2010-01-14 11:32:29.09 Server Server process ID is 2300.
2010-01-14 11:32:29.09 Server Authentication mode is MIXED.
2010-01-14 11:32:29.09 Server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2010-01-14 11:32:29.09 Server This instance of SQL Server last reported using a process ID of 2672 at 14.1.2010 11:32:18 (local) 14.1.2010 16:32:18 (UTC). This is an informational message only; no user action is required.
2010-01-14 11:32:29.09 Server Registry startup parameters:
2010-01-14 11:32:29.09 Server -d C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2010-01-14 11:32:29.09 Server -e C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2010-01-14 11:32:29.09 Server -l C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2010-01-14 11:32:29.09 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-01-14 11:32:29.09 Server Detected 1 CPUs. This is an informational message; no user action is required.
2010-01-14 11:32:29.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2010-01-14 11:32:29.37 Server Database mirroring has been enabled on this instance of SQL Server.
2010-01-14 11:32:29.40 spid5s Starting up database 'master'.
2010-01-14 11:32:29.45 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2010-01-14 11:32:29.48 spid5s SQL Trace ID 1 was started by login "sa".
2010-01-14 11:32:29.49 spid5s Starting up database 'mssqlsystemresource'.
2010-01-14 11:32:29.49 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2010-01-14 11:32:29.95 Server A self-generated certificate was successfully loaded for encryption.
2010-01-14 11:32:29.96 Server Server is listening on [ 'any' <ipv4> 1433].
2010-01-14 11:32:29.96 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2010-01-14 11:32:29.96 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2010-01-14 11:32:29.96 spid5s Server name is 'MEISTER\JTLWAWI'. This is an informational message only. No user action is required.
2010-01-14 11:32:29.96 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2010-01-14 11:32:29.98 spid8s Starting up database 'model'.
2010-01-14 11:32:29.98 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2010-01-14 11:32:29.98 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-01-14 11:32:29.98 spid5s Starting up database 'msdb'.
2010-01-14 11:32:30.03 spid8s Clearing tempdb database.
2010-01-14 11:32:31.23 spid8s Starting up database 'tempdb'.
2010-01-14 11:32:31.34 spid5s Recovery is complete. This is an informational message only. No user action is required.
2010-01-14 11:32:31.34 spid11s The Service Broker protocol transport is disabled or not configured.
2010-01-14 11:32:31.34 spid11s The Database Mirroring protocol transport is disabled or not configured.
2010-01-14 11:32:31.37 spid11s Service Broker manager has started.
2010-01-14 11:33:04.18 spid51 Starting up database 'eazybusiness'.
2010-01-14 11:33:26.62 Fehler: 17836, Schweregrad: 20, Status: 1.
2010-01-14 11:33:26.62 Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 92.74.125.59]
2010-01-14 11:33:26.79 Fehler: 17836, Schweregrad: 20, Status: 1.
2010-01-14 11:33:26.79 Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 92.74.125.59]
2010-01-14 11:33:27.04 Fehler: 17836, Schweregrad: 20, Status: 1.
Nun die Fehlermeldung welche der Client ausspuckt, wenn ich versuche die Verbindung unter "Systemsteuerung->Verwaltung->Datenquellen(ODBC)" einzurichten/testen.
Connection failed:
SQLState: '01000'
SQL Server Error: 14
{Microsoft}{ODBC SQL Server Driver}{TCP/IP Sockets}ConnectionOpen (Invalid Connection{}}
Connection failed:
SQLState: '08001'
SQL Server Error: 14
{Microsoft}{ODBC SQL Server Driver}{TCP/IP Sockets}Invalid Connection
Ich bin nun langsam am verzweifeln und weiss nicht was ich noch alles ausprobieren soll. Ich hoffe es gibt eine Lösung hierfür.
wir möchten die JTL WaWi auf einem Rootserver betreiben, auf welchen wir per Remote zugreifen, der Server steht in einem Rechenzentrum. Auf dem Server ist Linux installiert und darauf Parallales Desktop VM mit WinXP Pro (dies tut aber eig. nichts zur Sache denke ich)
So, ich habe den Port auf 1433 fest eingestellt, und diesen freigegeben mittels Port Forwarding. Auch habe ich den Port 1434 in den Forwarding Einstellungen drin, für den SQL Brower.
Bis dato ist noch keine Firewall installiert, die von XP ist auch deaktiviert.
Lokal in der VM funktioniert die JTL WaWi einwandfrei. Wir benutzen die Beta Version von JTL, auf dem Client-Rechner ist nur der Beta Client installiert, und keine MSSQL Datenbank.
Ich kann auch von aussen zur VM verbinden, mittels Telnet habe ich die Verbindung getestet. (Per Telnet an Server mit Angabe des Ports 1433, Verbindung funktioniert)
Wenn ich nun von aussen versuche auf den MSSQL Server zuzugreifen, dann kommt die Verbinung auch bis zu diesem durch, was man daran merkt (neben dem Telnet Test), dass Fehler in die MSSQL Log Files geschrieben werden, bzw handelt es sich um genau einen Fehler der immer wiederkehrt, dieser sieht so aus: (kompletter Log File auszug, hier kann man auch sehen an welchem Port der Server hängt usw.)
2010-01-14 11:32:29.07 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2010-01-14 11:32:29.07 Server (c) 2005 Microsoft Corporation.
2010-01-14 11:32:29.07 Server All rights reserved.
2010-01-14 11:32:29.09 Server Server process ID is 2300.
2010-01-14 11:32:29.09 Server Authentication mode is MIXED.
2010-01-14 11:32:29.09 Server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2010-01-14 11:32:29.09 Server This instance of SQL Server last reported using a process ID of 2672 at 14.1.2010 11:32:18 (local) 14.1.2010 16:32:18 (UTC). This is an informational message only; no user action is required.
2010-01-14 11:32:29.09 Server Registry startup parameters:
2010-01-14 11:32:29.09 Server -d C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2010-01-14 11:32:29.09 Server -e C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2010-01-14 11:32:29.09 Server -l C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2010-01-14 11:32:29.09 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-01-14 11:32:29.09 Server Detected 1 CPUs. This is an informational message; no user action is required.
2010-01-14 11:32:29.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2010-01-14 11:32:29.37 Server Database mirroring has been enabled on this instance of SQL Server.
2010-01-14 11:32:29.40 spid5s Starting up database 'master'.
2010-01-14 11:32:29.45 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2010-01-14 11:32:29.48 spid5s SQL Trace ID 1 was started by login "sa".
2010-01-14 11:32:29.49 spid5s Starting up database 'mssqlsystemresource'.
2010-01-14 11:32:29.49 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2010-01-14 11:32:29.95 Server A self-generated certificate was successfully loaded for encryption.
2010-01-14 11:32:29.96 Server Server is listening on [ 'any' <ipv4> 1433].
2010-01-14 11:32:29.96 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2010-01-14 11:32:29.96 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2010-01-14 11:32:29.96 spid5s Server name is 'MEISTER\JTLWAWI'. This is an informational message only. No user action is required.
2010-01-14 11:32:29.96 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2010-01-14 11:32:29.98 spid8s Starting up database 'model'.
2010-01-14 11:32:29.98 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2010-01-14 11:32:29.98 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-01-14 11:32:29.98 spid5s Starting up database 'msdb'.
2010-01-14 11:32:30.03 spid8s Clearing tempdb database.
2010-01-14 11:32:31.23 spid8s Starting up database 'tempdb'.
2010-01-14 11:32:31.34 spid5s Recovery is complete. This is an informational message only. No user action is required.
2010-01-14 11:32:31.34 spid11s The Service Broker protocol transport is disabled or not configured.
2010-01-14 11:32:31.34 spid11s The Database Mirroring protocol transport is disabled or not configured.
2010-01-14 11:32:31.37 spid11s Service Broker manager has started.
2010-01-14 11:33:04.18 spid51 Starting up database 'eazybusiness'.
2010-01-14 11:33:26.62 Fehler: 17836, Schweregrad: 20, Status: 1.
2010-01-14 11:33:26.62 Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 92.74.125.59]
2010-01-14 11:33:26.79 Fehler: 17836, Schweregrad: 20, Status: 1.
2010-01-14 11:33:26.79 Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 92.74.125.59]
2010-01-14 11:33:27.04 Fehler: 17836, Schweregrad: 20, Status: 1.
Nun die Fehlermeldung welche der Client ausspuckt, wenn ich versuche die Verbindung unter "Systemsteuerung->Verwaltung->Datenquellen(ODBC)" einzurichten/testen.
Connection failed:
SQLState: '01000'
SQL Server Error: 14
{Microsoft}{ODBC SQL Server Driver}{TCP/IP Sockets}ConnectionOpen (Invalid Connection{}}
Connection failed:
SQLState: '08001'
SQL Server Error: 14
{Microsoft}{ODBC SQL Server Driver}{TCP/IP Sockets}Invalid Connection
Ich bin nun langsam am verzweifeln und weiss nicht was ich noch alles ausprobieren soll. Ich hoffe es gibt eine Lösung hierfür.