Re: Cannot open remote connection to Dql Server

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



If a PC is using XP Home then the user will authenticate as
guest. Even with matching logins and passwords it will still
be guest logging in under windows authentication. XP Home
uses simple file sharing.

-Sue

On Mon, 20 Mar 2006 18:59:26 -0800, cnuk
<cnuk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

There must be more to it than that. I am in a workgroup on a home network.
I have matching usernames and passwords on every machine and I cannot get
passed the "Login failed for remotemachine\Guest" prompt. Only fix was to
use mixed mode and add a user as you suggested. Works for now but I'd like
to know why windows authentication won't work.

Thanks for the help.

"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: VB app connect THROUGH proxy to a remote SQL database
    ... The whole "HTTP proxy is way more secure than allowing outgoing ... the client app and the SQL server are on ... incoming connections to the SQL server are not the problem - it's ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... If I cut the maximum number of connections to for ... SQL Server simply blocks any further try to open another table until I close ... This doesn't happen with the SQL Server 2000 but with SQL Server ... No, I think ms-sql-s means that SQL 2000 is using port 1433, which is ...
    (microsoft.public.sqlserver.connect)
  • Re: SMTP Virtual Server Settings --- Lots of Sessions and Junk in
    ... successfully authenticate to relay, regardless of the list above" in case ... And under authentication you can uncheck all but the anoumous authentication ... if you are on a single server if you have more then one exchange server the ... connections trying to send spam) connections coming from companys or "Zombie ...
    (microsoft.public.exchange.admin)
  • Re: SQL Management Studio cannot connect remotely
    ... firewall has the TCP port 1433 and UDP port 1434 open). ... Server is listening on TCP port 1433. ... Use SQL Server Configuration ... protocol connections are using. ...
    (microsoft.public.sqlserver.connect)
  • Re: Login failed for user (null).
    ... authenticated connection with SQL server. ... Whether or not the remote service accepts the authentication from client ...
    (microsoft.public.dotnet.framework.aspnet.security)