I€™m quite new to SQL Server so maybe this is an easy question but I haven€™t found the answer after 3+ hours of Googling and experimenting.
I have a simple set up €“ two computers named HELEN and DELORES, both running Win XP Pro, SP2. These machines are connected via a home network and both belong to the same Workgroup. There€™s no Domain involved. HELEN is running SQL Server Express while DELORES is the €śclient€?, running SQL Server Management Studio Express. I am using €śWindows Authentication€? and Named Pipes to allow DELORES to work with the SQL Server Express instance on HELEN.
I have a general understanding of €śWindows Authentication€? and I was hoping someone could fill in the gaps. I realize €śWindows Authentication€? uses the underlying Windows User Accounts on the server to validate incoming connections.
I€™m sometimes having a problem in connecting SQL Server Management Studio Express (running on DELORES) to the SQL Server Express instance (running on HELEN). This problem may be due to a lack of understanding of Windows User Accounts.
I€™ve found that if I use the exact *same* username *and* passwords on both machines, SQL Server Management Studio Express has no problem connecting to HELEN€™s SQL Server Express instance. If I change the username and/or password on only one of the machines, the connection fails. Also, if I keep the usernames the same on both machines but I delete the passwords, the connection fails again.
I realize I can set up a user account on HELEN. Do I then have to set up the same user account (with the same non-blank password) on Delores? So far, this is the method that€™s been successful. Is it possible for me to tell SQL Server Management Studio Express to use a particular account (username/password) when connecting to HELEN via Named Pipes? If so, how is that specified?
I admit to my confusion. Any help would be greatly appreciated.
I€™m quite new to SQL Server so maybe this is an easy question but I haven€™t found the answer after 3+ hours of Googling and experimenting.
I have a simple set up €“ two computers named HELEN and DELORES, both running Win XP Pro, SP2. These machines are connected via a home network and both belong to the same Workgroup. There€™s no Domain involved. HELEN is running SQL Server Express while DELORES is the €śclient€?, running SQL Server Management Studio Express. I am using €śWindows Authentication€? and Named Pipes to allow DELORES to work with the SQL Server Express instance on HELEN.
I have a general understanding of €śWindows Authentication€? and I was hoping someone could fill in the gaps. I realize €śWindows Authentication€? uses the underlying Windows User Accounts on the server to validate incoming connections.
I€™m sometimes having a problem in connecting SQL Server Management Studio Express (running on DELORES) to the SQL Server Express instance (running on HELEN). This problem may be due to a lack of understanding of Windows User Accounts.
I€™ve found that if I use the exact *same* username *and* passwords on both machines, SQL Server Management Studio Express has no problem connecting to HELEN€™s SQL Server Express instance. If I change the username and/or password on only one of the machines, however, the connection fails. Also, if I keep the usernames the same on both machines but I delete the passwords, the connection fails again.
I realize I can set up a user account on HELEN. Do I then have to set up the same user account (with the same non-blank password) on Delores? So far, this is the method that€™s been successful. Is it possible for me to tell SQL Server Management Studio Express to use a particular account (username/password) when connecting to HELEN via Named Pipes? If so, how is that specified?
I admit to my confusion. Any help would be greatly appreciated.
I'm trying to implement a SSAS Project in a Virtual Machine using a private network. When I try to deploy the solution the program gives me the following error:
I already have a Windows Authentication but still gives me that error.
I'm trying to connect to an instance of MSDE 2000 from Visual Studio 2005 over a home network. Although I know how to connect to a database from Visual Studio, I'm pretty clueless about configuring Sql Server to allow the connection (I can connect with no problem when I do so from the same computer). Also, with experimenting I've created a bunch of instances of Sql Server that I don't really need and am not sure how to get rid of them. Thanks in advance for any help.
-Dave
I don't know if this will help, but I've already tried enabling all of the network protocols in the instance. Also, I can easily connect to an Access database over the network.
Hi there,I have installed MS SQL Server 2005 on my machine with windows authentication. But now I want to switch the authentication mode to SQL Authentication. I am unable to switch, I can’t find the proper way to do so here in 2005.Could any one help me in doing this?Thank you,-Ahsan
When using my Work laptop while at home, how can I log into an SQLServer Express 2005 database on a home server, using Windows Authentication, without having to VPN in and log onto the network at Work? If I VPN into work then I can connect to my home db just fine.
I have a laptop which I carry from work to home each day. I'm a Domain Admin at work so my network login name is DOMAINjoe. At home I have 5 PCs in a home network, WorkGroup is WORKGROUP. When I carry my laptop home I log in exactly as I do at work. All is fine. File sharing, printer sharing, & internet all work between my 5 PCs.
I installed SQLServer Express 2005 on a home PC I use as a server (Vista Business edition). Home server's name is STAR. I developed a database called AddressBk on my laptop (Visual Studio 2008) using my laptop's local copy of SQLServerExpress. App works fine. I copied the Db files onto my home server STAR. My user name on STAR is Joe2, so while logged onto Star as Joe2 I used Star's SQLServer Management Studio Express to connect the AddressBk db to Star's copy of SQLServer Express. All is fine.
Now if I use my LapTop on my home network and try to connect to AddressBk on STAR I get a connection error. I get the error whether connecting using SQLServer Management Studio Express or using Visual Studio 2008. The SQLServer Management Studio Express connection screen shows I'm connecting using Windows Authentication and my User Name is DOMAINjoe. I presume this is the problem as I can not add a user on Star with a Domain Name. Other PCs on my home network can connect to AddressBk db on Star without a problem. If my labtop VPNs into work then I can connect just fine.
Here is the connection string my App uses. Data Source=STARSQLEXPRESS;Initial Catalog=AddressBk;Integrated Security=True;connection timeout=60
How can I connect to my db without having to VPN into work?
(Using win2k, sqlserver2k, framework 1.1) I have an fairly data-heavy application that uses Windows authentication (Trusted connection/aspnet account) to connect to Sql Server. The site uses IIS basic authentication.
On the dev server everything works fine but when I move to the live server things get strange and it starts to crawl along. (Pages load OK but then it just crawls as it loads the datagrids etc. Sometimes it brings back incomplete/incorrect data )
BUT When I use Sql Authentication to connect to Sql Server and there is no problem at all!
Ok, there is something obviously wrong with the live server (which is identical setup to dev)but I dont know where to start.
I've got two applications which both have a database on my MS SQL 2000 server. The problem is, one application must use Windows Integrated Authentication (which it is currently using and cannot be changed) whilst the other application which I'm trying to configure must use a SQL password.
Since the server has already been configured to use Windows Integrated Authentication for the existing database and application, how do I configure the other database to use the SQL password?
My work is using a shared application which accesses a MSSQL 2000 database. To access the application, the folder on the Windows 2003 Server is shared and users can access the folder through a shared drive.
For the application to access the database, it uses an ODBC connection to the MSSQL server which originally used the SA password.
We have recently switched to using Windows Integrated Authentication because we believe it offers a higher level of security. However the only way in which we have been able to enable this is to add the windows users to the SQL server.
The problem with this is that the application sets permissions for individual users on what records they can see within the database. We have found that by adding the windows users to the SQL Server, they can bypass the permissions the set by the application by simply using any application that can use an ODBC connection, such as Enterprise Manager, and see all the database.
One way around this would be to set up domains of users with access privileges to the tables which reflect the permissions set by the application, and configuring a view of the data so they may only see the records that they have permissions to. However to do this would require a high administrative cost to ensure that changes made in the application are reflected in the privileges of the SQL server.
Instead, is there a way the SQL server can authenticate that the ODBC connection is coming from the correct application using Windows Integrated Authentication?
This would allow the applcation to determine security, and stop users from connecting to the SQL server using other applications.
Alternatively, can the SQL server, using Windows Integrated Authentication, also ask the application to supply a username and password?
Any help with this matter would be greatly appreciated.
I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.
My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.
I enabled all the protocols and all the ports I disabled windows firewall and antivirus (eset nod32) I installed all service packs available I have also installed Visual Studio 2005 without installing sqlexpress
But nothing happens!
Please i am very desperate, any information will be gratefully accepted.
This is my installation Information
Code Snippet
Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft MSXML 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.6001.18000 Microsoft .NET Framework 2.0.50727.1434 Operating System 6.0.6001
I'm green on this networking stuff so any help is greatly appreciated.
I have setup my home computer as a server and assigned a static IP to it. I installed SQL Server 2005 Developer and allowed remote connections to it through the Surface Area Config tool, added port 1433 TCP and 1434 UDP to firewall's exception list, and started the SQL Server Browser service.
Now I can't seem to remote connect to this SQL Server from my office network. Is there something I'm doing wrong here?
I just got Visual Studio 6 Enterprise which includes SQL Server7. However, when I try to install SQL7 (Standard Edition ?) onWindows XP Home it only installs the client components and notthe server component. The install routine claims this is becauseof the version of Windows I am using.Now I know that IIS isn't supposed to be installable on WindowsXP Home but it is with a fairly straight forward hack, so what Iwas wondering was is there a way to get SQL7 Standard installedon Windows XP Home (maybe with a similar sort of hack)?Failing that (and assuming the SQL7 in VS6EE is "Standard") doesSQL7 Desktop work on Windows XP Home? If so where can I get it(haven't seen one so far on eBay)?Regards PLST
I am new to servers and when I try to learn about them I get confused, because the information does not list a server in XP, but they keep it separate from Microsoft SQL Server, like XP has it's own server. Can someone help clarify for me what the versions of SQL servers are?
Say, I have configured my SQL to use Mixed Authentication. Now, I have a applicaiton which uses my SQL Server. The application just creates a database in SQL Server and uses the database to store its information.
This application also has a SYSTEM DSN under ODBC through which it accesses the database. For the application to access this database, should I only use SA (as my SQL instance is configured to use Mixed Authentication) or can I use Windows Authentcation too...
If I should only use SA, do we have a documentation which talks about this.
For using different services of SQL SERVER 2005 which is better... Windows Authentication or SQL Server Authentication? what are the advantages and disadvantages of both?
Ive seen several sellers, both retail and on ebay, who say that sql server2000 developeredition will run on windows xp home edition. Is this true? Some articlesI've seen imply yeswhile other articles imply no. I'm trying to learn sql server and a lot ofbooks I've purchaseoffer a 120 day evaluation. I'd prefer to buy an edition that I can affordand will give me boththe server and tools.A seller on ebay is selling the developer edition and it's price is withinmy budget. I don't wantto buy it if it won't install on windows xp home.Any help would be great. Thanks
I am trying to install SQL Express on Window Home XP and SCC is returning the following error:
The SQL Server Configuration Checker cannot b execute due to WMI configuration on the machine ..... Error 2147942405 (0X80070005).
I tried running the following batch file which I believe resolved the same issue that someone else raised earlier (though I am not sure whether the OS was Home XP)
Will upgrading from XP Home to XP Professional (academic version) help me install SQL express successfully>
The Batch file I ran looks like this:
FIXWMI.CMD ------------------------
@echo on cd /d c: emp if not exist %windir%system32wbem goto TryInstall cd /d %windir%system32wbem net stop winmgmt winmgmt /kill if exist Rep_bak rd Rep_bak /s /q rename Repository Rep_bak for %%i in (*.dll) do RegSvr32 -s %%i for %%i in (*.exe) do call :FixSrv %%i for %%i in (*.mof,*.mfl) do Mofcomp %%i net start winmgmt goto End
:FixSrv if /I (%1) == (wbemcntl.exe) goto SkipSrv if /I (%1) == (wbemtest.exe) goto SkipSrv if /I (%1) == (mofcomp.exe) goto SkipSrv %1 /RegServer
:SkipSrv goto End
:TryInstall if not exist wmicore.exe goto End wmicore /s net start winmgmt :End
I have to deal with a private network of laptops which are all equiped with preinstalled "Windows XP home"
I've installed SQLExpress on one of these, but I cannot connect on it from the rest of the laptops. (I've successfuly done this with "Windows XP profesional" though, and local connections work fine as well).
I've already setup the SQLExpress to accept conections throuigh TCP/IP but I can not think of something else. (Security comes to mind, but I do not know how to resolve it on "Windows XP Home").
I wanted to install SQL Server 2005 Express Edition, instead of installing .Net Framework 2.0, I installed .Net Framework 3.5. When I tried to install SQL Server 2005 Express Edition I received the following error:
SQL_ERROR (-1) in OdbcStatement::execute_batch sqlstate=42000, level=16, state=2, native_error=7404, msg=[Microsoft][SQL Native Client][SQL Server]The server could not load DCOM. Error Code: 0x80071cec (7404) Windows Error Text: Source File Name: libodbc_statement.h Compiler Timestamp: Wed Jun 14 16:28:15 2006 Function Name: OdbcStatement::execute_batch@sysdbupg.sql@56 Source Line Number: 91
I then decided maybe I do need .net framework 2.0, but when I try to install it it says it's already included with the OS.
But the "Programs and Featuers" only list .Net Framework 1.1 and .Net Framework 1,1 Hotfix (KB92979).
I uninstalled .Net Framework 3.5 and tried to install .Net Framework 2.0 again, but it still says it's included in the OS.
After uninstalling .Net Framework 3.5, I tried to install SQL Server 2005 Express Edition, but still received the above error message.
Is .Net Framework 2.0 included with Windows Vista Home Edition?
If it is, any ideas in solving the Server 2005 Express Edition installation error?
Hi Experts, Can anyone help me to identify the problem? The situation of my problem is : My company network in clients side is running either Window XP Pro or Window Xp Home.The problem occur when i access from Window XP Home to Server (Window Server 2003) an error pop up Sql Express Error 18452. It is worked fine in WIndow XP Pro version. Thanks for anyone provide me a solution.
Hi, I'm having a problem installing SQL2005 Developer on Windows Vista.
At the System Configuration check page, I'm getting the IIS Feature Requirement item telling me IIS is not installed or disabled. This is not the case.
I have read article http://support.microsoft.com/kb/920201 and switched on the IIS components as specified.
I've tried installing with Firewall, virus checker etc switched off. Every time I get the same problem. This is an issue, as I specifically need Reporting Services installed.
I am trying to install SQL Server 2005 on Windows Vista Home Premium edition, when I run the Installer I received are the following error message.
IIS Feature Requirement (Warning)
Messages
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.
I already configure IIS7 with all feature, but system still generate above mentioned message.
I wonder if it is possible to set forms authentication for report manager but leave report server "as it is". I need to authenticate users from external LDAP and can't use windows authentication for report manager, but I would also like to leave report server open for anonymous users. In that way authenticated administrators could create reports which anonymous users could read.
I tested the Security Extension Sample and got it working when I rewrote the authentication part with my own LDAP authentication.
If I have understood correctly, the report manager is just application inside report server so is it possible to use forms authentication with one application but still leave the report server with Windows authentication?
I am in the process of rolling out a sql server 2005 enterprise install and had a question regarding authentication. We will be providing sql hosting for a number of groups on our campus, many who are not using our campus-wide active directory, though they all have an AD account.
Windows authentication via the management studio appears to use your AD authentication tokens and will not allow them to enter a username/password combo. Is there any way to configure this?
I would like to use our campus AD for obvious reasons but if there is a requirement for passing tokens this isn't going to work right? It's also going to make database mirroring more of a challenge.
My SQLExpress seems to be set for windows authentication and not sql server authentication ... I am not quite sure why it is set to windows authentication - I installed this with Visual Studio 2005 and it just seemed to be set that way.Am I able to change this - if I choose sql authentication when connecting I get an errorIf someone could answer this point I would be most grateful !!Patrick
In an effort to eliminate the need to code accounts and passwords into the VB Com calling stored procedures, I would like to use Windows Authentication. I have setup the account that the com is running under to have access to the database. How does this change my connection string. Do I just drop the account and password parameters or do I need to let it know somehow that I want to use Windows Authentication?
I'm having problems with windows authentication. I'm new to using using Microsoft SQL Server. I just migrated from powerbuilder 8 to powerbuilder 10. I'm using OLE DB and can't get the windows authentication to work within the application. Can anyone help....
Hi, I am wondering that do we need to create the separate login at SQL SERVER (server) for all the user using the application for the windows authentication?
How do the windows authentication works? I have a apllication and SQL SERVER (SERVER) running on the same machine. Any user from the same domain can access the application. Application is interacting with the DB through Windows Authentication. Now my question is whether do we need to authenticate each user from the domain at the DB level. That is to craete the login id for all the user for windows authentication.
