ODBC SQL 2005 and Named Instance - won't connect

We have two instances of SQL 2005 installed, with static TCP/IP ports, one
instance on one IP address, port 1433 and the other instance on a different
IP address, port 1433.
Try to create an ODBC System DSN using SQL Native Client and it won't
connect.
If we do the same thing but using a default instance of SQL 2005, ODBC
connects fine.
Any help anyone can give as to why ODBC won't connect to the SQL 2005 names
instances?
I've tried searching thru MSDN and technet and such but found nothing of any
help.
Michael MacGregor
Database ArchitectNever mind, got it to work, having taken a sledgehammer to the server.
Disabled all IP addresses other than the one specified for the instance,
then restarted the whole box, and hey presto it finally worked.
Now we just have to get LDAP to recognise the named instances. Yeah I know,
old technology and all that stuff.
MTM
"Michael MacGregor" <nospam@.nospam.com> wrote in message
news:emWQtlFGGHA.3728@.tk2msftngp13.phx.gbl...
> We have two instances of SQL 2005 installed, with static TCP/IP ports, one
> instance on one IP address, port 1433 and the other instance on a
> different IP address, port 1433.
> Try to create an ODBC System DSN using SQL Native Client and it won't
> connect.
> If we do the same thing but using a default instance of SQL 2005, ODBC
> connects fine.
> Any help anyone can give as to why ODBC won't connect to the SQL 2005
> names instances?
> I've tried searching thru MSDN and technet and such but found nothing of
> any help.
> Michael MacGregor
> Database Architect
>