quote:

---

Originally posted by vmenon

Please find below the solution, I have implemented at my place of work.

1st Domain Name: Wambsi
SQL System in domain: WambsiSQL
SQL instance Name: WambsiSQL\SQL01

2nd Domain Name: Zommer
My Login ID in Domain: Zommer\vmenon

No trust exists between both domains, but I still want to access SQL instance on Wambsi domain using windows authentication.

1. On the SQL system in domain wambsi i.e. in WambsiSQL, create a user vmenon.
2. Assign pwd to the newly created user vmenon. Remember the pwd that you assign should be the same pwd that has been assinged for the login account Zommer\vmenon.
3. Now using SQL management studio, in SQL instance WambsiSQL\SQL01 add new windows login i.e WambsiSQL\vmenon.
4. Assign the required rights as per your business policy requirements to the newly added login i.e. WambisiSQL\vmenon.


Now when I attempt to connect to the SQL instance WambsiSQL\SQL01 via SQL management studio from domain Zommer, I am able to connect to the SQL instance and based on the permissions assigned to login WambisiSQL\vmenon I am able to carry out my work.

At your end, apart from the above you might also need to ensure that all incoming request from source domain to target domain on the SQL instance port is allowed and not blocked by firewall.

In my organization, for every new SQL instance configured on another domain, I need to request the domain administrator to explicitly configure firewall on target domain to allow traffic on the SQL instance port from my system on domain Zommer.

---