Cannot connect to Named Instance of MSDE through Enterprise Mananger...

Hi- I am hoping someone can help me or shed some light on an issue I am having.

I have recently moved to a dedicated server with MSDE installed on it. The server was installed as the default instance and I changed the password to the SA account. I then copied my entire SA database over to the new MSDE database and everything was working good so it seemed. I believe at some point during copying of the data, or after installalling an application the SA account begain to fail and the password was changed. I have no idea how this happened, and better yet when I tried to change it logged in as the administrator with OSQL it told me I did not have sysadmin rights (I tried multiple Windows NT Auth logins and still got this error trying to change the password).

So... I reinstalled MSDE and created a named instane. I then attached the mdf/ldf files to my named instance and am able to connect ok from a .NET application directly to my new MSDE Named Instance database. Sounds like everything is great right? Not really, I can't figure out how to connect through enterprise manager and its driving me CRAZY!

1. I CAN connect via any .NET app and a connection string

2. I CAN connect via the server with OSQL

3. I CAN connect via the web based enterprise manager (which is very limited and a freeware ASP app).

4. I CANNOT connect via enterprise manager. I have verified from the (SVRNETCN.EXE utility) that the port is open and have tried connecting to MY_IPADDRESS\NAMEDINSTANCE\ but no luck.

One additional side note, when I wasn't using a named instance I had no problems connecting through enterprise manager to my default MSDE instance.

Any help would be grealy appriciated, this is driving me nuts!

-Chad

Ok, I got this figured out. For anyone else that has this issue here is what solved my problem.

Within the client utility create an alias named YourDomainOrIPAddress\NamedInstance and make sure to open up the TCP port with the SVRNETCN.EXE on the server. Also, enabled TCP/IP on the client utility and make sure its the same port.

Additionally within Enterprise Manager I kept trying YourDomainOrIPAdress\NamedInstance:Port# instead what you need to do is try YourDomainOrIPAddress,Port# (Common instead of semi colon).

-Chad