disable netbios over tcpip

I have a win 2003 member server with sql server 2000 on a windows nt 4.0
domain.
If I disable the netbios oveer tcpip on win 2003 server i cannot connect
anymore to the sql server.
Maybe because i'm working on a win nt 4.0 domain ?Use the server network utility on your SQL Server box and enable TCP/IP.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
news:512D63C4-1B78-45E3-9A92-744F904F11E9@.microsoft.com...
I have a win 2003 member server with sql server 2000 on a windows nt 4.0
domain.
If I disable the netbios oveer tcpip on win 2003 server i cannot connect
anymore to the sql server.
Maybe because i'm working on a win nt 4.0 domain ?|||The tcpip is already enabled on the sql server. I mean both tcpip and named
pipes is enabled.
"Tom Moreau" wrote:

> Use the server network utility on your SQL Server box and enable TCP/IP.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
> news:512D63C4-1B78-45E3-9A92-744F904F11E9@.microsoft.com...
> I have a win 2003 member server with sql server 2000 on a windows nt 4.0
> domain.
> If I disable the netbios oveer tcpip on win 2003 server i cannot connect
> anymore to the sql server.
> Maybe because i'm working on a win nt 4.0 domain ?
>|||There may be a Windows firewall issue. Check that port 1433 has been
enabled.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
news:AA55F7BB-2F4D-4207-8953-C104C81F292C@.microsoft.com...
The tcpip is already enabled on the sql server. I mean both tcpip and named
pipes is enabled.
"Tom Moreau" wrote:

> Use the server network utility on your SQL Server box and enable TCP/IP.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
> news:512D63C4-1B78-45E3-9A92-744F904F11E9@.microsoft.com...
> I have a win 2003 member server with sql server 2000 on a windows nt 4.0
> domain.
> If I disable the netbios oveer tcpip on win 2003 server i cannot connect
> anymore to the sql server.
> Maybe because i'm working on a win nt 4.0 domain ?
>|||Yes, it is true, I have win 2003 sp1 with firewall activated. But I do an
exceptions on port 1433. here the configuration:
Name MS SQL Server - Tcp 1433
Port number 1433
with scope my network (subnet) only
"Tom Moreau" wrote:

> There may be a Windows firewall issue. Check that port 1433 has been
> enabled.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
> news:AA55F7BB-2F4D-4207-8953-C104C81F292C@.microsoft.com...
> The tcpip is already enabled on the sql server. I mean both tcpip and name
d
> pipes is enabled.
> "Tom Moreau" wrote:
>
>|||If you go to the server and attempt to connect via QA or osql, are you
successful?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
news:07C15A4D-EABD-42CD-8DB0-3D4C54263503@.microsoft.com...
Yes, it is true, I have win 2003 sp1 with firewall activated. But I do an
exceptions on port 1433. here the configuration:
Name MS SQL Server - Tcp 1433
Port number 1433
with scope my network (subnet) only
"Tom Moreau" wrote:

> There may be a Windows firewall issue. Check that port 1433 has been
> enabled.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
> news:AA55F7BB-2F4D-4207-8953-C104C81F292C@.microsoft.com...
> The tcpip is already enabled on the sql server. I mean both tcpip and
> named
> pipes is enabled.
> "Tom Moreau" wrote:
>
>|||Hello Yes it's work.
I send you the error from a client:
run-time error -2147217843 (80040e4d)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. reason: Not associated with a trusted SQL server connection.
it seems not a connection to the SQL but a problem with the trusting
connection.
For internal policy the application always use a trusted windows connection.
May it cannot comunicate with the Win NT 4.0 PDC.
"Tom Moreau" wrote:

> If you go to the server and attempt to connect via QA or osql, are you
> successful?
>
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
> news:07C15A4D-EABD-42CD-8DB0-3D4C54263503@.microsoft.com...
> Yes, it is true, I have win 2003 sp1 with firewall activated. But I do an
> exceptions on port 1433. here the configuration:
> Name MS SQL Server - Tcp 1433
> Port number 1433
> with scope my network (subnet) only
> "Tom Moreau" wrote:
>
>|||Check out the following:
http://support.microsoft.com/defaul...;en-us;827422#8
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
news:4B27E8D8-4F3A-4EB8-97F9-6781FFD5F937@.microsoft.com...
Hello Yes it's work.
I send you the error from a client:
run-time error -2147217843 (80040e4d)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. reason: Not associated with a trusted SQL server connection.
it seems not a connection to the SQL but a problem with the trusting
connection.
For internal policy the application always use a trusted windows connection.
May it cannot comunicate with the Win NT 4.0 PDC.
"Tom Moreau" wrote:

> If you go to the server and attempt to connect via QA or osql, are you
> successful?
>
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
> news:07C15A4D-EABD-42CD-8DB0-3D4C54263503@.microsoft.com...
> Yes, it is true, I have win 2003 sp1 with firewall activated. But I do an
> exceptions on port 1433. here the configuration:
> Name MS SQL Server - Tcp 1433
> Port number 1433
> with scope my network (subnet) only
> "Tom Moreau" wrote:
>
>|||Yes, I read it, but I continue to don't understand why ?
The win 2003 member server to validate the windows authentication logon to
the win NT 4.0 PDC need the NETBIOS ?
The Event viewer on the win 2003 server say that there is no logon server
available, only if I disable the NETBIOS over TCPIP.
"MarcoC" wrote:

> I have a win 2003 member server with sql server 2000 on a windows nt 4.0
> domain.
> If I disable the netbios oveer tcpip on win 2003 server i cannot connect
> anymore to the sql server.
> Maybe because i'm working on a win nt 4.0 domain ?|||Yes, I read it, but I continue to don't understand why ?
The win 2003 member server to validate the windows authentication logon to
the win NT 4.0 PDC need the NETBIOS ?
The Event viewer on the win 2003 server say that there is no logon server
available, only if I disable the NETBIOS over TCPIP.
"Tom Moreau" wrote:

> Check out the following:
> http://support.microsoft.com/defaul...;en-us;827422#8
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "MarcoC" <MarcoC@.discussions.microsoft.com> wrote in message
> news:4B27E8D8-4F3A-4EB8-97F9-6781FFD5F937@.microsoft.com...
> Hello Yes it's work.
> I send you the error from a client:
> run-time error -2147217843 (80040e4d)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> '(null)'. reason: Not associated with a trusted SQL server connection.
> it seems not a connection to the SQL but a problem with the trusting
> connection.
> For internal policy the application always use a trusted windows connectio
n.
> May it cannot comunicate with the Win NT 4.0 PDC.
> "Tom Moreau" wrote:
>
>