I guess you mean Management Studio not Enterprise Manager (you can't use EM
to manage a SQL2005 instance) ? For a simple connectivity check use osql to
test and post back any error e.g. from a command prompt on your client run
osql -E -S <your instance name here>

Signature
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
> hey all,
>
[quoted text clipped - 5 lines]
> thanks,
> rodchar
rodchar - 28 Oct 2005 20:32 GMT
i promise you i connected once before about couple months back.
> I guess you mean Management Studio not Enterprise Manager (you can't use EM
> to manage a SQL2005 instance) ? For a simple connectivity check use osql to
[quoted text clipped - 11 lines]
> > thanks,
> > rodchar
rodchar - 28 Oct 2005 20:45 GMT
On the command line, on the remote machine i got the same error message:
H:\>osql -E -S MYPC\SQLEXPRESS
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
H:\>
> I guess you mean Management Studio not Enterprise Manager (you can't use EM
> to manage a SQL2005 instance) ? For a simple connectivity check use osql to
[quoted text clipped - 11 lines]
> > thanks,
> > rodchar
rodchar - 28 Oct 2005 20:50 GMT
does sa have a password i can try as a default?
> I guess you mean Management Studio not Enterprise Manager (you can't use EM
> to manage a SQL2005 instance) ? For a simple connectivity check use osql to
[quoted text clipped - 11 lines]
> > thanks,
> > rodchar
Linchi Shea - 29 Oct 2005 03:23 GMT
Knowing the sa password is not going to help here because you need to get to
SQL Server first. Could you try to connect to the IP address followed by a
comma and then the port number? Just to check whether you have a network
name resolution issue.
Linchi
> does sa have a password i can try as a default?
>
[quoted text clipped - 17 lines]
>> > thanks,
>> > rodchar
rodchar - 30 Oct 2005 00:58 GMT
i guess i just misconfigured the sql server, i was able to connect using
osql. However, was it just a fluke that i was able to register the sql server
with enterprise manager a couple months back? is this why it's called beta?
Because now i get a message with enterprise manager saying to connect to the
server i need smo or management studio?
thanks,
rodchar
> Knowing the sa password is not going to help here because you need to get to
> SQL Server first. Could you try to connect to the IP address followed by a
[quoted text clipped - 24 lines]
> >> > thanks,
> >> > rodchar
Jasper Smith - 30 Oct 2005 03:09 GMT
Yes, it must have been a pretty old build that let you do that. You should
be able to use Query Analyzer to connect (and obviously the SQL2005 tools
also)

Signature
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
>i guess i just misconfigured the sql server, i was able to connect using
> osql. However, was it just a fluke that i was able to register the sql
[quoted text clipped - 43 lines]
>> >> > thanks,
>> >> > rodchar
rodchar - 30 Oct 2005 19:26 GMT
thanks for the confirmation, i thought i was going nuts.
rodchar
> Yes, it must have been a pretty old build that let you do that. You should
> be able to use Query Analyzer to connect (and obviously the SQL2005 tools
[quoted text clipped - 47 lines]
> >> >> > thanks,
> >> >> > rodchar