highly appreciated.

I am trying to connect the named instance from my client computer... I can
easily connect the default instance of my remote machine but when I tried to
connect through named instance it gave me an error that SQL Server doesn't
exist or access denied...
In the client network utility I have defined the IP and alias of that server
but failed to connect.
Can any one give their expert idea.
Thanks
Roy wrote:
> I am trying to connect the named instance from my client computer...
> I can easily connect the default instance of my remote machine but
> when I tried to connect through named instance it gave me an error
> that SQL Server doesn't exist or access denied...
> In the client network utility I have defined the IP and alias of that
> server but failed to connect.
> Can any one give their expert idea.
> Thanks
Why are you defining an alias? Was it because you had no luck connecting
using the named instance? The named instance runs on a different port
than the default 1433. I think it might use 1434, but am not sure. Try
using the instance name first before resorting to using an alias. For
example, if you remote computer name is MY_COMPUTER and the named
instance is SQL2, try the following as the server name:
MY_COMPUTER\SQL2
If you still have trouble, it could be a firewall issue. Try temporarily
disabling any firewall software and see if that helps.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||First of all David, thanks for your reply...
I am at client computer and how client computer diagnose MY_COMPUTER\SQL2
until and unless I have to mention that the ip which is running behind the
MY_Computer... this My_Computer doesn't exist on the network... that's why I
have to mention this My_Computer IP in the client network utility so that it
can easily diagnose it... I am mentioning you what I did for connecting named
instance... if I am wrong then please correct me...
Step 1: I did findout the port No of named instance through SQL Server
Network Utility that was 1434 right.
Step 2: I have mantioned that port and IP in client network utility like
Netowork Utility > Alias >
Alias: RemoteServer
Server: 209.45.23.55
Port : 1434
Protocol: TCP/IP
when I registered this named instance server through enterprise manager I
have defiled RemoteServer/Instancename and then trying to connect but
failed... sql server doesn't exist or access denied...
David, as you said I have to connect simply through MY_COMPUTER\SQL2 but how
my client machine know MY_Computer IP ?
I hope you understand what I wanna tell you... I would really appreciate if
you reply me ASAP... thanks and have a great day,
"David Gugick" wrote:

> Roy wrote:
> Why are you defining an alias? Was it because you had no luck connecting
> using the named instance? The named instance runs on a different port
> than the default 1433. I think it might use 1434, but am not sure. Try
> using the instance name first before resorting to using an alias. For
> example, if you remote computer name is MY_COMPUTER and the named
> instance is SQL2, try the following as the server name:
> MY_COMPUTER\SQL2
> If you still have trouble, it could be a firewall issue. Try temporarily
> disabling any firewall software and see if that helps.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||David, what I am thinking right now... do I need to create linked server
before registering the named instance on my machine ?
"David Gugick" wrote:

> Roy wrote:
> Why are you defining an alias? Was it because you had no luck connecting
> using the named instance? The named instance runs on a different port
> than the default 1433. I think it might use 1434, but am not sure. Try
> using the instance name first before resorting to using an alias. For
> example, if you remote computer name is MY_COMPUTER and the named
> instance is SQL2, try the following as the server name:
> MY_COMPUTER\SQL2
> If you still have trouble, it could be a firewall issue. Try temporarily
> disabling any firewall software and see if that helps.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||Rogers wrote:
> David, what I am thinking right now... do I need to create linked
> server before registering the named instance on my machine ?
>
If you're just connecting over the internet (which I assume from your
last post that you are), you're correct that you'll need to use the IP
address. This just makes me think there's a firewall issue on the remote
PC or remote network preventing communications on that IP over port
1434. To determine this, you could swap ports on the remote server and
make the named instance 1433 and cycle the SQL Server. If you then
connect to the named instance, you'll know it's a firewall issue.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||David, you are very right but how can I change the port of default instance
to 1434 and named instance to 1433 ... basically this is our production
machine and couple of databases are running to hit default instance.. what u
think if i do this then all would be in trouble right...
Looking forward to your reply.
Thanks
"David Gugick" wrote:

> Rogers wrote:
> If you're just connecting over the internet (which I assume from your
> last post that you are), you're correct that you'll need to use the IP
> address. This just makes me think there's a firewall issue on the remote
> PC or remote network preventing communications on that IP over port
> 1434. To determine this, you could swap ports on the remote server and
> make the named instance 1433 and cycle the SQL Server. If you then
> connect to the named instance, you'll know it's a firewall issue.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||Rogers wrote:
> David, you are very right but how can I change the port of default
> instance to 1434 and named instance to 1433 ... basically this is our
> production machine and couple of databases are running to hit default
> instance.. what u think if i do this then all would be in trouble
> right...
>
Talk to your network guys and see if the firewall is in play.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Alright..... David, tell me one thing just for information... we can change
the default and named instance port through sql server network utilities
right ?
Thanks and looking forward to your reply
thanks david !
"David Gugick" wrote:

> Rogers wrote:
> Talk to your network guys and see if the firewall is in play.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||Rogers wrote:
> Alright..... David, tell me one thing just for information... we can
> change the default and named instance port through sql server network
> utilities right ?
> Thanks and looking forward to your reply
You should be able to, but since your default instance is an in-use
production database, I'd caution doing so during production hours.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Yes but if both the databases are not in used then I can change the port of
named and default instance right through SQL Server Network Utlitiy .
Thanks
"David Gugick" wrote:

> Rogers wrote:
> You should be able to, but since your default instance is an in-use
> production database, I'd caution doing so during production hours.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>