Re: highly appreciated.
- From: Rogers <Rogers@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 14 Jul 2005 09:00:05 -0700
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:
> > 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
>
>
.
- References:
- highly appreciated.
- From: Roy
- Re: highly appreciated.
- From: David Gugick
- highly appreciated.
- Prev by Date: Re: highly appreciated.
- Next by Date: Re: highly appreciated.
- Previous by thread: Re: highly appreciated.
- Next by thread: Re: highly appreciated.
- Index(es):
Relevant Pages
|
