We have two domains in our company, one in the US (DomainB) and one outside of the US (DomainA). DomainB is a small office and only runs Windows 2003 SBS. DomainA has Windows 2003 Standard.
There is an always on firewall hardware to firewall hardware VPN connection between the two networks, and the DNS is setup in a way that we can see the machines on either side and ping them successfully from either side.
There are no trusts setup because as I understand it, SBS does not allow trusts and forces the single domain.
We have an application in DomainA which runs against a SQL Server database. Our users in our domain can use it just fine and it works great.
But our users in DomainB cannot connect to the SQL Server (they can ping it and name resolve it just fine, but the application won't allow the first stage authentication to it).
As far as I understand it, the application talks to the server and sets up a process by which to authenticate through SQL authentication. This brings up a login screen and then whatever is submitted in there is checked against the SQL logins in the system.
But DomainB gets an error message when trying to even bring up the login screen, which leads me to believe that it is an issue of our server denying the connection due to it being an outside domain.
So my question is, how can I force our SQL Server to allow all connections from that domain? If it is a trust relationship, can it be done with the SBS system?
There is an always on firewall hardware to firewall hardware VPN connection between the two networks, and the DNS is setup in a way that we can see the machines on either side and ping them successfully from either side.
There are no trusts setup because as I understand it, SBS does not allow trusts and forces the single domain.
We have an application in DomainA which runs against a SQL Server database. Our users in our domain can use it just fine and it works great.
But our users in DomainB cannot connect to the SQL Server (they can ping it and name resolve it just fine, but the application won't allow the first stage authentication to it).
As far as I understand it, the application talks to the server and sets up a process by which to authenticate through SQL authentication. This brings up a login screen and then whatever is submitted in there is checked against the SQL logins in the system.
But DomainB gets an error message when trying to even bring up the login screen, which leads me to believe that it is an issue of our server denying the connection due to it being an outside domain.
So my question is, how can I force our SQL Server to allow all connections from that domain? If it is a trust relationship, can it be done with the SBS system?