Client attaches to wrong server

Hello All,
I am running SQL server 7 sp4 on an NT4.0 SP6a, I'll call it machin2. I =
am=20
also running SQL server 7 sp2 on an NT4.0 SP6a, I'll call it machine 1. =
Two=20
databases. I am trying to move the database on machine 1 to the server=20
machine 2. I have installed sql and installed all of the patches ( i =
think) for=20
SQL7 sp4 on machine 2. I copied over a back up of the original=20
database(just the data) running on machine 1 to machine 2 after a clean=20
install. Then ran all the patches and updates to get machine 2 to SQL7 =
sp4.=20
Now my problem is if both servers are running my clients will only =
connect=20
to machine 1 no matter what. I have tried specifying ip address in the =
Client=20
utility and still no connection to machine 2. IT connects just fine with =
no=20
errors but it is machine1 not machine2. I f I stop sql services on =
machine1=20
and try to connect to machine2 I get the eror : native SQL error 10004.=20
Cannot locate or connect to SQL server. I can connect to both machines =
with=20
the enterprise utility, but from the client I can only connect to =
machine 1. If I=20
am at the console I can connect to machine 2, but that is the only way I =
know of. I can ping machine2 by name and it resolves correctly if I use =
the=20
-a option when I ping also.
I think I have all of the patches installed to fix everything in SP4 =
but I'm=20
not certain. Any help would be great.
Thanks
Robert SmithCheck the client machines for aliases under the
MSSQLServer\Client\ConnectTo key.
Otherwise, make network traces from the client machine.
run ipconfig /flushdns
ipconfig /registerdns
then start Microsoft Network Monitor or network sniffer.
Then attempt a connection from Query Analyser.
Review the trace and verify that the tcp session is connecting to the
correct machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks! That took care of it. Fpr some reason the connect to key was=20
referencing the wrong server.
Thanks again for the help!

>--Original Message--
>Check the client machines for aliases under the=20
>MSSQLServer\Client\ConnectTo key.
>Otherwise, make network traces from the client machine.
>run ipconfig /flushdns
>ipconfig /registerdns
>then start Microsoft Network Monitor or network sniffer.
>Then attempt a connection from Query Analyser.
>Review the trace and verify that the tcp session is connecting to the=20
>correct machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no =
rights.
>
>.
>|||You're welcome!
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.