Connection with server problem

Ok guys,
First of, I don't even know if this question should be
posted here, because it's related to Networking, Database
server(namely sql 2000), and c#.
I have 3 computers, 3 of them are connected in one
network. Computer A (windows 2000 server) has SQL 2000
server. My company uses 2 other computers with windows
XP. I program in one of them (B) and I have to install
the program in C.
I wanted to use windows authentication of SQL access. The
problem with this is that if I wanted to give an access
to somebody, he has to login from the main domain in
computer A (since the SQL is in computer A). This login
process takes a lot of time (5 minutes). Not to mention,
even though I managed to do this, the opening access to
the SQL server sometimes are pretty long too.
Now, after understanding my problem could you answer some
question of mine?
1. Where did I went wrong? (If I was wrong in one of this)
A. The windows server setup (Active directory or Domain
mistakes)
B. The SQL server setup (it's not set properly?)
C. I'm stupid, I'm supposed to go with SQL authentication
(which I avoided becoz it means that I have to insert my
database password in my code)
2. say in computer A I have domain named Domain-A, I'm
logging in from computer B using an account from computer
A using Domain-A. Is there anyway to speed up the
proccess of the login? (Or is there a reason why the
process went slow?)
3. Is there anyway for the SQL to give a permission to
another account in another computer? For future references
(windows
authentication mode)-- Eric wrote: --
>> Ok guys
>> First of, I don't even know if this question should be
> posted here, because it's related to Networking, Database
> server(namely sql 2000), and c#
>> I have 3 computers, 3 of them are connected in one
> network. Computer A (windows 2000 server) has SQL 2000
> server. My company uses 2 other computers with windows
> XP. I program in one of them (B) and I have to install
> the program in C
>> I wanted to use windows authentication of SQL access. The
> problem with this is that if I wanted to give an access
> to somebody, he has to login from the main domain in
> computer A (since the SQL is in computer A). This login
> process takes a lot of time (5 minutes). Not to mention,
> even though I managed to do this, the opening access to
> the SQL server sometimes are pretty long too
--
Hi Eric
Did you install SQL Server on a domain controller? Officially, this is not a recommended setup. I've personally seen problems with other customers with this setup: from performance issues to weird SQL Server behaviour. Is it feasible to commission another lower spec'd machine to act as the domain controller so that SQL Server is a dedicated application server?
Hope this helps
- Eric Cárdena
SQL Server suppor