2008R2 lauscht nicht auf 1433

[tobee 10]

Hallo

Sowohl in meiner Mini-Testumgebung (win7 ohne Domäne), als auch produktiv (Server 2008 R2 in einer Domäne) habe ich das Problem, dass der SQL Server 2008 R2 (Standard-Edition mit SP1) nicht auf 1433 lauscht, wie in TCP/IP port numbers required to communicate to SQL over a firewall beschrieben

 

Z.B.

C:\Windows\system32>netstat -abn | findstr 143
UDP    0.0.0.0:1434           *:*
UDP    [::]:1434              *:*

oder (xp_errorlog):

2012-03-07 13:56:21.770	Server	Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)    Jun 17 2011 00:54:03    Copyright (c) Microsoft Corporation    (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)  
2012-03-07 13:56:21.780	Server	Authentication mode is WINDOWS-ONLY.
2012-03-07 13:56:21.780	Server	Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2INSTANZ\MSSQL\Log\ERRORLOG'.
2012-03-07 13:56:21.790	Server	Registry startup parameters:     -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2INSTANZ\MSSQL\DATA\master.mdf    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2INSTANZ\MSSQL\Log\ERRORLOG    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2INSTANZ\MSSQL\DATA\mastlog.ldf
2012-03-07 13:56:22.110	spid7s	FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008R2INSTANZ'.
2012-03-07 13:56:22.130	spid7s	SQL Trace ID 1 was started by login "sa".
2012-03-07 13:56:22.140	spid7s	Starting up database 'mssqlsystemresource'.
2012-03-07 13:56:22.300	spid10s	Starting up database 'model'.
2012-03-07 13:56:22.330	spid10s	The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes.  3584 bytes at offset 16896 in file C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2INSTANZ\MSSQL\DATA\modellog.ldf will be written.
2012-03-07 13:56:22.350	spid10s	Clearing tempdb database.
2012-03-07 13:56:22.620	spid10s	Starting up database 'tempdb'.
2012-03-07 13:56:22.650	spid14s	The Service Broker protocol transport is disabled or not configured.
2012-03-07 13:56:22.660	Server	A self-generated certificate was successfully loaded for encryption.
2012-03-07 13:56:22.670	Server	Server is listening on [ 'any' <ipv6> 49344].
2012-03-07 13:56:22.670	Server	Server is listening on [ 'any' <ipv4> 49344].
2012-03-07 13:56:22.670	Server	Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2008R2INSTANZ ].
2012-03-07 13:56:22.670	Server	Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2008R2INSTANZ\sql\query ].
2012-03-07 13:56:22.670	Server	Server is listening on [ ::1 <ipv6> 49345].
2012-03-07 13:56:22.680	Server	Server is listening on [ 127.0.0.1 <ipv4> 49345].
2012-03-07 13:56:22.680	spid14s	Service Broker manager has started.
2012-03-07 13:56:22.680	Server	Dedicated admin connection support was established for listening locally on port 49345.
2012-03-07 13:56:22.680	Server	SQL Server is now ready for client connections. This is an informational message; no user action is required.
2012-03-07 13:56:52.570	spid17s	Starting up database 'msdb'.
2012-03-07 13:56:52.570	spid18s	Starting up database 'ReportServer$SQL2008R2INSTANZ'.
2012-03-07 13:56:52.590	spid20s	Starting up database 'ReportServer$SQL2008R2INSTANZTempDB'.
2012-03-07 13:56:53.300	spid7s	Recovery is complete. This is an informational message only. No user action is required.
2012-03-07 13:57:00.030	spid13s	A new instance of the full-text filter daemon host process has been successfully started.  

Wie behebt man das? Auf dem Produktiven Server läuft sonst nix, nur Domain Member, kein DC, DNS, DHCP, Mail oder sonstiges.

Auf meinem Testrechner (Win7ulti, 64bit) auch nur diese Serversoftware, ansonsten nur Browser und Textverarbeitung.

Asncheinend sind die Ports bei Win7 und Server 2008R2 unterschiedlich?

 

Ciao

[wilgin 11]

Hallo,

 

ich bin mal vor einiger Zeit über so etwas "gefallen".

Bei mir war der Port nicht auf den Schnittstellen aktiviert.

 

Navigiere zu SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for MSSQLSERVER > TCP/IP > Registerkarte: IP Addresses

 

Hier muss bei der betroffenen Schnittstelle (falls mehrere) UND (!!!) im Bereich IPAll (ganz unten) unter TCP Port 1433 eingetragen sein.

 

Erst nachdem ich unter IPALL den Port eingetragen hab, funktionierte es.

[Sunny61 806]

Evtl. hilft dieser Lösungsvorschlag: http://blog.alexonasp.net/post/2011/03/06/Auf-welchem-Port-lauft-mein-SQL-Server-%28Express%29-2008-R2-Oder-warum-bekomme-ich-keine-Verbindung.aspx