Error Connecting to Remote Machine
- From: "Randy Whitehead" <rwhitehead@xxxxxxxxxxxx>
- Date: Wed, 3 Oct 2007 13:41:24 -0400
I have a remote server that I need to setup replication with, but I can't
get the connection setup because of a port issue.
When I first setup the server I could connect by using just
SERVERNAME\INSTANCE. Something happened about a month back and I am not
sure why but now I have to use SERVERNAME\INSTANCE,1433. I only have one
instance setup, but it is a named instance. For some reason I can't get
replication to allow me to specify the port number, so I would like to
figure out what is forcing me to use the port number in my connection
strings.
I have just recently realized that I can connect using just SERVERNAME, but
replication setup requires me to specify the instance.
Thanks in advance!
Here is what I have setup on my server.
SQL Server Browser Service is running
IP1
Active - Yes
Enabled - Yes
IP Address - MyPublicIP
TCP Dynamic Ports -
TCP Port - 1433
IP2
Active - No
Enabled - No
IP Address - MyLANIP
TCP Dynamic Ports -
TCP Port - 1433
IP3
Active - Yes
Enabled - No
IP Address - 127.0.0.1
TCP Dynamic Ports -
TCP Port - 1433
IP ALL
TCP Dynamic Ports -
TCP Port - 1433
SQL Native Client Configuration
TCP = Enabled
Default Port - 1433
.
- Prev by Date: Re: How many periods are REALLY needed?
- Next by Date: SQL Server 2000 Connection Timeout Issues
- Previous by thread: Re: How many periods are REALLY needed?
- Next by thread: SQL Server 2000 Connection Timeout Issues
- Index(es):
Relevant Pages
|
Loading
