|
Home > Archive > MS SQL Server Connectivity > February 2006 > COnnecting via IP address
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
COnnecting via IP address
|
|
| cfrank@investorforce.com 2006-02-25, 9:28 am |
| When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
Chris
| |
| cfrank@investorforce.com 2006-02-25, 9:28 am |
| I should have stated this but I am using SQL Server 200 on a Windows
2003 cluster
| |
| Linchi Shea 2006-02-28, 8:24 pm |
| Your SQL Server instance must be a named instance listening on port 1433. If
it were a default instance, connecting to the IP without specifying a port
would have automatically led to the default port of 1433, and would have
succeeded.
With a named instance, however, you are not directed to 1433 by default.
Either the client has to be told by the server via UDP 1434 as to what port
to use, or it has to identify the port explicitly. And if the client is
using an explicit IP address, you are not using UDP 1434.
Linchi
< cfrank@investorforce
.com> wrote in message
news:1140797262.929065.72080@i40g2000cwc.googlegroups.com...
> When I try to connect via IP to a newly created Active Active cluster I
> have to add the port to the IP for it to work. An example is if my IP
> is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
> then it works fine. Am I missing a setting somewhere to make this work
> just by using the IP? Oh... and just to note this work the same accross
> the network or if I am logged on local to the box.
>
> thanks
> Chris
>
|
|
|
|
|