Ok, this may be the wrong area to post this question. I'm working from an NT4 domain trying to access a 2003 domain they're trusted. The Pre-Windows 2000 Compatible mode is set. Yet when someone tries to SQL enterprise Manager to register the server it gives out a Null error. Anyone have any clues on this problem?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Ok, this may be the wrong area to p
- Thread starter tschouten
- Start date
Let's see if I have this clear....
You are using a NT4 machine with SQL Server client tool Enterprise Manager. You are trying to register a SQL Server server that is in a Win2003 domain.
Do you have access to the database (do you have a login for the database)?
If you don't have a login in SQL Server, you aren't going to be able to register it in Enterprise Manager.
-SQLBill
You are using a NT4 machine with SQL Server client tool Enterprise Manager. You are trying to register a SQL Server server that is in a Win2003 domain.
Do you have access to the database (do you have a login for the database)?
If you don't have a login in SQL Server, you aren't going to be able to register it in Enterprise Manager.
-SQLBill
- Thread starter
- #3
Let me try to describe this better. I have the SQL Server running in a Win2003 domain of its own. The NT4 domain is where the standard users are, I am trying to connect using the NT4 domain into the SQL server domain. There is an account on the SQL server for this. However it isn't working. The domains are trusted, the global accounts are there, users are in them. But, no sir it doesn't like it, gives me a null error.
I tried creating a local account to be authenticated through sql itself. That didn't work either.
sigh I hate working on something I didn't setup in the first place.
I tried creating a local account to be authenticated through sql itself. That didn't work either.
sigh I hate working on something I didn't setup in the first place.
Try these:
From an NT4 machine, see if you can PING the SQL Server
(Start>Run type cmd and enter, then type PING yourservername). If that doesn't work try the server IP Address instead of the name.
If the address works but the name doesn't, there's a DNS name resolution problem. You'll be able to register the server by using the IP address instead of the name.
If both fail, there's probably an access/permission problem.
Lastly, you have trusted domains, but what is SQL Server set up to use for authentication? Can you access Enterprise Manager on the SQL Server itself? If so, right click on the server, select Properties, select the Security tab and see what the authentication type is. Then make sure the logins match that.
-SQLBill
From an NT4 machine, see if you can PING the SQL Server
(Start>Run type cmd and enter, then type PING yourservername). If that doesn't work try the server IP Address instead of the name.
If the address works but the name doesn't, there's a DNS name resolution problem. You'll be able to register the server by using the IP address instead of the name.
If both fail, there's probably an access/permission problem.
Lastly, you have trusted domains, but what is SQL Server set up to use for authentication? Can you access Enterprise Manager on the SQL Server itself? If so, right click on the server, select Properties, select the Security tab and see what the authentication type is. Then make sure the logins match that.
-SQLBill
- Status
Similar threads
- Locked
- Question
- Locked
- Question