connecting to sql server (within windows domain) through linux?

Hi,

I'm planning to develop a small intranet to provide our organization
with documents online. I've decided to do this using jsp/servlets
using a tomcat server. For an operating system, I have chosen red hat
linux. However, I'd like to keep a small database on a sql server as
a datasource. However, this sql server is already part of our
organization's windows domain. I suspect I'll need to configure samba
so that other terminals on the windows domain will be able to reach
the intranet. What's the best manner in which to connect my linux
servlets to this sql server database? I suspect this may be
difficult, considering the sql server exists within a windows domain,
but as a beginner, what do I know. Perhaps someone could point me in
the right direction.Hi

You can use the JDBC driver to communicate with your SQL Server and use SQL
Server authentication to access the server. Samba is not needed at all this
may be a way to connect to an access database but SQL Server is a completely
different product.

John
"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> Hi,
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know.Perhapssomeonecouldpointmein
> the right direction.|||Dan (danhicks333@.gmail.com) writes:
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know. Perhaps someone could point me in
> the right direction.

I have never connected to SQL Server from Unix myself, but I happen to
maintain a page which summarizes the various options. Look at:
http://www.sommarskog.se/mssqlperl/unix.html

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||The SQL server I want to connect to does not have a public IP address.
I connect to this server from my other web server (part of the
windows domain)using the server name (treadstonesql). My thinking was
that if samba is configured correctly, I could connect to it the same
way my web server does. Does this help?

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> Hi
> You can use the JDBC driver to communicate with your SQL Server and use SQL
> Server authentication to access the server. Samba is not needed at all this
> may be a way to connect to an access database but SQL Server is a completely
> different product.
> John
> "Dan" <danhicks333@.gmail.com> wrote in message
> news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > Hi,
> > I'm planning to develop a small intranet to provide our organization
> > with documents online. I've decided to do this using jsp/servlets
> > using a tomcat server. For an operating system, I have chosen red hat
> > linux. However, I'd like to keep a small database on a sql server as
> > a datasource. However, this sql server is already part of our
> > organization's windows domain. I suspect I'll need to configure samba
> > so that other terminals on the windows domain will be able to reach
> > the intranet. What's the best manner in which to connect my linux
> > servlets to this sql server database? I suspect this may be
> > difficult, considering the sql server exists within a windows domain,
> > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > the right direction.|||Hi

