Error : SQL server does not exist or access denied.

Error : SQL server does not exist or access denied.
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
MichaelHi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:
> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag