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
>
>
Showing posts with label w2k3. Show all posts
Showing posts with label w2k3. Show all posts
Friday, March 23, 2012
Wednesday, March 21, 2012
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 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
Same 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
>
>
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
Same 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
>
>
Monday, March 12, 2012
Problem: SQL Server does not accept TCP connections
Hi,
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.arIts not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
>|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server
.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.lo
g
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.arIts not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
>|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server
.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.lo
g
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...
Problem: SQL Server does not accept TCP connections
Hi,
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.ar
Its not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>
|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.log
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.ar
Its not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>
|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.log
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...
Subscribe to:
Posts (Atom)