The IPaddress does not have to be a public one (in fact it would be better
if it wasn't) The IP Address can be used when connecting instead of using a
lookup, you will need to set up the firewall rules so that you can talk on
the right ports (not necessarily the default ones!) between the two
machines.

I would not expect your second web server to be part of the internal domain,
this may mean that your whole domain is compromised if the web server is
compromised.

John

"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409120659.618cc1ae@.posting.google.c om...
> The SQL server I want to connect to does not have a public IP address.
> I connect to this server from my other web server (part of the
> windows domain)using the server name (treadstonesql). My thinking was
> that if samba is configured correctly, I could connect to it the same
> way my web server does. Does this help?
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> > Hi
> > You can use the JDBC driver to communicate with your SQL Server and use
SQL
> > Server authentication to access the server. Samba is not needed at all
this
> > may be a way to connect to an access database but SQL Server is a
completely
> > different product.
> > John
> > "Dan" <danhicks333@.gmail.com> wrote in message
> > news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > > Hi,
> > > > I'm planning to develop a small intranet to provide our organization
> > > with documents online. I've decided to do this using jsp/servlets
> > > using a tomcat server. For an operating system, I have chosen red hat
> > > linux. However, I'd like to keep a small database on a sql server as
> > > a datasource. However, this sql server is already part of our
> > > organization's windows domain. I suspect I'll need to configure samba
> > > so that other terminals on the windows domain will be able to reach
> > > the intranet. What's the best manner in which to connect my linux
> > > servlets to this sql server database? I suspect this may be
> > > difficult, considering the sql server exists within a windows domain,
> > > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > > the right direction.

Connecting to SQL Express on a hosted site

Folks.

I just moved my domain to GoDaddy.com. When I run my website locally, everything works fine.

When I ftp it to my server space on GoDaddy.com, I get a "remote connection" error. Does anyone have an example of a connection string I should be using to connect while on the server?

Thanks!

From looking at their website, they do not appear to offer SQL Server2005 or SQL Server 2005 Express. That'd be why you're getting theerror you are. I'm getting the same dang thing on my hostingservice - 1PlanHost.com. They, for some reason, will not installSQL Express... even though ALL of these starter kits, etc. are using itby default. It's making things quite bothersome for us developers!

If anyone figures out a way to force SQL Express to run within a shared hosting enviroment, let me know!|||

Thanks for your response. GoDaddy does offer SQL Server. You can configure it once you have purchased a hosting package. What they don't offer is any incling of support for it. If I find anything out, I'll let you know.

sqlsql

Connecting to SQL across Non-Trusted Domains

The problem I am having is this :
SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not show
as being alive in Enterprise Manager unless you map a drive to a server in t
he non-trusted domain.
Has anyone seem this problem before? Not sure whether this is related to Act
ive Directory.
Also all our SQL Instances use specific port numbers.
Thanks
CPNZSounds like the Agent polling is not able to contact the other servers
unless you map a drive allowing your server
to communicate with the others. This is more of a problem with disjoined
domains that SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||You can do the following.
Your SQL Server instances must be running as a LOCAL or Domain account. If
you configure a LOCAL account on the server you are trying to connect to
with the same username and password it will log in using this account.
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"CPNZ" <anonymous@.discussions.microsoft.com> wrote in message
news:72C261EE-AB91-45D1-BA20-EE1F805E3FD0@.microsoft.com...
> The problem I am having is this :
> SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not
show as being alive in Enterprise Manager unless you map a drive to a server
in the non-trusted domain.
> Has anyone seem this problem before? Not sure whether this is related to
Active Directory.
> Also all our SQL Instances use specific port numbers.
> Thanks
> CPNZ|||Okay. We have clients using Enterprise Manager, and they used to be able to
connect accross these domains using SQL authentication.
Kevin could there be an Active Directory issue stopping these services being
seen accross the domains? My server people say nothing has changed in AD,
but you never know. Also could you give a little more info on the Polling A
gent.
Thanks
Clint|||Hi Clint,
The SQL Server state polling is controlled in Enterprise Manager.
Go to the server you registered. Then Select from the menu, Tools ,
Options.
By default we poll servers every 10 seconds.
Check to see if you're clients connect using Named Pipes or TCP/IP sockets.
You'll be unable to connect to a remote server in an untrusted domain
using Named Pipes. Use the SQL Client network utility to specify tcp/ip as
the protocol to connect to the remote server.
Hope this helps.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connecting to SQL across Non-Trusted Domains

The problem I am having is this :
SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not show
as being alive in Enterprise Manager unless you map a drive to a server in t
he non-trusted domain.
Has anyone seem this problem before? Not sure whether this is related to Act
ive Directory.
Also all our SQL Instances use specific port numbers.
ThanksClint,
That's called "working as designed" I'm afraif - it's expecting there to be
an underlying NT authentication.

> The problem I am having is this :
> SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not sho
w as being alive in Enterprise Manager unless you map a drive to a server in
the non-trusted domain.
> Has anyone seem this problem before? Not sure whether this is related to A
ctive Directory.
> Also all our SQL Instances use specific port numbers.
> Thanks
>
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvfor...p?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq

Connecting to Analysis Services on different domain

Does anyone know how I can connecting to an analysis services cube that
is located on a different server/domain than the one I am developing
the report on.
I am able to remote connect to the server and process the cube, however
I don't know how to create a connection to the cube.
I am woring on the corp domain and the cube is located on the corp2
domain, server name cr2rchmiis10.
Thanks in advance for any help.
John CCan you set up a SQL linked server on a SQL server in the corp domain
that connects to the AS in the corp2 domain?
If you can get the linked server set up across domains, you can run
your query against the linked server in the corp domain.|||If you are using Analysis Services ENTERPRISE edition, you can connect to
Analysis Services through Http, and that would probably solve your problem.
If you are using AS Standard edition, you need to do something else. (Like
Potter suggested.)
With Analysis Services 2005 Enterprise edition
http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx
With ANalysis Services 2000 Enterprise edition:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/olapdmad/aghtconfig_4giq.asp
Kaisa
<john.r.carter@.bankofamerica.com> wrote in message
news:1135094407.938804.228280@.g14g2000cwa.googlegroups.com...
> Does anyone know how I can connecting to an analysis services cube that
> is located on a different server/domain than the one I am developing
> the report on.
> I am able to remote connect to the server and process the cube, however
> I don't know how to create a connection to the cube.
> I am woring on the corp domain and the cube is located on the corp2
> domain, server name cr2rchmiis10.
> Thanks in advance for any help.
> John C
>

Connecting to a DB in a non-trusted domain

SQL Server 2000 mainly, but also 2005 (Management Studio only)
We are restructuring our network and have created a new QA (clustered)
server in a new, non-trusted domain (named QA). To do the initial setup of
the server, I've been using rdp to login to the box and run EM there (the
server is 2000). The rdp login process is flawless.
When I attempt to create a New Server registration in EM, or MS I get the
error:
machine.qa.name.com - SQL Server does not exist access denied.
ConnectionOpen (Connect())
Checking the event log on the remote server, I see the attempted login with
the CORP domain, not the QA domain
So, I tried to create a local SQL Server login: QA\myname and when I check
the event log, I get the same CORP\myname "Unknown user, or bad password"
error. I've also tried entering the server as QA\machine.qa.name.com and
several other combinations.
I'm at a loss. I really need to register this server.
Thanks,
JayFWIW, I get two messages in the remote computers event log:
-- message #1 --
Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 680
Date: 11/6/2007
Time: 10:53:08 AM
User: NT AUTHORITY\SYSTEM
Computer: __QA_ClusterNode-A__
Description:
Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: __MyLoginName__
Source Workstation: __MyWorkstation__
Error Code: 0xC0000064
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
-- message #2
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: 11/6/2007
Time: 10:53:07 AM
User: NT AUTHORITY\SYSTEM
Computer: __QA_ClusterNode-A__
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name: MyLoginName
Domain: __MYDOMAIN__
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: __MyWorkStation__
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: __My_IP_Address__
Source Port: 0
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
"Jay" <nospan@.nospam.org> wrote in message
news:OymY1FKIIHA.4808@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2000 mainly, but also 2005 (Management Studio only)
> We are restructuring our network and have created a new QA (clustered)
> server in a new, non-trusted domain (named QA). To do the initial setup of
> the server, I've been using rdp to login to the box and run EM there (the
> server is 2000). The rdp login process is flawless.
> When I attempt to create a New Server registration in EM, or MS I get the
> error:
> machine.qa.name.com - SQL Server does not exist access denied.
> ConnectionOpen (Connect())
> Checking the event log on the remote server, I see the attempted login
> with the CORP domain, not the QA domain
> So, I tried to create a local SQL Server login: QA\myname and when I check
> the event log, I get the same CORP\myname "Unknown user, or bad password"
> error. I've also tried entering the server as QA\machine.qa.name.com and
> several other combinations.
> I'm at a loss. I really need to register this server.
> Thanks,
> Jay
>
>|||I have completly uninstalled all of my SQL Server instances and reinstalled
the 2000 tools and am still getting the error.
The only thing I can think of that could have caused this was that I had
previously changed all of the login accounts in services to local to fix a
domain issue that prevented my local instances from starting when the domain
policy was updated. However, as I said, I've removed everything.
"Jay" <nospan@.nospam.org> wrote in message
news:OymY1FKIIHA.4808@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2000 mainly, but also 2005 (Management Studio only)
> We are restructuring our network and have created a new QA (clustered)
> server in a new, non-trusted domain (named QA). To do the initial setup of
> the server, I've been using rdp to login to the box and run EM there (the
> server is 2000). The rdp login process is flawless.
> When I attempt to create a New Server registration in EM, or MS I get the
> error:
> machine.qa.name.com - SQL Server does not exist access denied.
> ConnectionOpen (Connect())
> Checking the event log on the remote server, I see the attempted login
> with the CORP domain, not the QA domain
> So, I tried to create a local SQL Server login: QA\myname and when I check
> the event log, I get the same CORP\myname "Unknown user, or bad password"
> error. I've also tried entering the server as QA\machine.qa.name.com and
> several other combinations.
> I'm at a loss. I really need to register this server.
> Thanks,
> Jay
>
>

