Problems connecting to SQL server on W2K3 from Win 2000 workstatio

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 machine
s
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 Netwo
rk
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?
ThanksSame here, except we can not to connect from win98 machines. From XP
everything looks fine. Before everything worked for about 1,5 years and
only today morning crashed. Btw, connection to (local) on server machine
works fine. Nobody did any changes in TCP/IP nor in DSN settings.|||This is because you are using Windows authentication without a domain setup.
If you aren't using a domain you shouldn't use windows authentication
because it tends not to work, use SQL Authentication and you'll always
connect. The problem is mainly that the users you are signed in to the W2k
box doesn't match a user on the W2k3 box, or the user isn't passed properly
to SQL, or if you really want to setup Windows authentication use to put the
workstations that servers into a domain..
Thanks,
Mike Bulava, MCDBA
"Mike Allen" <MikeAllen@.discussions.microsoft.com> wrote in message
news:071EE849-F61A-4729-8598-67974D2D5269@.microsoft.com...
> 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
>
>