RE: Accessing SQL Server Accross Domain
From: JT (JTnospam_at_verizon.net)
Date: 12/19/03
- Next message: Glen Moffitt: "tracking source of login failures"
- Previous message: ken: "change standard security password of sa"
- In reply to: Baisong Wei[MSFT]: "RE: Accessing SQL Server Accross Domain"
- Next in thread: Baisong Wei[MSFT]: "RE: Accessing SQL Server Accross Domain"
- Reply: Baisong Wei[MSFT]: "RE: Accessing SQL Server Accross Domain"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 19 Dec 2003 05:58:43 -0800
Thanks Baisong,
What type of Authentication does the distant user need to
use? Is it possible for them to use Windows Auth, or do
the need to use SQL Server Auth? Thanks.
JT
>-----Original Message-----
>Hi JT,
>
>Thank you for using MSDN Newsgroup! It's my pleasure to
assist you with
>your issue.
>
>As my understanding of your question, you want to know if
you client
>application in their domain could access the SQL Server
in another domain,
>right. If I misunderstood, please feel free to let me
know.
>
>To access the SQL Server across domain is possible.
>
>At first, make sure the connection between this two
computers is OK.
>
>Please refer to this article:
>http://support.microsoft.com/?id=238949
>
>You can test the application environment by the
following steps to test
>the connectivity:
>
>To test general connectivity:
> PING < SQL_Server ip>
>
>To test we can connect to default SQL Server port 1433:
> TELNET < SQL_Server ip> 1433
>
>If we can connect, the screen will go blank. The server
is awaiting more
>commands. Hit any key to return.
>If we CANNOT connect, you will get an error:
>"Connecting To < ip > ..Could not open connection to the
host, on port 1433
> No connection could be made because the target machine
actively refused
>it."
>
>NOTE:
>Port 1433 is the default port number for SQL Server. You
can check the
>actual port number by Server Network Utility. You can get
the actual port
>number in use by check the properties of TCP/IP (which
should be in the
>"Enabled Protocols").
>
>Then, use your Query Analyzer to check if it can access
the database from
>one domain to another.
>
>For information you could refer to or ADO.NET
programming, you can refer
>to the following materials or ask questions in related
newsgroup:
>http://support.microsoft.com/?id=216415
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/dnauth/html
>/dnauth_security.asp
>http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com:
>80/support/kb/articles/Q193/1/35.ASP&NoWebContent=1
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;q176379
>
>Hope this answered your questions. If you still have
questions, please feel
>free to post new message here and I am ready to help.
>
>
>Best regards
>
>Baisong Wei
>Microsoft Online Support
>----------------------------------------------------
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and
confers no rights.
>Please reply to newsgroups only. Thanks.
>
>
>
>
>.
>
- Next message: Glen Moffitt: "tracking source of login failures"
- Previous message: ken: "change standard security password of sa"
- In reply to: Baisong Wei[MSFT]: "RE: Accessing SQL Server Accross Domain"
- Next in thread: Baisong Wei[MSFT]: "RE: Accessing SQL Server Accross Domain"
- Reply: Baisong Wei[MSFT]: "RE: Accessing SQL Server Accross Domain"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