Connecting SQL server 2000 from different domain.

Please help to connect SQL server 2000 on different domain.

Please correct if I m wrong.

System details as follows

Client

Domain : DomainA

System: System1

IP Address : 10.10.225.19

SQL server 2000 installed

SQL Server

Domain : DomainB

System: System2

IP Address : 10.108.22.19

SQl Server : System2\inst2 ( My database is under inst2 instance)

SQL login : TestUser1

Password : Users123

I have Opened firewall port to access 10.108.22.19 from 10.10.225.19

While connecting the SQL server “System2\inst2” from the client machine enterprise manager with the SQL authentication, I am getting error Login failed for user “TestUser1”

And I have noticed in the SQL server log the login attempt shows under System2 default instance ( no instance). Actually I want to connect system2\inst2.

Please let me know the steps to connect.

Thanks in advance.

For named instance, you also need to open UDP port 1434 for firewall on 10.108.22.19(the server). This is requried to find named instances. You said "default instance (no instance)", which errorlog were you checking?|||

Thanks for your reply,

I got solution and i am able to connect all my SQL servers from my domain.

It is a firewall issue , buy default they opened for 1433 it is goes to Default instance , but i need to connect a different SQL server instance.

then i opened firewall for that port it is connecting .

Thanks

Connecting MS, or EM to a server on a non-trusted domain

