I have purchased 4 new boxes for SQL2005 and my var database product all running on the new Windows 2008 server. A lot of silly mind bender issues but I am up and live now. However, what should the firewall settings be on my SQL database box? I have ultimately turned off Windows Firewall so that I could connect and continue forward.
I am using SQL Server 2005 Express + SP1 on a Windows Small Business Server(SBS) box. The SBS is connected to a client thru LAN.
Following are what I gave as IP address and DNS on the server:
IP: 192.168.16.2, subnet mask : 255.255.255.0, Preferred DNS server: 192.168.16.2, Default gateway and Alternate DNS Server blank
On the client, I have,
IP: 192.168.16.4, subnet mask : 255.255.255.0, Preferred DNS server, Default gateway and Alternate DNS Server blank
I can ping and connect to either of the machines.
If I do a sqlcmd -S "tcp:servernameINSTANCE,port", I get the following error message: HResult 0x80090304, Level 16, State 1 SQL Network Interfaces: The Local Security Authority cannot be contacted
I have changed SQL Server port to 2433, and add it to exception in Windows Firewall, add executive files as in this KB http://msdn2.microsoft.com/en-us/library/ms175043.aspx
Want to change port of SQL Server Browser as well, but dont know how to :(
anyway, after enable Firewall, SQL server is stop working. How to get it working with Firewall? Also, if some one lets me know how to change port of SQL Server Browser too, it would be great
I am trying to install SQl express as part of a custom app.I have been able to use the template.ini to pass in all the parameters and install. installs fine,however the installation isnt browseable by remote machines due to the sqlserver.exe and sqlbrowser.exe not being in the windows firewall list. How can i add then to this list automatically at install time? or is there another way around this?
I have a Windows Server 2003 with SQL Server 2005. I´ve configured the following itens to allow remote connecitions:
[code] WORKAROUND Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To work around this problem, follow these steps on the computer that Windows XP SP2 is installed on:
1. Make sure that the Log On As account for the MSDTC service is the Network Service account. To do this, follow these steps: a. Click Start, and then click Run. b. In the Run dialog box, type Services.msc, and then click OK. c. In the Services window, locate the Distributed Transaction Coordinator service under Name in the right pane. d. Under the Log On As column, see whether the Log On As account is Network Service or Local System.
If the Log On As account is Network Service, go to step 2. If the Log On As account is Local System, continue with these steps. e. Click Start, and then click Run. f. In the Run dialog box, type cmd, and then click OK. g. At the command prompt, type Net stop msdtc to stop the MSDTC service. h. At the command prompt, type Msdtc €“uninstall to remove MSDTC. i. At the command prompt, type regedit to open Registry Editor. j. In Registry Editor, locate, and then delete the following subkey: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDTC k. Close Registry Editor. l. At the command prompt, type Msdtc €“install to install MSDTC. m. At the command prompt, type Net start msdtc to start the MSDTC service.
Note The Log On As account for the MSDTC service is set to the Network Service account.
2. To allow the network transaction, you must enable MSDTC. To do this, follow these steps: a. Click Start, and then click Run. b. In the Run dialog box, type dcomcnfg.exe, and then click OK. c. In the Component Services window, expand Component Services, expand Computers, and then expand My Computer. d. Right-click My Computer, and then click Properties. e. In the My Computer Properties dialog box, click Security Configuration on the MSDTC tab. f. In the Security Configuration dialog box, click to select the Network DTC Access check box. g. To allow the distributed transaction to run on this computer from a remote computer, click to select the Allow Inbound check box. h. To allow the distributed transaction to run on a remote computer from this computer, click to select the Allow Outbound check box. i. Under the Transaction Manager Communication group, click to select the No Authentication Required option. j. In the Security Configuration dialog box, click OK. k. In the My Computer Properties dialog box, click OK.
3. Configure Windows Firewall to include the MSDTC program and to include port 135 as an exception. To do this, follow these steps:
a. Click Start, and then click Run. b. In the Run dialog box, type Firewall.cpl, and then click OK. c. In Control Panel, double-click Windows Firewall. d. In the Windows Firewall dialog box, click Add Program on the Exceptions tab. e. In the Add a Program dialog box, click Browse, and then locate the Msdtc.exe file. By default, the file is stored in the Installation drive:WindowsSystem32 folder. f. In the Add a Program dialog box, click OK. g. In the Windows Firewall dialog box, click to select the msdtc option in the Programs and Services list. h. Click Add Port on the Exceptions tab. i. In the Add a Port dialog box, type 135 in the Port number text box, and then click to select the TCP option. j. In the Add a Port dialog box, type a name for the exception in the Name text box, and then click OK. k. In the Windows Firewall dialog box, select the name that you used for the exception in step j in the Programs and Services list, and then click OK. [/code]
But, when the Windows firewal on the server is "On", remote connections are not allowed, despite I´ve configured the Exceptions on the firewall.
Hello! Recently, I set up server with Windows Web Server 2008 RC1, SQL 2008 Express beta, .NET 3.5, IIS 7. I'm running ASP.NET web application with SQL database. Everything works fine until the first application state on the server expires. After that, any postback that starts a new application state on the server and connects to the database, results in the following error: Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. Is this a bug that will be fixed in release of Windows / SQL or am I doing something wrong? Many thanks for help, Jan
Leon writes "I am trying to connect to a W2K3 Server's 2005 Reporting Server through my laptop's (WXP Pro SP2) SQL Server Management Studio.
I turned Port 1433 on in the server's Windows Firewall and was able to connect to the server's database engine from my laptop, but I have to turn Windows Firewall on the server off completely to be able to connect to the Reporting Server.
I have tried all the ports listed for SQL Server in the Microsoft documentation (TCP and UDP), but they seem to have no effect.
Can anyone tell me which port or ports I need to turn on in the server's firewall so that I can access Reporting Services through my laptop's SSMS?
We install SQL Express 2005 with a custom named instance. Since a named instance uses dynamic ports, how can I add this named instance to the Windows Firewall exception list? Previously with MSDE 2000 we installed as default, then I added port 1433 to the Firewall exception list.
Is there a way to install SQL Express to a static port (programmatically)? Or, is there a better method, like adding the SQL custom named instance service to the firewall exception list?
We are working with works with tool certification with windows server 2008 64 bit version. Ours is a web application, we are using SQL as Database. In windows server 2008 64 bit I installed 32 bit SQL 2005 when I am installing the application is ROOLING BACK while installing. But it€™s finely working with in windows server 2008 32 bit and 32 bit SQL 2005.
Then I Tried with 64 bit SQL 2005 in 64 bit windows server 2008 but our application is unable to recognize the SQL 64 bit.Our application is not showing any database but manuvally I am able to connect to Database.
Bouth 32 and 64 bit SQL 2005 are packed with SP2.
How to solve this problem do you have any Ideas€¦€¦€¦€¦€¦
When I try to install either SQL Server 2005 SP2 or SQL Server 2008 CTP 2 on a trial copy of Windows Server 2008 Web Edition I get no error messages but the SQL engines are not installed. I have been informed that the SQL Server restriction in place for Windows Server 2003 Web Edition is no longer in place for the 2008 version.
Hi, We have just created a new Windows 2008 server running SQL 2005 64 bit. I am in the process of migrating old SQL 2000 databases onto this new server. One of the databases required a SQL login for some Windows groups that get created from the SMS software. I'm having a problem when I go into create a new login, select object type Groups, from this location , I enter the object name and click Check Names and it finds it. I select okay and everything looks good. But when I click ok on the New Login screen, I get the 15401 error saying that Windows NT user or group not found. I have gone into the Server Manager - Groups and verified that the group exists, and it does. The only thing I see when I click properties is on the bottom right had side of the screen it says "Changes to a user's group membership are not effective until the next time the user logs on." It says this for all the groups on this server and I get the same error message when I try to add any group. I have had the user that is a memeber of this group log off and back on a few times, but it still says the same thing and I still get the same error.
Anyone have any ideas on what the problem might be? Is there something on the Windows 2008 server setup that we missed?
Hi All, After I installed sql server 2005 64bit standard edition on Windows Server Enterprise 2008 64bit, I cannot connect to the sql instance using the sql management studio on the same machine! I verified that:
service is running,
in surface area configuration: remote connections to local and remote are enabled, for TCP/IP and named pipes.
ran the command netstat -avn| findstr 49279 to make sure that the server is listening.
firewall is off, but this does not matter since I'm connecting locally to local instance
I'm using domain controller account to login to sql server / also tried the sa account. what else can be wrong?
Does anyone know how to properly install SQL server 2005 express reporting services on windows server 2008. When ever i try to access the report manager I get an error "Cannot access the remote server" even though the report server is on the local machine. I only have the web server role installed on the server. Im still quite a newbie at managing servers so please keep it as simple as possible. Thanks Matthew
Is it possible to install SQL Server 2005 Eval on a Virtual PC 2007 client running Server 2008 Beta? Nothing says it isn't possible, it says I need to service pack it right away, but before it gets started it comes up with the error 'sqlcu.dll failed to load'. Anyone know what this is all about?
I would like to ask you all a few questions. Please kindly inform me the related links if this topic is already brought before.
Is SQL Server 2005 Standard Edition compatible with Windows Server 2008? Can it run well there? If not, what do I need in order to install it on my server?
Thank you so much for your kind attention and look forward to hearing from you all soon.
I just installed Windows Server 2008. The installation also included Web Server.
When I tried to install SQL Server, I got the following warning:
IIS Feature Requirement (Warning)
Messag
IIS Feature Requirement
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Can somebody advise me on how I can resolve this warning? Would running SP2 take care of this?
I'm trying to install SQL Server 2005 Enterprise Edition 64-bit on a 64-bit instance of Windows 2008 running as Server Core. I read about an issue in KB article 920201, but I don't even get that far. The setup first tries to install .NET Framework 2.0, which fails with error message: Error 70243 installing .NET Framework 2.0
I tried installing .NET Framework separately, which indicates that I need to install Internet Explorer 5.01. I'm reluctant to try that, so I'd like to know if the people that actually got to the issue in KB920201 installed IE first (is that even possible?).
Im trying to install the SQL Server Compact Tools in Windows Server 2008, but the installation program won´t let me continue since it says that I must install the IIS Backward Compatibility Tools. The problem is that I can´t find where I do that.
I know that Windows Server 2008 is not listed as a supported os for the server tools, but surely I must at least be able to install them?
Hi, I have a Windows 2008 server 64-bit SP1 and I have installed SQL 2005 SP2 Enterprise Edition 64-bit. My current version is 9.00.3042.00. I am trying to configure Reporting Services and I am having lots of trouble getting the Application Pools to work properly. I have followed the Microsoft Technet paper 839480 "How to Install and Configure Reporting Services on Windows Server 2008". In the "Configure Reporting Services" part, I have successfully configured everything (all arrows are green) and have the following setup:
Report Server Virtual dir: ReportServer Default Web Site Report Manager Virtual dir: Reports Defualt Web Site Windows Service Identity: ReportServer with a service acct login Web Service Identity: Report Server: ReportServer, Report Manager: DefaultAppPool (I get an error when I try to configure it to anything else: ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 800708AC at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)
The one thing I notice in the SQL Server configuration manager is that there is a red dot next to the SQL Reporting Services services even though the green arrow is there to show it is running.
When I look in IIS7, I see the application pools Reports and ReportServer and they are both in Integrated mode. When I try to go to http://localhost/reportserver, it gives an error. It will work if I change both application pools to classic. But then when I try to go to http://localhost/reports, I get an error:
"REQUEST IS NOT AVAILABLE IN THIS CONTEXT".
I have read up on IIS7 and it says that: "This error is due to a design change in the IIS7 Integrated pipeline that makes the request context unavailable in Application_Start event. When using the Classic mode (the only mode when running on previous versions of IIS), the request context used to be available, even though the Application_Start event has always been intended as a global and request-agnostic event in the application lifetime."
So, how do I configure these application pools to work using IIS7 with SQL 2005 Reporting Services on a Windows 2008 server? I have tried all kinds of different things based on what I am reading on the net and nothing is working. Anybody have any suggestions?
Hye all, running WHS 2008, I try to install SQL Server 2005 with reporting services, but on install, in "components to install" wizard, the reporting services box is hided. I can't check this box :/ Do you know whats wrong ? if anyone knows the problem, thanks in advance.
I have read over the feature set and I really don't see a huge reasons to jump on the bus. There are a few niceties like IP enhancements, cluster enhancements and maybe bitlocker for the backup drive. Am I missing something?
My ISP recently had me reset my TCP/IP stack. After that, Norton PersonalFirewall prompted me twice that SQL Server was trying to access theInternet. Both times I responded to allow it to and to always use thataction. Now I am not able to use SQL Server with NPF enabled. If I disableNPF, SQL Server works fine.I am using the desktop edition of SQL Server 7, on a standalone PC, notconnected to a server. I have been using SQL Server and NPF together forover a year. Now, since my TCP/IP stack was reset, NPF interferes with SQLServer.Anyone have any experience with this?Thanks,Neil
I am trying to connect to SQL Server 7.0 from a web server. The web server is outside our firewall, SQL Server is inside the firewall. I want to use a multiprotocol connection so I can encrypt it. We have port 1433 open on our firewall for TCP/IP from SQL Server. When I connect with just TCP/IP it works. When I switch to multiprotocol it fails with error code 1701. I can connect to the SQL Server box from inside the firewall using multiprotocol. My theory is that when you use multiprotocol you are using another port than 1433. Is this the answer?
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?
Hello,We use Informix and MySQL on linux/unix to drive our web application.SQL*Server is used only for backend enterprise applications within thefirewall. I am trying to get the management to use SQL*Server outside thefirewall. They tell me there are security issues with Microsoft products,including SQL*Server, that make it vulnerable to attacks outside thefirewall. Can someone please point me to white papers/documentation thatsuggests how SQL*Server can be used securely outside the firewall? I thinkif I put SQL*server on it's own box and open it up only to the applicationson our web servers, we should be secure. However, I need hard evidence.Thanks.- Rajesh
Is there any concerns or problems with forward a port to SQL server from our internet firewall so that you can access the databases over the internet? Is it a standard practice to do this in order to remotely access the SQL server. Or is there a better way to do this? Also, if it is ok to do this are any things you need to do to enhance your security from vulnerabilities being open to the internet.
Any suggestions or comments would be appreciated on this subject.
I cannot seem to find the definitive how-to guide for this. Can anyone point me in the right direction?
I have SQL Server 2005 (x64) already running on Windows 2003 R2 (x64). I'm having difficulty trying to expose it the Internet.
Using the Surface Area Configuration tool I can see that remote connections using TCP/IP is enabled. I also made the machine administrator a member of the SysAdmin role from here too.
In Windows Firewall "SQL Server" and "Web" are already checked as exceptions.
I know that SQL Server uses port 1433 and I also read somewhere that clients connecting to SQL Server communicate on a random port between 1024 and 5000. So, on my router (Netgear WNR854T) I'm forwarding ports 1024 through 5000 to the machine where SQL Server lives.
In my connection string I'm using the IP address of the SQL Server machine with ":1433" appended to the address. Yet I cannot connect to SQL Server. Am I missing anything?
I have got a MTS Server and SQL server 7 in different boxes. However, MTS only communicates to SQL server when there is no firewall while it doesn't work when there is a firewall between them. Any idea I can solve this problem?
Can anyone tell me if there's a recommended way to link from a SQL 2000 SP4 DB through a firewall to SQL 2005? I have tried with SQLOLEDB but this uses NETBios which is not secure. Or is there a way to tell it not to use NETBios? SET @provdetail = 'DRIVER={SQL SERVER};SERVER=<IP address>;Trusted_connection=Yes' EXEC Master..sp_addlinkedserver @server = ,'<IP address>', @srvproduct = '', @provider = 'SQLOLEDB', @provstr = @provdetail , @catalog = 'TestDB', @datasrc ='<IP address>DB1'