Re: Problems connecting to SQL server on W2K3 from Win 2000 workst

Are you sure you're signing the Station in to the domain and you're not just
signing in locally? Can you connect to a network share on the SQL server?
Also I know this isn't as important on 2k machines but is the primary DNS
server that is listed on the 2k station the Ip address of the w2k3 DC (which
is usally a DNS server too)? That could make a differance.

Mike Bulava, MCDBA


"Mike Allen" <MikeAllen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:997CBCF5-5D74-4A02-8C20-09E43C624B88@xxxxxxxxxxxxxxxx
> The machines are in the same domain. The user I am logged on to the
> windows
> 2000 machine is a domain admin account.
>
> "Mike Bulava" wrote:
>
>> 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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:071EE849-F61A-4729-8598-67974D2D5269@xxxxxxxxxxxxxxxx
>> > 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
>> >
>> >
>> >
>>
>>
>>


.

Relevant Pages

  • Re: Cant connect to MSDE on SBS 2003
    ... SQL or Windows authentication on the server. ... From client workstations ... I can connect with Windows authentication but not SQL authentication. ...
    (microsoft.public.sqlserver.msde)
  • Re: Problems connecting to SQL server on W2K3 from Win 2000 workstatio
    ... This is because you are using Windows authentication without a domain setup. ... because it tends not to work, use SQL Authentication and you'll always ... > from windows XP machines. ... > to the server using the SA account and Named Pipes from a windows ...
    (microsoft.public.sqlserver.connect)
  • Windows Authentication
    ... I'm trying to enable SQL Server 2000 to run on a network or Wind 2K Pro and ... Win XP machines using Windows Authentication and think I have figured out ... and for that I need the server machine to run a server version of Windows. ...
    (microsoft.public.sqlserver.connect)
  • Cannot generate SPPI Context
    ... Since the replacement we can no longer access the SQL-server via Windows Authentication (SQL turns mainly on this new server). ... This happens on ALL machines including the server. ...
    (microsoft.public.sqlserver.security)
  • RE: trusted connections
    ... What mode is the Server in? ... Windows Authentication and SQL Authentication ... What is the value of LoginMode under: ...
    (microsoft.public.sqlserver.security)