We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
Jay
Make sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com| http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:

> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>
|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...[vbcol=seagreen]
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:

Connecting MS, or EM to a server on a non-trusted domain

We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
JayMake sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com|http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:
> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
>> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
>> non-trusted Windows domain.
>> I can rdp to the machine just fine, but I can't get MS to connect.
>> My machine (and most servers) are in the HOME domain and the new server
>> is
>> in the non-trusted QA domain.
>> I've tried several combinations, including creating a SQL Server login
>> for
>> my use on the server - no joy.
>> I'm fairly certain this can work, but I'm out of idea's as to how ...
>> Thanks,
>> Jay
>>

Connecting MS, or EM to a server on a non-trusted domain

We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
JayMake sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com| http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:

> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...[vbcol=seagreen]
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
>

Connecting from Management studio with *another* windows account

I'm trying to connect to a SQL Server at work from my virtual PC> The
virtual PC is not logged in under my domain account as it is not part of
the domain.
I need to be able to connect to the domain account using Windows
Authentication. For other services (sourcesafe, printing, shares etc) I
can use "net use \\servername /user:domain\password " to connect under
another account. Sql Server Management studio however does not recognise
this and still tries to log in with vpc\administrator instead.
I'm unable to start the program using runas either (fails with unknown
user or bad password).
Is there a way to connect using a different account without resorting to
SQL accounts?
Jesse"Jesse Houwing" <jesse.houwing@.nospam-sogeti.nl> wrote in message
news:OBtjE$exGHA.1224@.TK2MSFTNGP03.phx.gbl...
> I'm trying to connect to a SQL Server at work from my virtual PC> The
> virtual PC is not logged in under my domain account as it is not part of
> the domain.
> I need to be able to connect to the domain account using Windows
> Authentication. For other services (sourcesafe, printing, shares etc) I
> can use "net use \\servername /user:domain\password " to connect under
> another account. Sql Server Management studio however does not recognise
> this and still tries to log in with vpc\administrator instead.
> I'm unable to start the program using runas either (fails with unknown
> user or bad password).
> Is there a way to connect using a different account without resorting to
> SQL accounts?
>
Without joining your VPC to the domain, you can create local accounts
accounts on both your VPC and your SQL Server (not its domain). The
accounts must have the same password, and appropriate group memberships on
each box. Then Windows will use "workgroup authentication" and your local
user MyVPC\Fred will be able to access resources on the SQL Server as
MySQLServer\Fred.
This is a different mechanism from "net use", and works for all kinds of
authenticated traffic.
David|||* David Browne wrote, On 22-8-2006 16:14:
> "Jesse Houwing" <jesse.houwing@.nospam-sogeti.nl> wrote in message
> news:OBtjE$exGHA.1224@.TK2MSFTNGP03.phx.gbl...
>
> Without joining your VPC to the domain, you can create local accounts
> accounts on both your VPC and your SQL Server (not its domain). The
> accounts must have the same password, and appropriate group memberships on
> each box. Then Windows will use "workgroup authentication" and your local
> user MyVPC\Fred will be able to access resources on the SQL Server as
> MySQLServer\Fred.
> This is a different mechanism from "net use", and works for all kinds of
> authenticated traffic.
This is unfortunately no option
This would force the creation of many extra users for which passwords
need to be synchronised and such...
Jesse

