Re: Cannot open remote connection to Dql Server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Jasper, thank you this is valuable information.

"Jasper Smith" wrote:

> > If I select 'Use Windows Authentication' the error is: "Login failed for
> > user 'remoteMachine\Guest'.
>
> Are you in a domain? If not then create a local user on the server that
> matches the user you are signed onto your client with (same user name and
> same password). This should then allow you to connect via Windows
> Authentication.
>
> > If I select 'Use SQL Server Authentication' the error is: "Login failed
> > for user 'Joe'. The user is not associated with a trusted SQL Server
> > connection.
>
> This error is because the server is configured for Windows Authentication
> only. You can change it to mixed mode on the server by using Management
> Studio and in Object Explorer Right Clicking the Server and clicking on
> Properties. Select the Security section and change the Server Authentication
> to SQL Server and Windows Authentication mode and click OK. You need to
> restart SQL Server for it to take effect. You'll also need to add a SQL
> login for yourself.
>
> --
> HTH
>
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Fred Exley" <fexley221@xxxxxxx> wrote in message
> news:OJmxNJh8FHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
> >
> > "Jasper Smith" <jasper_smith9@xxxxxxxxxxx> wrote in message
> > news:ORgVXQV8FHA.2716@xxxxxxxxxxxxxxxxxxxxxxx
> >> The Allow Remote Conections is not the correct setting (it controls the
> >> ability for remote servers to execute stored procedures on the local
> >> server via a linked server) The easiest thing to do is on the server go
> >> to Start>Programs>Microsoft SQL Server 2005>Configuration Tools>SQL
> >> Surface Area Configuration and click on Surface Area Configuration for
> >> Services And Connections. Under the Database Engine section on the left
> >> select Remote Connections and select the Local and remote connections
> >> radio burron and select Using both TCP/ip and named pipes and click
> >> Apply.
> >>
> >> --
> >> HTH
> >>
> >> Jasper Smith (SQL Server MVP)
> >> http://www.sqldbatips.com
> >> I support PASS - the definitive, global
> >> community for SQL Server professionals -
> >> http://www.sqlpass.org
> >>
> >> "BusIntelInstructor" <BusIntelInstructor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> >> in message news:0BD3DDB2-7C02-458A-A617-5B14D98BD002@xxxxxxxxxxxxxxxx
> >>>I have SQL 2005 Developer installed on one computer, and the Client tools
> >>> only on another. When I try to connect to te server from the client I
> >>> get an
> >>> error:
> >>> "Named pipes provider: Error 40. Could not open a connection to SQL
> >>> Server.
> >>> Microsoft SQL Server error 233."
> >>>
> >>> There is also a hint with the error message that says "...by default,
> >>> SQL
> >>> Server does not allow remote connections"
> >>>
> >>> Checking the Properties for the server, the Connections option, the
> >>> check
> >>> box for "Allow Remote Connections to this Server" is checked.
> >>>
> >>> Interestingly, I can connect to the Analysis Services Server on my
> >>> Server
> >>> computer from the client.
> >
> >
> > Hi. I'm having the same problem, and your suggestion gets me closer (my
> > remote computer sees the full server name now), but I still can't get past
> > the 'Test Connection' button (in configuring a SqlDataSource in VS2005).
> >
> > If I select 'Use Windows Authentication' the error is: "Login failed for
> > user 'remoteMachine\Guest'. I can't see how to change that it's looking
> > for Guest user, and user Guest is turned on anyway.
> >
> > If I select 'Use SQL Server Authentication' the error is: "Login failed
> > for user 'Joe'. The user is not associated with a trusted SQL Server
> > connection.
> >
> > I can remotely browse IIS websites on the server, and locally on the
> > server the connection to SQL server works fine, but I just can't see the
> > SQL Server database remotely. I even turned off the firewall as yet
> > another guess. Any other suggestions as to places to look will be much
> > appreciated.
> >
> > Thanks -Fred
> >
> >
>
>
>
.



Relevant Pages

  • Re: ADOCE 3.1 SDK
    ... ADOCE's provider cannot connect to a remote server. ... > I am attempting to access a remote SQL Server 2000 running on a Windows ... We desire to access a remote SQL Server 2000 via ADOCE and call ...
    (microsoft.public.windowsce.embedded.vc)
  • dts package transfer local file remote server idiosyncrasy
    ... purposes and the other at a remote location. ... I developed a DTS package on my local PC and on the local SQL Server ...
    (microsoft.public.sqlserver.dts)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Uninstall the SQL server from the SBS 2k3 server from add/remove programs ... Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT) ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I also checked the individual patch levels for the .NET drivers, SQL Server ... The SQL Server is fully patched, however Windows Update reported that the OS ... Lock pages in memory -- I guess you might have taken care of it as well. ...
    (microsoft.public.sqlserver.clustering)
  • Re: upsizing to SQL.
    ... I believe the correct term is now Remote Desktop.... ... Basically you would install a new Win2K3 box with however many licenses you ... > Terminal server is probably the best option. ... >> SQL Server doesn't magically make that problem go away. ...
    (microsoft.public.access.tablesdbdesign)