Viual Studio 2003; ASP.Net; .Net Framework 1.1, SQL Server 2000
Hi,
We have two domains in our network - prod.domain.com and dev.domain.com. There is no trust relationship between the two domains. I am trying to connect to an SQL Server in dev.domain.com using SQL Server Authentication from prod.domain.com. My connection string uses the fully qualified domain name (xxxxxx.dev.domain.com) to connect. The error I receive is SQL Server does not exist or access denied. I can access the database through SQL Query Analyser and SQL Enterprise Manager across the domains with no problems. I can also connect through a .udl file using the same SQL Server Authentication information.
If I run my application from dev.domain.com accessing a database that sits in prod.domain.com then the connection is fine.
Can someone point me in the direction of any areas I can troubleshoot to see what is preventing the connection please? The only things I can see on the web are details of windows authentication across domains which isn't relevant to me in this instance. I've been pulling what little hair I have out over this for the last week.
Thanks in advance.
Is it possible to configure transnational replication between two different domains also non trusted domains.
It's possible means what i need to take care before configure replication and how to configure transnational replication between two different domains.
I have a network that has 10 machines-6 of them have sql server registrations. I am able to access all 6 from any machine while they are on the domain. However I also need to take 5 of them off of the domain to a remote site and set up a workgroup. I am able to log in to each sql server from the workgroup login but I am not able to run software on one machine that connects to a sql server registration on another machine in the workgroup. I get a "sql server does not exist or access denied" message. Further, when I open enterprise manager, the other sql servers don't show up and I am unable to add them using the wizard.
Hi, My problem is somewhat like this that, i want to connect my all applications (developed in asp.net) to one database. In other words i want to make a centralised database that can be accessible from the application running at the different domains. When i did so by using the same username, password, database and server...i recieve an error that, "connection cannot be establised". If any body have the solution for this problem. then please do write the "connection string" for me that can be efficiantly used on the applications running on differnt domains. Thanks and Regards, Steve Dcosta
Okay, i've got an ETL package which works flawless, we've created a scheduled job for it which also worked. This ETL accesses a flat file located on a server on a different location in the same domain.
Last week we start a migration to a new network, the location where the flat file is stored has already moved to the new domain but the SQL server agent is still on the old domain. There is a trust between the 2 domains, the network user from the old domain has been added on the server in the new domain where the flatfile is located.
If i run the etl package manually it works flawless, now if i run the etl using the SQL server agent it won't run anymore.
I get the following error:
Executed as user: OIdDomaindwh. ...n 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 21:15:00 Error: 2007-10-02 21:15:02.10 Code: 0xC001401E Source: Rolmer_Product Connection manager "Flatfile Product" Description: The file name "\fs-cha-fs01dwhproduit.csv" specified in the connection was not valid.
Don't tell me its a problem related to the user that the SQL Server Agent is set to because its set to OldDomaindwh which is the same user i use to login on the server where i can manually run it without problems. The problem only occures when i run it using the SQL server agent which uses the same user to execute packages.
This is a very difficult problem i doubt anyone here will be able to crack this nut, but if they do i'll be very impressed because it would require a real smart network admin with SQL experiance to figure this one out...
We have an Enterprise setup with multiple domains.
We a Domain A with SQL server 2008R2 say SQL-A and Domain B with SQL server 2008R2 ( SQL-B). It will be like SQL-A will always access SQL-B. Reverse is not required.
In Domain A we have a .Net Application which accesses SQL-A to perform CRUD operations which ultimately come to SQL- B since all SQL tables exist in SQL- B only.
Need to know the right way to implement Linked Server from SQL-A to SQL-B, so that Domain issues as well as DML execution work smooth.
I need not worry about DDL in SQL-A And SQL-B as it will taken care of by network and H/W team. I just need to focus on as developer.
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?
Hi all, I have a production website at Godaddy and an ASP.net 2.0 page that successfull connects to a SQL 2005 instance provided by Godaddy using SQL authentication(User ID/Password). The Godaddy database has become too small (200MB limit) and the plan is to use the SQL Server 2005 standard edition at my office. In other words, I want to host my own SQL server and keep the front-end at Godaddy. The ASP.net test page at Godaddy generates the basic connection errors when attempting to connect to my SQL server at the office. This error has several variations depending on how the connection string is configured: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) In this case the connection string is: Data Source=xxx.xxx.xx.xxx,1433; Network Library=DBMSSOCN; Initial Catalog=Test; User ID=xxx; Password=xxx" I've embedded this connection string directly into the ASP.net test page in order to make this page independent of the web.config file. My MS SQL server is on a Small Bussiness Server 2003 with Sharepoint and Remote Workplace running, and this machine is behind a linksys router, and Routing and Remote Access is running in place of windows firewall. I've openned ports TCP 1433 and UDP 1434 on the router and Routing and Remote Access. Telnet xxx.xxx.xxx.xxxx 1433 connects successfull, and the SQL log shows listening on 1433. I don't know if telnet is telling me that there is successful connection to the port on the router, or if it makes it all the way to the SQL server. The SQL server is running the default instance MSSQLSERVER. Locally, I am able to connect using SQL 2005 Studio, and I am able to confirm this activity in the SQL log. Since I've openned port 1433, I also see numerous dictionary attacks in the SQL Log. Based on this, remote connectivity is there. The strange observation is that the SQL log shows no sign of a connection attempt from the ASP.net page. The connection appears to be failing before it reaches the SQL server. I've openned ports in the Linksys router and the NAT/Firewall the same way I've openned them for Sharepoint and Remote Workplace. I also found that when I move the ASP.net test page to another ISP, then the SQL connection that worked from the Godaddy website, is no longer able to connect. An explanation of this would also be very helpful to me. Is there something that needs to be configured to expose the SQL server to ASP.net pages that is different from remote access? Does IIS need to somehow be involved? Is there something in Small Business Server 2003 that could be interferring with ASP.net page requests to the SQL server? Do I need to run my machine as a web server to make this work? Any help with this configuration would be greatly appreciated.
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 need to figure out what kind of Authentication , I need to use for following applicaiton
Product : -
1 ) It resides on a its Domain and has access to Database on that Domain. 2 ) We have a application level login , n based on application login id display specific pages.
The question that bother me is this
Q ) If i use NT authentication , then a user will be required to
a ) Login to domain (with userid and password) first and then
b ) Then i would require to again login to applicaiton with application level login and password.(different levels of login as there) Based on the application level login i will display only specific asp pages. They have different access rights..and roles.
Requirment is to login only once..and it should authenticate to application display specific pages and authenticate to SQl server database also..
Is there any way thru which i can map my application level login to SQl server.. and what authentication should i use..
I folks.I Have installed sql server 2005 express and choosed windowsauthentication on instalation, but i make a mistake and now i needmixed authentication, how can i modify this whithout uninstall andinstall again the application?thanks for the help.
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
Hey all, I need your help again..We are having many domains. Actually we have created SQLgroups in sql and granted permissions in our domain. But guys from other domains are just entering into their query analyser and accessing the sql server..They are not at all falling under our SQLgroups. We have given trusted connections between domains.. My question here is Is there anyway that there should be an option to select the domain before they log in thru query analyser? Like Nobody should enter from their domain ...only through our domain they should enter..? Please help me out..
Hi, I have two SQL servers in different domains(A and B), I cant use the Enterprise Manager to register eachother...they show me "Sever doesnt exist" but when I use ping I can show them.... Please help me.....What can I do?
(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'm attempting to set up a dts transfer SQL 7 box to SQL 7 box. These two servers are on two separate NT domains with no trust relationship, and I will be sending the info across a VPN.
Anyone out there have a similar situation? Offer any recommendations, pitfalls, ports used, ways to do this??? I'd appreciate any ANY ideas on how to make this work. Thanks in advance. -Tricia
Is there any way to connect to SQL Server from a non trusted domain. Passthrough authentication works for other NT Server resources (like exchange folder, printers, shared folders), but SQL Server 7.0 does not seem to accept this passthrough authentication (where the username and password are the same in both domains). There is no internet access required.
I need to move three sql 6.5 servers over from one domain to another domain. What is the best way to do it and what should I look out for? I am really new at this so any help would be great.
Company with one head office and one remote office. In the two offices I have two domains with two PDCs. The two networks are connected with eachother through leased line and the routers are configured properly. The SQL Server is on the PDC in head office and "local" clients connect fine. I cannot connect from the remote office. I think that I have folowing solutions:
1. make trust relationships between two domains - it will be hard a little bit because second PDC is samba on linux
2. make all clients in remote office to be members of the head office domain - potential problems if the leased line drops
3. make all clients to log in with same account as SQL Server logs locally - stupid
I have a sql-table. The domain of one of my columns a fix number of string values (like "blue", "green" and "yellow"). However, there is a big likelyhood that the domain will be expanded by more string values in the future (however, none of the existing string values will ever be discluded from the domain). How would I go about enforcing that all strings added to my column in my table is within my domain?
Should I use a check constraint, or create a domain, or sholud a create another table with the domain values and use a foreign key? What would be best practise for my problem?
I not too hot on networking. When I type "IPCONFIG /ALL" the "Prmary DNS Suffix" is empty. Does this mean I have no domain? Can I configure a mirror on this server?
I would like to replicate databases from an SQL 2000 Server to a SQL 2005 Server.
a. First can this be done?
b. Does it matter if both servers are on different domains?
Secondly
If all is possible from my above questions, in order for me to enable replication on the SQL 2000 Server, i need to rename the server from LOCAL to a realname. I get an error message saying that it can not use nicknames.
a. If I go ahead and make a New SQL Server Registration, could this have a major impact on the applications using the Database server?
b. When renaming, do I first Delete the current server registration or should I first create the new one then delete the old one?
We are testing merge replication. Between servers on one domain, it works fine. Between servers on different domains, appears to work while configuring the Publisher and Push subscribers, but then errors appear after configuration. One error is that the Merge Agent could not connect to the subscriber.
The SQL Service accounts and passwords are the same on both servers. We also configured a one-way trust (maybe it is the wrong way)Subscribers trust the Publisher, and SQL service accounts added to local admin group on subscribing systems.
Anything else I should try?...modify publisher access list?
Hello, I have a problem scheduling an Object Transfer task on a server that is in a different domain than the server it is getting the data from. I can set up the Object Transfer through the Tools/DatabaseObject Transfer... option and run it manually (works great), but if I schedule it to run, it stops after about 30 seconds and gives an error message "Process Exit Code 1. Cannot connect to source server." Any ideas would be much appreciated. Thank you Ryan
We have installed SQL servers in 3 domains. We cannot see the servers in Enterprise manager in the other domains from any other domain. Trusted security is set up. Named pipes is the set protocol as we made no changes at install time. We can see the NT servers in the Server manager. All services are running. Is there something that I missed? Any help will appreciated.
