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

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: Cryptogram Comment
    ... >> bother me with Windows questions. ... >> machines are broken. ... Just like if you don't know to tune up your car every year then you ... > and Linux and other open OS's make all patches FREE to redistribute. ...
    (sci.crypt)
  • What Does It Take to Get a PC With XP?
    ... I won't waste time rehashing the argument over whether Windows Vista ... that virtually every copy of Vista Business or Vista Ultimate Edition ... machines doesn't mean that its employees understand that policy. ...
    (misc.consumers)
  • [Full-Disclosure] RE: M$ - so what should they do?
    ... >isn't a basic windows design piece. ... or getting their machines loaded with adware and spyware ... heart of the problem of machines connected to the Internet, ...
    (Full-Disclosure)
  • Re: Need tutorials, guides... However...
    ... performance loss you'll get from an OS like Windows or Linux. ... machines out there have gone off in many different directions. ... expect to find certain hardware at certain addressess. ...
    (alt.lang.asm)
  • Re: Saw 10.4.1 Running On a PC Laptop Today
    ... People would no longer differentiate between Macs and PCs and most would just stick with the Windows OS that came with their box. ... Apple would no longer be innovative as it now and eventually be marginalized out of business. ... The fact is, Windows users use Windows NOT because "it works, and that's all that counts", but because it is the ONLY real game in town for Intel machines, and because Apples are JUST TOO EXPENSIVE for the common man and corporations to embrace that paradigm. ... most Windows users would rather switch to OSX than continue to put up with Microsoft's machinations in the computer world. ...
    (comp.sys.mac.advocacy)