Enterprise Manager Server Registration General Network Error

I'm having problems Registering servers in Enterrpise Manager.
This problem is workstation specific.
Workstation is XP Pro SP1, in an Active Directory domain. Only protocol in
machine is TCP/IP.
I have 4 machines with identical hardware ghosted from one source image and
all have the problem. Hardware isn't the problem. I have at least one
other Win XP Pro computer built from a different build that has the problem.
User logs on using Active Driectory account. Opens Enterprise Manager,
register SQL server, types server name, uses NT Authentication. Error
returned is "General Network Error, check you network documentation"
Registration using SQL Authentication works fine (using SQL Authentication
is NOT an option for security reasons)
Same user can perform the same task using the same Active Directory
credentials using a different machine, so the account is not the problem.
This machine has different hardware, runs Windows 2000 Pro.
I can use this Windows 2000 machine on the same network port that the other
machine is on and don't have a problem. The network from the NIC to the
server isn't the problem.
I tried updating MDAC from 2.7 to 2.8 with no change.
SQL Server in question is newly build SQL 2000 SP3a with NO load on it
(application vendor hasn't installed software yet).
Query Analyzer has the same problem.
I tried using ODBCPING.EXE and received this response:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
A similar error came up from Query Analyzer.
I did find 2 different SQL servers that will allow registrations, but these
users don't need access to those servers.
What do I need to look at on this client to correct this problem?
Scott Begin
kb below has some good troubleshooting steps
http://support.microsoft.com/default...b;en-us;827422
Andy.
"Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
> I'm having problems Registering servers in Enterrpise Manager.
> This problem is workstation specific.
> Workstation is XP Pro SP1, in an Active Directory domain. Only protocol
> in
> machine is TCP/IP.
> I have 4 machines with identical hardware ghosted from one source image
> and
> all have the problem. Hardware isn't the problem. I have at least one
> other Win XP Pro computer built from a different build that has the
> problem.
> User logs on using Active Driectory account. Opens Enterprise Manager,
> register SQL server, types server name, uses NT Authentication. Error
> returned is "General Network Error, check you network documentation"
> Registration using SQL Authentication works fine (using SQL Authentication
> is NOT an option for security reasons)
> Same user can perform the same task using the same Active Directory
> credentials using a different machine, so the account is not the problem.
> This machine has different hardware, runs Windows 2000 Pro.
> I can use this Windows 2000 machine on the same network port that the
> other
> machine is on and don't have a problem. The network from the NIC to the
> server isn't the problem.
> I tried updating MDAC from 2.7 to 2.8 with no change.
> SQL Server in question is newly build SQL 2000 SP3a with NO load on it
> (application vendor hasn't installed software yet).
> Query Analyzer has the same problem.
> I tried using ODBCPING.EXE and received this response:
>
> COULD NOT CONNECT TO SQL SERVER
> SQLState: 08S01 Native Error: 11
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General
> network
> error. Check your network documentation.
> SQLState: 01000 Native Error: 10054
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (recv()).
> A similar error came up from Query Analyzer.
> I did find 2 different SQL servers that will allow registrations, but
> these
> users don't need access to those servers.
> What do I need to look at on this client to correct this problem?
> Scott Begin
>
>
>
|||I looked at the article
I've tried the suggestions listed, but with no luck
1) Check DNS.
I can ping the server by name from the affected client. (rules out name
resolution)
I can register the server by name using SQL Authentication (rules out name
resolution)
I can register the server by IP address (rules out name resolution)
2) Verify the enabled protocols and aliases
Working Windows 2000 machine has Named Pipes and TCP/IP configured. Not
working XP machine matches. No aliases defined on either machine.
Everything else in Client Network Utility is the same on both machines.
3) Verify that the instance of SQL Server is listening Correctly
Have working Windows 2000 machine that can connect to this instance of SQL
Server using NT Authentication. XP Machine can connect to this instance of
SQL Server using SQL Authentication but NOT NT Authentication. As Suggested
by the article, the SQL Server log shows it is listening on port 1433
correctly.
Instance is running correctly.
4) Troubleshoot MDAC Issues
Windows 2000 Pro machine that works is running MDAC 2.7 SP1 Refresh
Windows XP Machine that doesn't work is running MDAC 2.8 RTM
ODBC Ping on 2000 machine that works shows the connection is being opened
properly.
ODBC Ping on XP machine that doesn't shows the following errors:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
Seems to be an ODBC Issue
5) Troubleshoot firewall Issues:
Not applicable. There isn't a firewall between the client and server.
6) Troubleshoot Authentication and Security Issues
I use Active Directory Account on Windows 2000 machine. NT Authentication
works. I use same Active Directory account on Windows XP machine, doesn't
work.
Problem isn't authentication / security
7) Troubleshoot Stress on TCP/IP sockets
One of the servers being connected is a new server, without an application
running on it I don't think the stress on the TCP/IP sockets is the issue
8) See if teh instance of SQL Server is started in single user mode
I can connect to the server from other workstations simultaneously, so this
isn't the problem
9) Verify Named Pipes connectivity to SQL Server
Not trying to use Named Pipes to connect.
10) Troubleshoot conenctions that time otu during the recovery process.
These servers have been running anywhere from 1 day to 4 months. Recovery
process isn't going on. If this were a problem, I couldn't connect from the
Windows 2000 machine.
11) Test different ways to connect to the instance of SQL Server
Use SQL Authentication: Works from affected machine
From other data sources: Enterprise manager Fails NT Authentication, works
SQL; ODBC fails NT authentication, works SQL; Query Analyzer fails NT
Authentication, works SQL;
Using other protocols: Not an option. Must use TCP/IP
Different Login Account: why? The login account works on another computer
Put entry in hosts file: Why, resolution not problem
Connect from SQL Server: Works
Connect using IP address: Fails NT Authenticatiion/ works SQL Authentication
Specify port: Why? This doesn't seem to be the problem
12) Capture Network Traces:
Haven't tried this
The recurring theme you should see in what I have done is NT Authentication
doesn't work from this client. SQL Authentication does work from this
client. There is some setting / Driver or something that prevents it from
working.
Any other Ideas?
Scott Begin
scott@.thebegins.com
"Andy Ball" wrote:

> kb below has some good troubleshooting steps
> http://support.microsoft.com/default...b;en-us;827422
> Andy.
> "Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
> news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
>
>