Connecting from Management studio with *another* windows account

I'm trying to connect to a SQL Server at work from my virtual PC> The
virtual PC is not logged in under my domain account as it is not part of
the domain.
I need to be able to connect to the domain account using Windows
Authentication. For other services (sourcesafe, printing, shares etc) I
can use "net use \\servername /user:domain\password " to connect under
another account. Sql Server Management studio however does not recognise
this and still tries to log in with vpc\administrator instead.
I'm unable to start the program using runas either (fails with unknown
user or bad password).
Is there a way to connect using a different account without resorting to
SQL accounts?
Jesse"Jesse Houwing" <jesse.houwing@.nospam-sogeti.nl> wrote in message
news:OBtjE$exGHA.1224@.TK2MSFTNGP03.phx.gbl...
> I'm trying to connect to a SQL Server at work from my virtual PC> The
> virtual PC is not logged in under my domain account as it is not part of
> the domain.
> I need to be able to connect to the domain account using Windows
> Authentication. For other services (sourcesafe, printing, shares etc) I
> can use "net use \\servername /user:domain\password " to connect under
> another account. Sql Server Management studio however does not recognise
> this and still tries to log in with vpc\administrator instead.
> I'm unable to start the program using runas either (fails with unknown
> user or bad password).
> Is there a way to connect using a different account without resorting to
> SQL accounts?
>
Without joining your VPC to the domain, you can create local accounts
accounts on both your VPC and your SQL Server (not its domain). The
accounts must have the same password, and appropriate group memberships on
each box. Then Windows will use "workgroup authentication" and your local
user MyVPC\Fred will be able to access resources on the SQL Server as
MySQLServer\Fred.
This is a different mechanism from "net use", and works for all kinds of
authenticated traffic.
David|||* David Browne wrote, On 22-8-2006 16:14:
> "Jesse Houwing" <jesse.houwing@.nospam-sogeti.nl> wrote in message
> news:OBtjE$exGHA.1224@.TK2MSFTNGP03.phx.gbl...
>> I'm trying to connect to a SQL Server at work from my virtual PC> The
>> virtual PC is not logged in under my domain account as it is not part of
>> the domain.
>> I need to be able to connect to the domain account using Windows
>> Authentication. For other services (sourcesafe, printing, shares etc) I
>> can use "net use \\servername /user:domain\password " to connect under
>> another account. Sql Server Management studio however does not recognise
>> this and still tries to log in with vpc\administrator instead.
>> I'm unable to start the program using runas either (fails with unknown
>> user or bad password).
>> Is there a way to connect using a different account without resorting to
>> SQL accounts?
>
> Without joining your VPC to the domain, you can create local accounts
> accounts on both your VPC and your SQL Server (not its domain). The
> accounts must have the same password, and appropriate group memberships on
> each box. Then Windows will use "workgroup authentication" and your local
> user MyVPC\Fred will be able to access resources on the SQL Server as
> MySQLServer\Fred.
> This is a different mechanism from "net use", and works for all kinds of
> authenticated traffic.
This is unfortunately no option :(
This would force the creation of many extra users for which passwords
need to be synchronised and such...
Jesse

Connecting (ODBC) to SQL 2005 Express from different domain with trust

Hi!

I am trying to establish connection from different domain using ODBC driver with no luck!

I am able to do it within my domain from any place, but it fails from outside. I have two-ways trust established between domains. Users are able to see and use resources both ways.

When I create ODBC it doesn't matter if I use SQL or Windows NT authenctication, I am getting error:

Connection Failed:

SQLState: '01000'

SQLServer Error: 11004

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (getbyhostname()() )

Connectio Failed:

SQLState: '08001'

SQL Server Error: 11

I tried to set it with TCP Static Port or Dynamic. No difference.

What should I look into?

Any ideas? Any help?

Thanks.

Did you try using the ip address ? Maybe the name cannot be resolved ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Yes I tried. Does SQl 2005 Express have any limitations as far as Connections from other domains?

Any other ideas.

|||

No, it don′t has such things. Is the server pingable ? SQL Server uses a dynamic port not he standard port. The SQL Server browser service will redirect incoming request to the appripiate dynamic port. Therefore the service has to be started on the server system. Did you check that ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

I am able to ping server, able to access files on server using UNC.

SQL Server browser is running on my server. Everything is in place, yet I can't logon.

I tried setting up ODBC Data Source with both Windows NT and SQL account authentication with no luck.

SQL actually is letting me create login using user name from other domain. I can do Find and discover users from other domain.

When it gets to making connection with server from their side it just dont see it.

Is that possible that because server is installed as a named instance I am having that problem?

|||

There has to be a firewall in between which block the traffic (bit not ICMP). Make sure you configured the firewall to let the appropiate ports open for connecting.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||Apparently I had to change port in All IP to 1433. Leaving it default dynamic was the problem. I changed all settings to listen to 1433 and here we go. Thank you for your help.

Connecting (ODBC) to SQL 2005 Express from different domain with trust

Hi!

I am trying to establish connection from different domain using ODBC driver with no luck!

I am able to do it within my domain from any place, but it fails from outside. I have two-ways trust established between domains. Users are able to see and use resources both ways.

When I create ODBC it doesn't matter if I use SQL or Windows NT authenctication, I am getting error:

Connection Failed:

SQLState: '01000'

SQLServer Error: 11004

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (getbyhostname()() )

Connectio Failed:

SQLState: '08001'

SQL Server Error: 11

I tried to set it with TCP Static Port or Dynamic. No difference.

What should I look into?

Any ideas? Any help?

Thanks.

Did you try using the ip address ? Maybe the name cannot be resolved ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Yes I tried. Does SQl 2005 Express have any limitations as far as Connections from other domains?

Any other ideas.

|||

No, it don′t has such things. Is the server pingable ? SQL Server uses a dynamic port not he standard port. The SQL Server browser service will redirect incoming request to the appripiate dynamic port. Therefore the service has to be started on the server system. Did you check that ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

I am able to ping server, able to access files on server using UNC.

SQL Server browser is running on my server. Everything is in place, yet I can't logon.

I tried setting up ODBC Data Source with both Windows NT and SQL account authentication with no luck.

SQL actually is letting me create login using user name from other domain. I can do Find and discover users from other domain.

When it gets to making connection with server from their side it just dont see it.

Is that possible that because server is installed as a named instance I am having that problem?

|||

There has to be a firewall in between which block the traffic (bit not ICMP). Make sure you configured the firewall to let the appropiate ports open for connecting.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||Apparently I had to change port in All IP to 1433. Leaving it default dynamic was the problem. I changed all settings to listen to 1433 and here we go. Thank you for your help.

Connecting (ODBC) to SQL 2005 Express from different domain with trust

Hi!

I am trying to establish connection from different domain using ODBC driver with no luck!

I am able to do it within my domain from any place, but it fails from outside. I have two-ways trust established between domains. Users are able to see and use resources both ways.

When I create ODBC it doesn't matter if I use SQL or Windows NT authenctication, I am getting error:

Connection Failed:

SQLState: '01000'

SQLServer Error: 11004

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (getbyhostname()() )

Connectio Failed:

SQLState: '08001'

SQL Server Error: 11

I tried to set it with TCP Static Port or Dynamic. No difference.

What should I look into?

Any ideas? Any help?

Thanks.

Did you try using the ip address ? Maybe the name cannot be resolved ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Yes I tried. Does SQl 2005 Express have any limitations as far as Connections from other domains?

Any other ideas.

|||

No, it don′t has such things. Is the server pingable ? SQL Server uses a dynamic port not he standard port. The SQL Server browser service will redirect incoming request to the appripiate dynamic port. Therefore the service has to be started on the server system. Did you check that ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

I am able to ping server, able to access files on server using UNC.

SQL Server browser is running on my server. Everything is in place, yet I can't logon.

I tried setting up ODBC Data Source with both Windows NT and SQL account authentication with no luck.

SQL actually is letting me create login using user name from other domain. I can do Find and discover users from other domain.

When it gets to making connection with server from their side it just dont see it.

Is that possible that because server is installed as a named instance I am having that problem?

|||

There has to be a firewall in between which block the traffic (bit not ICMP). Make sure you configured the firewall to let the appropiate ports open for connecting.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||Apparently I had to change port in All IP to 1433. Leaving it default dynamic was the problem. I changed all settings to listen to 1433 and here we go. Thank you for your help.

connect via QA with windows auth without joining domain

Hi, I'm using my laptop to connect to a client's internal network. I'd
like to connect to their SqlServer database using Query Analyzer,
Enterprise Manager, osql, etc... They only have Windows Authentication
enabled (they won't change this setting).
When I try to connect in QA I get the authentication failed for user
(null) error.
They've given me a domain login to use when connecting to their
database, but I'm not sure how to use it without logging on to windows
as that user.
I'd prefer not to make my laptop part of their domain. I'd rather use
my regular (local machine) login so I can access my installed programs
and files.
Any thoughts on how I should connect?
Thanks!
Try mapping a drive to a share on a machine in that domain
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<dinosaur8000@.yahoo.com> wrote in message
news:1133316094.691249.88290@.z14g2000cwz.googlegro ups.com...
> Hi, I'm using my laptop to connect to a client's internal network. I'd
> like to connect to their SqlServer database using Query Analyzer,
> Enterprise Manager, osql, etc... They only have Windows Authentication
> enabled (they won't change this setting).
> When I try to connect in QA I get the authentication failed for user
> (null) error.
> They've given me a domain login to use when connecting to their
> database, but I'm not sure how to use it without logging on to windows
> as that user.
> I'd prefer not to make my laptop part of their domain. I'd rather use
> my regular (local machine) login so I can access my installed programs
> and files.
> Any thoughts on how I should connect?
> Thanks!
>
|||I've done that. I mapped a drive to the machine hosting the SqlServer,
actually. I supply the domain login and I'm able to connect to the
share just fine. However, when I try to connect to the DB through QA or
Enterprise Manager, it doesn't work. Am I missing a step?
Tibor Karaszi wrote:[vbcol=seagreen]
> Try mapping a drive to a share on a machine in that domain
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> <dinosaur8000@.yahoo.com> wrote in message
> news:1133316094.691249.88290@.z14g2000cwz.googlegro ups.com...

connect using a non-interactive user

Hi,
I've been searching the web for some time, without any luck ...
Is it possible to connect to a SQL Server using a domain account that is
marked as a non-interactive user ?
Thanks,
Marc
"Marc Nemegeer" <nemegeermATdelaware.be.NOSPAM> wrote in message
news:eOPNDNg$EHA.4028@.TK2MSFTNGP15.phx.gbl...
> I've been searching the web for some time, without any luck ...
> Is it possible to connect to a SQL Server using a domain account that is
> marked as a non-interactive user ?
Where are you setting that option, on the server local security option, or
through group policy? Seems like it should be easy to test...
Steve

connect using a non-interactive user

Hi,
I've been searching the web for some time, without any luck ...
Is it possible to connect to a SQL Server using a domain account that is
marked as a non-interactive user '
Thanks,
Marc"Marc Nemegeer" <nemegeermATdelaware.be.NOSPAM> wrote in message
news:eOPNDNg$EHA.4028@.TK2MSFTNGP15.phx.gbl...
> I've been searching the web for some time, without any luck ...
> Is it possible to connect to a SQL Server using a domain account that is
> marked as a non-interactive user '
Where are you setting that option, on the server local security option, or
through group policy? Seems like it should be easy to test...
Steve

Connect to SQL Server from machine not in domain

I am attempting to connect to a SQL Server that is in a domain that I
have a VPN connection to. I am receiving the Error: "Login failed for
user '(null)'. Reason: Not associated with a trusted SQL Server
connection. (Microsoft SQL Server, Error: 18452)
I errantly had expected that by mapping a drive to one of the shares
on the SQL Server that I am attempting to connect to, that I would be
able to connect ok using Integrated Windows Authentication. I have
even renamed my local UID/pwd to match that on the domain that owns
the SQL Server I am attempting to connect to.
Thoughts?Hi
If you have granted login to that user or a domain group on the domain where
the sql server is (where the user is a member) , then you should be able to
log in even though the user is in a different domain. If you can't grant the
login and if you can't change the way the domains trust each other, then you
will need to ue SQL Authentication.
John
"brandor" wrote:
> I am attempting to connect to a SQL Server that is in a domain that I
> have a VPN connection to. I am receiving the Error: "Login failed for
> user '(null)'. Reason: Not associated with a trusted SQL Server
> connection. (Microsoft SQL Server, Error: 18452)
> I errantly had expected that by mapping a drive to one of the shares
> on the SQL Server that I am attempting to connect to, that I would be
> able to connect ok using Integrated Windows Authentication. I have
> even renamed my local UID/pwd to match that on the domain that owns
> the SQL Server I am attempting to connect to.
> Thoughts?
>

Connect to SQL Server from Application on different domain

I have written a VB .Net 2005 application that connects to SQL Server 2005. When both the application and the SQL Server are on the same domain we can connect fine using the connection string: "Data Source = Server1\sqlexpress;Initial Catalog=DB1;Integrated Security=True"

My question/problem is my client has machines at remote locations that they want to run the application on and connect to the database, what do I need to do?

Thanks
Simmy

Hi,

then you either have to impersonate the user in the remote domain context in your application first or use SQL Server authentication to connect to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Hi Simmy,

If your intention is to use integrated authentication, then you need to either (1) create a trust relationship between your client machine's domain of the server machine's domain (assuming that your client machine is part of a domain) or (2) you can create the same local user account with identical passwords on both machines. I don't really recommend (2) since it means that you'll be relying upon NTLM authentication whereas with (1), Kerberos authentication is available (see http://blogs.msdn.com/sql_protocols/archive/2005/10/12/479871.aspx for more information).

Thanks,
Il-Sung.

|||thanks for the help!