Connecting to MSDE named instance

If we install MSDE 2000 SP3a with out a named instance we can connect to
through OSQL from a different computer on the network.
We used SVRNETCN.EXE to add TCP/IP to the protocol list.
We changed the port from 1059 or something like that to 1433.
We changed "LoginMode" to 2, but we also tried it with 0
But when we try to connect via OSQL
osql -S ROBXP\RR -U sa -P 11111
we get the following error.
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
the same OSQL command works OK from the local computer.
If we re-install with out a named instance we can connect fine with OSQL
Any ideas?
-Rob
PS. it was installed with the following:
setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
Check your MDAC version on the client you're trying to connect from. Upgrade
to the latest version and try it again.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"rob" wrote:

> If we install MSDE 2000 SP3a with out a named instance we can connect to
> through OSQL from a different computer on the network.
> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
> We changed "LoginMode" to 2, but we also tried it with 0
> But when we try to connect via OSQL
> osql -S ROBXP\RR -U sa -P 11111
> we get the following error.
>
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> the same OSQL command works OK from the local computer.
>
> If we re-install with out a named instance we can connect fine with OSQL
> Any ideas?
> -Rob
> PS. it was installed with the following:
> setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
>
>
|||I ran Componet Checker 2.0 and it indidcates I have MDAC 2.8 SP1 which looks
to be the latest version.
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:86C87062-5A4C-4962-8FB3-99BA9CA2F375@.microsoft.com...
> Check your MDAC version on the client you're trying to connect from.
> Upgrade
> to the latest version and try it again.
|||hi,
rob wrote:

> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
usually 1433 is for default instances, where other port numbers indicates
named instances...
specifying a fixed port and not using the dynamic assigned port (wiche
requires on the server the UDP 1434 port to be available out of eventual
firewall) you have to specify an alias via Client Network Utility
(cliconfg.exe) on each remote client...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||THANKS it works.
For anyone else reading this thread in the future.
You give it an alias name (RR for example) and and the servername is the
servername\instance
you can test the connection by using the alias name:
osql -S RR -U sa -Pxxxxx
thanks again.
.....
I have done some more testing. The only thing I am concerned about is:
After my program and MSDE is installed on someones computer, if they want to
access it from a different computer they will need to know how to create
exceptions in the WindowsXP firewall.
They will need to open up UPD 1434 and TCP port XXXX where XXXX is whatever
random port is used during installation of MSDE. I can find that port in
the registry and tell them at install time. But my users are not always
very proficient at using computers, and could have a hard time opening up
ports in the firewall.
If anyone has any suggestions about making this easier I would love to hear
about it.
-Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qfs6cFe280bU1@.individual.net...
> hi,
> rob wrote:
>
> usually 1433 is for default instances, where other port numbers indicates
> named instances...
> specifying a fixed port and not using the dynamic assigned port (wiche
> requires on the server the UDP 1434 port to be available out of eventual
> firewall) you have to specify an alias via Client Network Utility
> (cliconfg.exe) on each remote client...
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Rob,
rob wrote:
> ....
> I have done some more testing. The only thing I am concerned about
> is: After my program and MSDE is installed on someones computer, if
> they want to access it from a different computer they will need to
> know how to create exceptions in the WindowsXP firewall.
> They will need to open up UPD 1434 and TCP port XXXX where XXXX is
> whatever random port is used during installation of MSDE. I can find
> that port in the registry and tell them at install time. But my
> users are not always very proficient at using computers, and could
> have a hard time opening up ports in the firewall.
> If anyone has any suggestions about making this easier I would love
> to hear about it.
>
actually you can provide the script available at
http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
ports" :D
try having a look at it if can helps..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Wow, that will make it easier. I was dreading having to give instructions to
open the firewall. ; )
I don't want to bother you, but I have one more question.
Your advice did work, and I can connect to the newly installed instance, -
IF I set up an alias.
BUT,
I have one computer that I installed with an instance that I do NOT have to
set up an alias for to connect remotely. I can not see what is different
for this computer. I even printed out the MSSQL registry settings for the
two computers and could not see a difference (besides uptime, etc.)
Even though your suggestion works, it would be much easier if I did not have
to set up an alias on the clients. Do you have any ideas what I did
differently with the one that works with out an alias?
Thanks,
Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qhp0hFem400U1@.individual.net...
> hi Rob,
> actually you can provide the script available at
> http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
> ports" :D
> try having a look at it if can helps..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||I downloaded your program DBMgr2 and was able to connect to my DB without
using an alias. The difference was (from your help file) to use servername =
ROBXP\RR,1433
explicitly name the port number. This works via osql also.
The difference remains that I have one computer that I do not need to know
what the port number is, or set up an alias.
"rob" <ryost@..no.spam.rentright.com> wrote in message
news:OqGjGPbyFHA.2924@.TK2MSFTNGP15.phx.gbl...
> Wow, that will make it easier. I was dreading having to give instructions
> to open the firewall. ; )
> I don't want to bother you, but I have one more question.
> Your advice did work, and I can connect to the newly installed instance, -
> IF I set up an alias.
> BUT,
> I have one computer that I installed with an instance that I do NOT have
> to set up an alias for to connect remotely. I can not see what is
> different for this computer. I even printed out the MSSQL registry
> settings for the two computers and could not see a difference (besides
> uptime, etc.)
> Even though your suggestion works, it would be much easier if I did not
> have to set up an alias on the clients. Do you have any ideas what I did
> differently with the one that works with out an alias?
> Thanks,
> Rob
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3qhp0hFem400U1@.individual.net...
>
|||hi Rob,
rob wrote:
> I downloaded your program DBMgr2 and was able to connect to my DB
> without using an alias. The difference was (from your help file) to
> use servername = ROBXP\RR,1433
> explicitly name the port number. This works via osql also.
> The difference remains that I have one computer that I do not need to
> know what the port number is, or set up an alias.
probably it's not a named instance but a default one, that's to say ROBXP
and not ROBXP\RR..
default instances automatically listen on TCP 1433 as this port is the one
Microsoft reserved on IANA for SQL Server...
try having a look at it..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I am pretty sure it is a named instance. I connected to it through your
Dbamgr2k by specifing
MICHELLEP\MICHELLE
I did not have to give it port 1433 (which is its port)
I did set this server up several months ago, and do not remember exactly how
I did it.
Also, when I go to add remove programs it is listed as:
Microsoft SQL Server Desktop Engine (MICHELLE)
and I think the instance name is listed in the paren's
From SQLPing:
C:\>sqlping 192.168.0.88
SQL-Pinging 192.168.0.88
Listening...
ServerName:MICHELLEP
InstanceName:MICHELLE
IsClustered:No
Version:8.00.194
tcp:1433
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qieavFf286oU1@.individual.net...
> probably it's not a named instance but a default one, that's to say ROBXP
> and not ROBXP\RR..
> default instances automatically listen on TCP 1433 as this port is the one
> Microsoft reserved on IANA for SQL Server...
> try having a look at it..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>