Problems connecting to SQL server on W2K3 from Win 2000 workstatio
- From: "Mike Allen" <MikeAllen@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 1 Jun 2005 09:06:04 -0700
We are running SQL Server 2000 on Windows Server 2003 (SP1 not installed).
We are trying to access our databases using Enterprise manager from our
machines in the office using windows authentication. We have no problems
from windows XP machines (using both TCP/IP and Named Pipes). I can connect
to the server using the SA account (TCP/IP) and Named Pipes from a windows
2000 workstation, but cannot access the SQL server from windows 2000 machines
using TCP/IP.
When we try to log in using windows 2000 we get "login failed for user
null". From xp machines it goes straight in.
Testing that I have done:
• Set up an alias to the Windows 2003 server name (SQL Server Client Network
Utility). No luck
• I can map a folder to the machine using net use command
• I am in the same AD domain.
• The clients are connecting to the server using integrated security (not
allowing SQL authentication)
I cannot understand what’s going on; do you have any pointers on where to
start looking?
Thanks
.
- Follow-Ups:
- Re: Problems connecting to SQL server on W2K3 from Win 2000 workstatio
- From: Mike Bulava
- Re: Problems connecting to SQL server on W2K3 from Win 2000 workstatio
- From: Gintaras Gostautas via SQLMonster.com
- Re: Problems connecting to SQL server on W2K3 from Win 2000 workstatio
- Prev by Date: pbm while connecting to the remote SQL server
- Next by Date: Re: snap-in failed to initialize
- Previous by thread: pbm while connecting to the remote SQL server
- Next by thread: Re: Problems connecting to SQL server on W2K3 from Win 2000 workstatio
- Index(es):
Relevant Pages
|